I just wanted to put this out there so that I don't have to keep addressing
this question, because it keeps coming up over and over again.

1) Yes, the component framework is not the most extensive in the world right
now.
2) No, it isn't going to stay that way, and newer components will be added
as quickly as possible, including menus, page controls, graphics properties
for gradients, canvas functionality, etc.

So, please do not keep asking us whether X component will be available, and
when.  The new components will be coming out as fast as they can be written,
but my first order of business is to get the back-end JSON layers
implemented in PHP, etc.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

And, for the record, I'm not picking on you Kevin.  It's just something that
keeps coming up, to the point of distraction, so I wanted to address it in a
more public manner.

Tim Young
Elevate Software
www.elevatesoft.com

<< but my first order of business is to get the back-end JSON layers
implemented in PHP, etc. >>

Cool.

"Tim Young [Elevate Software]" wrote:

<<And, for the record, I'm not picking on you Kevin.  It's just something that
keeps coming up, to the point of distraction, so I wanted to address it in a
more public manner. >

No worries.  I don't feel picked on.  I can imagine that the release of the trial has created an avalanche of questions.  At least there is good interest.

Maybe you can pin/sticky this thread before it gets bumped down the list by people asking about desired components

Kevin,

<< No worries.  I don't feel picked on.  I can imagine that the release of
the trial has created an avalanche of questions.  At least there is good
interest. >>

Yes, absolutely.  I'm doing triage right now.

<< Maybe you can pin/sticky this thread before it gets bumped down the list
by people asking about desired components >>

I need to add that to the forums functionality - Yeah ! something else for
my to-do list.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim

Thank you ! As soon there's a <canvas> and the ability to inject <script... myscript.js>, we'd like to try to port our TeeChart for HTML5 Javascript to WebBuilder. (Very similar structure and features to TeeChart for Delphi)

http://www.steema.com/teechart/html5

regards
david

David,

<< Thank you ! As soon there's a <canvas> and the ability to inject
<script... myscript.js>, we'd like to try to port our TeeChart for HTML5
Javascript to WebBuilder. (Very similar structure and features to TeeChart
for Delphi) >>

Actually, if your TeeChart component is already written in JS, then we can
surface it now in EWB.  EWB doesn't support injection of JS into the Object
Pascal, rather it requires that you define an external interface to the JS
code:

http://www.elevatesoft.com/manual?action=viewtopic&id=ewb1&topic=External_Interfaces

This allows the compiler to enforce all type-checking, etc. rules on the
external JS code also, which keeps simple bugs to a minimum.

So, what someone would do is simply add the TeeChart.js file as external
code to their project, and then add an EWB TeeChart.wbs (or whatever) unit
that includes the external interface to the JS code to their uses clause.

However, send me an email (timyoung@elevatesoft.com) and we can discuss
another option, which is to have native charting support directly in the
Object Pascal dialect supported by EWB.  I'll need you to send me the source
so that I can review it to see if it is feasible, but it would allow for
people to set up such charting controls at design-time in the IDE.  It would
also allow the EWB compiler to invoke compression/obfuscation on the
TeeChart code, which drastically reduces the size of the resulting JS code.

Thanks very much,

Tim Young
Elevate Software
www.elevatesoft.com