Hmmmm. As to the first mentioned issue, of ajax enhancing all of your components, I agree that this is less than ideal, but there are two things that need mentioning in regard to that. The first is that these enhancement operations only occurr with page-caching turned off, which is what I hope is only the case in development and not production.
The second problem is that to provide ajax support in the way that we have there really hasn't been much of a choice other than doing these enhancements. Ideally it would be somewhere staticly compiled into the tapestry core, but this isn't going to be addressed by the tapestry folks until at least tap 4.1 from what I hear. I don't really know how else to do it without these enhancements or modifications to tapestry itself, unless you've got a better idea? I view it as more of an inconvenience for now, with the small glimmer of hope that at some point we will be able to take some of the knowledge gained from the ajax enhancements made in tacos and integrate them into tapestry in a manner that fits with the rest of the systems design. The only solice is that it doesn't happen with caching turned off so it's just more of a pain in the ass during development. As to your tree state problem, I don't believe I've seen any mention of it in bug reports or on the tacos/tapestry user mailing lists until this post, so you'd have to be more descriptive, give examples for me to be able to respond reasonably. I can't help what I don't know exists :) jesse On 9/13/05, Aslak Gronflaten <[EMAIL PROTECTED]> wrote: > > I've tried Tacos tree, but I don't like the fact that it tries to ajax > enhance my pages and components (and failing at that) for every > request to the page. That doesn't seem thought through, and certainly > performs badly on my computer. Also, for some reason, folding out a > tree works fine on the first level, but it doesn't fold out second > level nodes. As if it doesn't remember state. This is using the basic > tree example code as a basis. > I'd love to get it to work though.... > > Aslak > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
