2010/8/2 Dietrich Streifert <[email protected]>
> I've been following your thread. I'm not a qooxdoo developper, but i'm a
>> bit suprised you don't want to solve the real problem.
>
> Good to hear form someone knowing my real problem. I should stop paying my
> couch doctor ;-)
>
I'm sorry. It wasn't the most diplomatic choice of words.
That's not true. The form is reused. The loadtime is on first form open.
> Subsequent opening is alot faster.
>
That's great to hear. So we're talking about the inital loading time here.
Hmmm... where did you got my source code from? You did not or did you?
>
I was using some pseudo code. There aren't too many different ways to
actually 'render' a form.
Or are you not using the qx.form.Form class at all?
> The patient chart is loaded as a single xml-request. So, even if not
> visible, values are loaded into fields and cause changevalue events which
> have an influence to other fields like disabled fields etc.
>
But that part shouldn't take very long.
The actual rendering of all the widgets is another case.
Playground code to prove my case:
http://tinyurl.com/2fnf7a2
>So, even if not visible, values are loaded into fields and cause
changevalue events which have an influence to other fields like disabled
fields etc.
Feel free to create the fields! Just don't *render* them.
*Don't add them all to the DOM at once!*
In your screenshots I see widgets inside tab-pages.
The only way those widgets can be in a tab-page is if you *add* them.
So, somewhere in your code, there has to be something like:
myTabPage.add ( myWidget );
All i'm saying is that if you replace that code with:
myTabPage.addListenerOnce('appear', function(
myTabPage.add( myWidget );
});
Sure, in your code it's problely called something other than "myTabPage".
And your code is likely way more complicated than this. But somewhere,
somehow you are adding widgets to a tabpage.
And right there, you replace that code with the 'appear' trick above.
I would be really interested in hearing how this trick could possible be
hard to implement in any code-base behind the screenshots you sent here.
I'm still not 100% shure if the raise in created dom elements causes the
> problem. I'm still investigating.
>
Take a look at the playground code!
- Creating the objects: fast
- Creating the renderer: fast
- Adding the rendered form to the document root: performance hit!
*I'll make you a bet*
If this trick doesn't cut the load time by 80%, I'll drink a German beer
this week ;-)
Greetings,
Ralf
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
