I've posted a short video on YouTube that shows a little bit of Elevate Web
Builder 2 and is intended for component developers.  EWB 2 is getting close
to being completed, and we wanted to try and get the product into the hands
of some component developers before the first public test release so that
they can play around with the product and give us some feedback on component
development with the product (ease of use, etc.).

If you're a component developer, and are interested in joining this early
experience program, please contact Sam Young at samyoung@elevatesoft.com and
she'll put you on the list.

As for everyone else:  I'm finishing up the component library right now, and
progress is brisk, so I'm hoping that we have a final release by Christmas,
with a test release by early December.  It will be difficult, but I think I
can get it close to that if I push.  The only particularly difficult
controls left to deal with are the TGrid and the TMemo, and the TMemo only
because it's a bit of a challenge to deal with the scrollbars properly (EWB
2.0 uses its own scrollbars, not the native OS scrollbars).  After that
there is some minor cleanup involved with the Project/Environment Options
dialogs, and I'm done.  If need be, I'll be skipping any public testing and
go right to a release since most of the core of EWB 2 is pretty well tested
at this point.

I'm going to start popping in here more as we get closer to a release date.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

It really helps if I include the URL:

https://www.youtube.com/watch?v=ZV7CKDuQJEw

Sorry about that.

Tim Young
Elevate Software
www.elevatesoft.com

Going to take a peek right now!!!!!

Walter

Tim Young [Elevate Software] wrote:

> It really helps if I include the url:
>
> https://www.youtube.com/watch?v=ZV7CKDuQJEw
>

Looking really nice. I can see the layout system is going to be very
powerful, but also give us a bit of conversation about how to achieve a
particular mode. My first thought is that it might be handy to have a
mode where you can have arrows or indicator lines or something to
indicate the "flow". But I love the margins that give the spacing,
instead of the old "stack of panels" that was once the way.

It also appears that the components are "pure pascal" and not
Javascript at all. Which is fine of course - there is a lot of power
there. It would be nice to be able to incorporate standard Javascript
components, but with 1.x I've done full native "components" and they
have worked well.

So, one question, for someone not going to be on the early experience
programme: Can I pre-order?


--

Matthew Jones

Tim Young [Elevate Software] wrote:

> I've posted a short video on YouTube that shows a little bit of
> Elevate Web Builder 2 and is intended for component developers.

I scoured the video for hints of touch support, but didn't see any,
which is probably because it was aimed at component developers.
Does EWB 2 have touch events in the first release?

It also struck me that I aim to build a component, but it will be
forever private (key part of our core competence that I don't want to
give away!). Would that exclude me from the early programme? It may be
that other commitments stop me playing anyway, but I might spend time
over Christmas exprimenting on what I want to build.

Matthew

Tim


Looks nice, looks impressive and I was following until you started consuming things.

Roy Lambert

Roy Lambert wrote:
> I was following until you started
> consuming things.

Give the lad a break, he was hungry.

On 11/18/2014 4:10 AM, Matthew Jones wrote:
> It also appears that the components are "pure pascal" and not
> Javascript at all. Which is fine of course - there is a lot of power

I assume they would get compiled into JS eventually though. Supporting
native JS components in design time would be very hard (says one not
having to write a IDE and compiler) since you cannot control how they
interact with the DOM etc nor can you provide any hooks that design time
might need.

> there. It would be nice to be able to incorporate standard Javascript
> components, but with 1.x I've done full native "components" and they
> have worked well.

I assume native controls will still be be supported runtime and
hopefully better than v1. If at design time there is a generic container
where the JS component goes runtime is best i'm hoping.

Raul

Raul wrote:

> I assume they would get compiled into JS eventually though.

Indeed - it has worked very well previously. I don't know what I was
expecting really, but I do like the look of what is coming.

--

Matthew Jones

Tim, this is really good news for all of us!
Can't wait to test it, to create some components,
and of corse to give the new life of our language.
After watching promo video i think you took the right direction.