Ok, sounds good... On a side note, I'm not dead set against not including dojo in tapestrys core, I just want to be sure it's for a very good reason as it will sort of take some of the fun out of what I'm doing. It's not a ~must have~. The ajax support will still work either way..
On 2/1/06, Ron Piterman <[EMAIL PROTECTED]> wrote: > > as mentioned in my previous postings, its quite a time difference, so I > will set some test tommorow... > Cheers, > Ron > > Jesse Kuhnert wrote: > > There is a delay whenever using a dojo page - I see it more at home than > > > > > >>on my dev box, and that concerns me: > >>I don't know what dojo does that makes the browser think twice before it > >>shows a page but it does somthing, and this 0.5 seconds (in the good > >>case) where my browser window is white - this 0.5 seconds will lead my > >>customers to click to the competitor's web site, so I just can not > >>afford it. > >> > >>this "white delay" exists also to some extent in prototype but dojo > >>breaks the records there... > >>As said, in (current) tapestry pages (also with forms) this does not > >>happen, and as for me, it also shouldn't. > > > > > > > > I'd be very interested in knowing if you experienced this delay if you > > configured dojo using "parseWdigets: false" in your djConfig variable. > > That's the exact reason why you experienced delays a long time ago, and > was > > addressed in my previous email I believe. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
