I would also add in that these building blocks, when re-written should be more than enough of a foundation for any library to use together with tapestry. I see them all as being very interchangeable.
The major piece of the framework that I think you have in question is the engine service on tapestry's end that handles ajax requests as well as the interactions between that service and the rest of the tapestry framework. With this alone it should be relatively easy for anyone to plug-in whichever JS library they want as well as most anything else...Isn't that why hivemind/aop is so great? I can't speak on Viktor's behalf, but if what we (you?) come up with over the next couple weeks seems like a good foundation there's absolutely no reason why someone couldn't submit it as a patch to tapestry to avoid forcing other component libraries to have to mix in a tacos engine jar. (I'm hoping we can seperate this part of tacos a little bit into a sort of "core ajax" release for this specific reason). There are also plans to provide ajax request logic to more than just components, like actual service calls on hivemind services/etc...This should all be relatively straightforward from what I've read so far. I know I don't care who implements what, but I don't see anyone else building a real foundation as of yet so we are pursuing it ourselves. If you really do feel this strongly about it then we could definitely use your help in tacos, even if you don't ever actually use a tacos componenet ;) jesse On 8/12/05, Viktor Szathmary <[EMAIL PROTECTED]> wrote: > On 8/12/05, Alex Ieong <[EMAIL PROTECTED]> wrote: > > Jamie, I visit Tacos's site quite often. But frankly, it doesn't seem > > too attractive comparing to the frameworks I metioned. It provides > > just a few Ajax enabled compoents and they are in fact "re-inventing > > the wheel", except that they are really Tapestry compoents. > > At this point Tacos is trying to provide some building blocks that fit > well into the Tapestry rendering lifecycle but utilize ajax. With > RPC-ish ajax frameworks, there's very little in tapestry that you > would leverage (ie. none of the templating and callback mechanisms). > That said, there are plans to port the current javascript to > prototype.js - with that we can also leverage some eyecandy from > scriptaculous and rico... Also, there's another release coming up > shortly with further ajaxified components (such as a PartialTree)... > > > regards, > viktor > > --------------------------------------------------------------------- > 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]
