Thanks! I agree, the delay I'm experiencing could be caused by parsing of widget tags. I'm using a dojo package downloaded from the dojo website. I didn't realize that there was a dojo file in the tacos demo app, I see now that that dojo file is about 170k, I think the one I'm using is 300k or more. 170k is still a bit large, but I thought the browser was supposed to cache all .js files after the first load?
My experience is that the page loads slowly all the time, not only the first time. I guess that indicates that the widget parsing/initialization is the issue here. Inge On 1/23/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > Performance issues could also be caused by the dojo semantics of parsing > pages for "widget" tags. This can be turned off, but I'm afraid the > current > incarnation of tacos isn't guaranteed to work in this scenerio. > > It is something I plan on addressing directly in the coming weeks with > tap4.1 / tacos4.1, but I can't say when it will be done enough for anyone > to > attempt using. > > On 1/23/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > > > Are you using the dojo.js package provided in the tacos download, or one > > that you've gotten on your own? > > > > On 1/23/06, Inge Solvoll < [EMAIL PROTECTED]> wrote: > > > > > > This isn't really a Tapestry problem, but I ask it here anyway. > > > > > > I would really like to use all the features of tacos, and as far as I > > > can > > > see, I have to include the full dojo js package to use tacos. I have > > > tried > > > to download dojo and use it on my pages, and I notice a slowdown on > page > > > > > > load that isn't acceptable. I guess this is caused by the file size of > > > dojo.js, or because of the browser spending some time initializing > dojo. > > > > > > Is there an absolute minimum of dojo code that can be included to make > > > tacos > > > work? > > > > > > Inge > > > > > > > > > >
