dojo freezes because it parses the whole page source as text, it is sick,
the whole widget part is too heavy weight. the standalone widgets are even ok, baut the layout ones (TabContainer ... SplitPane ...) yuck. On 11/23/06, Norbert Sándor <[EMAIL PROTECTED]> wrote:
Yeah, but I have some "old" tapestry components which still use the embedded definition of dojo widgets. It seems that I have to modify them... The interesting thing is that the pages contain only 1-2 dojo widgets, so I don't know why do they freeze :\ Regards: Norbi Jesse Kuhnert írta: > Right. If anything that config option is mostly there to help people > getting newly acquainted with dojo. No one ever actually sets it to > true in production level apps as the performance overhead involved in > iterating over the entire dom tree checking attributes on the client > side is just too much for most situations. > > On 11/23/06, Norbert Sándor <[EMAIL PROTECTED]> wrote: >> If I set Shell.parseWidgets to true, some of my pages freeze (utilize >> 100% CPU and never seem to finish) in IE6 but working properly in FF1.5 . >> This must be a dojo problem, but maybe you want to know about it... >> >> Regards, >> Norbi >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
