I'm very much hoping to have Tapestry 5.0.6 out soon. I've been squeezing in some more time to work on Tapestry 5 and just added a BeanDisplay component (to complement the BeanEditor component).
The Ajax story for Tapestry 5 is still up in the air ... the specter of writing an abstraction layer has come back. And I still want better, smarter handling of Hibernate ... it seems to me that the BeanEditor should be capable of handling to-one relationships in a smart way. And Spring WebFlow integration would be a snap if I just had a couple of days to work on it.
I'm personally anxious to get Tapestry 5 solid and shipped ... but not before it's ready.
9 comments:
Do you think you'll use decorators from T5 IoC to better tweak hibernate support? If not why?
I've read the debate about abstraction layer for javascript... it's always a mess, choose one and stick with it.
Howard, could you give us more details about the way that Tapestry 5 will work with Ajax ?
From my point of view, there is essentially a need for linking Javascript with Java like DWR do.
DWR does not integrate very well with Tapestry, so do you plan to implement a DWR like functionnality ?
"The Ajax story for Tapestry 5 is still up in the air"
Howard - you know what to do to solve this problem ....
Hi,
Do you have an estimation of when we could see the ajax support on Tapestry 5? I am very curious about that :)
There are some really cool things that can come from integrating ajax support into a web framework. It can also be very limiting to people whose choice of client side libraries is driven by some external factor. I feel like someone on this comments list needs to be wishing for few/easily plugable/easily ignored dependencies on particular js libraries.
I think we need that tapestry should help us to use our favorite JS library with a clean, easy to use design and a good documentation. With this in place is matter of time that appear integrations of all the flawors, and we don't need to worry about any particular ajax implementation.
I'm not sure I see an easy integration between DWR and Tapestry. But the leap forward in quality of Javascript libraries over the last year is amazing. JQuery is just stunning to me, but there are lots of people with legacy code in other libraries of course. So some sort of pluggable architecture seems to make sense.
I think that you don't need a pluggable api (at least not for T5, maybe T5.1); as long as Tapestry has decent AJAX support which plays "nice" with other people's favorite JS library then so be it, at least it would get the core framework out. Also: DWR is kind of nice; it would be pretty cool if there was a T5 injection mechanism to use it.
Is there something new in Tapestry -> DWR integration? Does anybody heard something new since 2007?
Post a Comment