Dear Tim,

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

1) Does EWB 2 supports localstorage, SqlLite, MySQL etc database support
in order to host our projects on linux hosted servers without using the
EWB server ?

2) Also any discount for EDB customers ?

3) Does it support CSS3 ? I want to create a web page using
EWB 2 control but i want to have my HTML layout with CSS and
customer jquery 3rd scripts.

Thank you

On 18/11/14 09:11, 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.

Tim, EWB2 components look to be nice and flexible which is just what I
was after. Really looking forward to using it so please feel free to
bypass beta testing and go for an immediate release!

If I did have one criticism of the new control layout features however,
it would be that the word "consumption" makes me think of tuberculosis.

Some questions ...

1. The video shows associating interfaces with a component via a
compiler directive. This is fine at design time but will it be possible
to associate an interface to a control dynamically at run time? For
example, I might use a standard TButton control when designing a form
but want it to display different attributes when the application runs.
Will this be possible? If so, how?

2. You mentioned in another append that the component library forms a
separate layer over the DOM and I noticed that you re-built the library
whenever you changed the control's interface. Will this create a second
Javascript file at run time or will the application still consist of a
single file that contains the component library? Will the file size
increase dramatically? Has run time performance changed much from V1?

I know that EWB2 is still in development but I am interested in how the
structure of the resultant application will look. Any chance you could
create a small example application using some of the new controls and
make it available for us to access via a browser?

Thanks.

--
Rick

Steve,

<< This looks very impressive. I can't wait until the release. Maybe it's
time for me to start doing component development again. >>

Yes, yes it is.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks Ivan.

Tim Young
Elevate Software
www.elevatesoft.com

Matthew,

<< I've emailed, and may start with my WebBuilder 1 "components" that you
can see at

http://www.banxia.com/resources/connect/userguide/index.html?rating.htm

which might be generally useful to others. Depends on how much time I get
really, as ever. >>

Those should be fairly easy. Are you using an canvas elements at all, or are
they all using plain HTML elements ?

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

Sergey,

<< Also send sent a request about to start component development.   Have
some ideas, energy and design experience to make EWB not only the
alternative of Sencha Space and ect,
but a new chance for Object Pascal, which Firemonkey and SmartMobile studio
obviously couldn't become. >>

Thanks, that is much appreciated.  EWB 2 will finally allow you guys to
start showing off what you can do, and I can't wait to see what you produce.


Tim Young
Elevate Software
www.elevatesoft.com

Bob,

<< Looks impressive Tim - sorry to sound like a stuck record but does the v2
compiler have interfaces and will I be able to use .pas files together with
IFDEFs? >>

It has interfaces, but unfortunately not the kind that you're looking for.
The compiler does have IFDEF support, though.  There will be more compiler
improvements coming along with the code editor improvements, and I will try
to work in interface support.

Tim Young
Elevate Software
www.elevatesoft.com

Michael,

<< 1) Does EWB 2 supports localstorage, SqlLite, MySQL etc database support
in order to host our projects on linux hosted servers without using the EWB
server ? >>

EWB 1.x does all of this now, and EWB 2 will be no different.  The same
issues apply - if you want to use a non EWB Web Server, then you simply have
to provide support for generating the JSON for dataset handling, and we
provide PHP examples that show how to do this with ElevateDB.

<< 2) Also any discount for EDB customers ? >>

You'll have to contact Sam in sales to be sure (sales@elevatesoft.com), but
I don't think that there are any discounts for the upgrade price, other than
whether or not you have a current subscription to EWB.

<< 3) Does it support CSS3 ? I want to create a web page using EWB 2 control
but i want to have my HTML layout with CSS and customer jquery 3rd scripts.
>>

EWB uses CSS3, but it doesn't expose it for modification since it's all
handled dynamically at runtime in the browser.  Frankly, if you want to only
use EWB for one thing, and still want to use HTML/CSS/JS for the most part,
then EWB is probably not the right product for you.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

Rick,

<< Tim, EWB2 components look to be nice and flexible which is just what I
was after. Really looking forward to using it so please feel free to bypass
beta testing and go for an immediate release! >>

Usually, my schedules (which are never correct) take care of this for me.


<< If I did have one criticism of the new control layout features however,
it would be that the word "consumption" makes me think of tuberculosis.
>>

Ugh, I never thought of that....

<< 1. The video shows associating interfaces with a component via a compiler
directive. >>

You're not associating the interface with a control at that stage.  You're
simply including the interface in the component library (after a rebuild) so
that it is available for any applications to use.  You will have the option
of selecting which interfaces to include in a given project, also.  The
interfaces are stored in a JSON format in meta tags in the HTML loader file.
The interfaces are loaded during application startup from the meta tags, and
then the controls can use them as they wish.  But, because the interfaces
are simply JSON, I eventually want to give the option of being able to load
them from whatever source one wants, which would allow for switching out an
entire application's interface at runtime, if one so desires.

<< This is fine at design time but will it be possible to associate an
interface to a control dynamically at run time? For example, I might use a
standard TButton control when designing a form but want it to display
different attributes when the application runs. Will this be possible? If
so, how? >>

Rule number one with EWB 2:  you can do whatever you want.  And yes, you
can do that - each TControl descendant has a method that is used to
interrogate which interface name to use for the control, and you can change
this to return whatever you want, based upon whatever conditions that you
want.  In most cases, you'll simply use a control's class name (the class
type handling is greatly improved in the compiler), and use the various
states in the interface to control dynamic changes within the context of a
control, but there are exceptions.  For example, the scroll bar control uses
a different interface class name depending upon whether it is
horizontally-oriented, or vertically-oriented.

<< 2. You mentioned in another append that the component library forms a
separate layer over the DOM and I noticed that you re-built the library
whenever you changed the control's interface. Will this create a second
Javascript file at run time or will the application still consist of a
single file that contains the component library? >>

The output is the same as with EWB 1.x, except for the style sheets.  There
are no longer style sheets, since there are no longer any themes.  Now you
just have two files - an .HTML file and a .JS file, so load times are pretty
quick in terms of latency.

<< Will the file size increase dramatically? >>

The application sizes are larger than EWB 1.x, but most of that is due to
the base UI layer.  In general, due to the lessened amount of code required
per new control, the size of the your application will grow less over time
as you add controls.  And, the compile-time compression still takes care of
a lot of this.  Right now I'm seeing around 250k compressed for applications
that use every control in the component library.

<< Has run time performance changed much from V1? >>

I haven't done any official profiling yet, but it sure seems snappier to me.
 The elements are much simpler, since there isn't any more "elements to
hold image bits" going on, so there is a lot less for the browser to do.
For example, a lot of the controls had up to 8 elements just for their
borders.  These same controls now use 1 element since the borders are simply
part of the element drawing.

<< I know that EWB2 is still in development but I am interested in how the
structure of the resultant application will look. Any chance you could
create a small example application using some of the new controls and make
it available for us to access via a browser? >>

I'll see what I can do.  Obviously, I want to be careful about releasing
things that may change, or getting into a discussion about too much before
the product is completed.  Don't want to get the cart before the horse.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com

On 21/11/14 10:17, Tim Young [Elevate Software] wrote:
> lots of good things ....

Thanks for taking the time to respond Tim. It all sounds (and looks)
excellent. Could be the best Christmas ever!

--
Rick