That event stiff looks really cool. I'm glad you're on the team Jesse. Comprehensive support in Tapestry for ajax and Web 3,4,5.0 (whatever) really depends on your experience.
I recently took a whack at implementing a very rich Ajax tree and while I learned alot about Ajax, I learned more about what I don't know! Geoff On 2/26/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > It's like a framework christmas! The EventListener idea is incredibly cool. > Mixing that in with ajax/json/flash/form logic and pretty soon the whole > thing just starts working in incredible ways. > > I'm not trying to be all "gung ho" about every little thing I read, but this > is really a critical step. No one has really addressed all the changing > design patterns that are emerging and this one seems to do just that. I > won't call it web 3.0 though. Just tapestry 5 ;) Seriously though, all of > the core-ish people on the "exciting new web 2.0" ajax end of things have > been hinting about how cool it will be when a framework really gets what > they're doing /embraces it and provides a new development style for these > things. Not just another wrapper around a few js libraries... > > That sounds like exactly what you're describing. > > The only actual "new" thing I can add to your thought pool would be > addressing client state. I think a lot of work is going to go into 4.1 for > this - but if you think of the client as just a pure gui with a remoted > backend, that is also handicapped in that it doesn't really know how to > render itself without the backend's help, you can get a better vision for > what is more or less going on there. (ie a bunch of gui code running around > , maintaing state of some of that info on the server/client and being very > very smart about what gets updated when , even what happens > before/during/after update...etc ) > > jesse > > On 2/26/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > > Other ideas: > > > > Components will be able to emit events. Methods on your components > > will have an @EventListener annotation that defines which components > > and events they should be invoked for. So instead of defining > > listeners via parameters (pushing the listener method into the > > component), we just define the listeners and let Tapestry wire it up. > > > > I'm looking for more areas where Tapestry can 'do the right thing'. > > > > -- > > Howard M. Lewis Ship > > Independent J2EE / Open-Source Java Consultant > > Creator, Jakarta Tapestry > > Creator, Jakarta HiveMind > > > > Professional Tapestry training, mentoring, support > > and project work. http://howardlewisship.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- The Spindle guy. http://spindle.sf.net Get help with Spindle: http://lists.sourceforge.net/mailman/listinfo/spindle-user Blog: http://jroller.com/page/glongman Feature Updates: http://spindle.sf.net/updates --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
