My application is growing and I wonder, if there may be restrictions
about code size and number of components.

Currently the compressed sizes are:
index.js   257KB
modern.css  87KB

I have about 15 forms, all created at startup and I use nested panels
for aligning controls.

For me this doesn't looks big but before I start "to grow" the
application (add up to 50 forms) I would like to know others
experiences.

Also I didn't find a way to see how much memory is used in the browser
by my application and if this is ok or if it is too much.

cu Christian

On 6/27/2013 9:11 AM, Christian Kaufmann wrote:
> My application is growing and I wonder, if there may be restrictions
> about code size and number of components.

Sounds quite reasonable to me but no first hand experience - all apps
small at this time.


> Also I didn't find a way to see how much memory is used in the browser
> by my application and if this is ok or if it is too much.

This will likely depend on browser implementation but in Chrome there is
a nifty task manager under Tools->Task Manager menu (and there is even
more detail in Stats For Nerd link there).

This will show entire tab process (and not just your app) - i'm thinking
one could do an absolute minimum html )or ideally 1 line JS app to init
the JS engine) page and compare memory usage of that with EWB app but
not sure if that would capture the memory just for EWB app well enough.

Raul

Have a look also at the F12 options in Chrome, one of which is Timeline. That gives
you tons of info on memory and time and lots!

/Matthew Jones/

> I have about 15 forms, all created at startup

That prompted me to look at my application, which I've been pondering the startup
time of recently. I now have 8 forms along with the main form, and I just turned
off auto-create for them all to see what the difference was. Much faster startup.
Thus I have now searched for .ShowModal; and added a call to a "NeedfrmExample"
procedure for each form, which will be in the form unit and like:

procedure NeedFrmOptions;
begin        
if not assigned(frmOptions) then
 frmOptions := TfrmOptions.Create(Application);
end;

This then does the work when needed, and not before (or at all for many of them).
The rest of the code is as-before, but with less resource taken, and less time at
startup.

Thanks for the prompt.

/Matthew Jones/

Christian,

<< Currently the compressed sizes are:
index.js   257KB
modern.css  87KB >>

jQuery is around 55KB minified (compressed), and ExtJS is at least 700+KB
minified, before you even write a single line of code (and doesn't include
any CSS).  That's the perspective to keep in mind, in terms of code size.

Having said that, each form (and its contents) takes time to create/load, so
reducing the number of auto-create forms and using dynamically created/freed
forms improves startup performance and the user experience, just as it does
with Delphi applications.  It also allows for leaner memory usage, as HTML
elements are destroyed in the browser when the form itself is destroyed.

Tim Young
Elevate Software
www.elevatesoft.com

Tim, could you add an option somewhere to have the IDE not auto-create forms by
default? That would be nice one someone has decided to take control of the forms.
(Personally I'd add it to the project, so a new project is easy and just works, but
a complex project under manual management can be set appropriately.)

/Matthew Jones/

On 6/27/2013 11:39 AM, (Matthew Jones) wrote:
> Tim, could you add an option somewhere to have the IDE not auto-create forms by
> default? That would be nice one someone has decided to take control of the forms.
> (Personally I'd add it to the project, so a new project is easy and just works, but
> a complex project under manual management can be set appropriately.)
>
> /Matthew Jones/
>
Matthew,
I may not be reading your question right, but if I am, I was just
reading about this yesterday in the help file.  If you place all of the
forms in the Available Forms box they won't be marked as Auto-Create.

Hopefully I'm not too far off base and this helps a bit.

-Dan

On 6/27/2013 12:58 PM, Dan Collins wrote:
> On 6/27/2013 11:39 AM, (Matthew Jones) wrote:
>> Tim, could you add an option somewhere to have the IDE not auto-create
>> forms by
>> default? That would be nice one someone has decided to take control of
>> the forms.
>> (Personally I'd add it to the project, so a new project is easy and
>> just works, but
>> a complex project under manual management can be set appropriately.)
>>
>> /Matthew Jones/
>>
> Matthew,
> I may not be reading your question right, but if I am, I was just
> reading about this yesterday in the help file.  If you place all of the
> forms in the Available Forms box they won't be marked as Auto-Create.
>
> Hopefully I'm not too far off base and this helps a bit.
>
> -Dan
>
>
>
>
Sorry, meant to add reference to that post:

Manual -> Getting Started -> Project Options

-Dan

Indeed, but if you then create another new form, it is put in the auto-create list.
It is an option to stop that, per project, that I'd like. Even a manual option in
the project file would be fine - it is perhaps an advanced option.

/Matthew Jones/

On 6/27/2013 2:56 PM, (Matthew Jones) wrote:
> Indeed, but if you then create another new form, it is put in the auto-create list.
> It is an option to stop that, per project, that I'd like. Even a manual option in
> the project file would be fine - it is perhaps an advanced option.
>
> /Matthew Jones/
>
So you mean an option as an alternative to going into project options
and placing the new form in the available forms box every time you
create a new form?

We're going to run out of space for all of these extra buttons

I can actually understand your desire for little options like this.  I
wish that TMemo's were, by default, created with TabStop = False.
However, when I think about it, it's really just me being lazy.