Hi Ron, I definitely welcome any feedback people may have.
It's obvious that I haven't spent nearly as much time on components/widgets as I have been on general infrastructure. If you have a specific problem or two in mind I can try to come up with solutions, but with only solutions I'm going to have a hard time visualizing everything properly. Please feel free to chirp up with more specifics, I do value your input very much. (as you have been doing this for as long as I have I think ..) On 8/22/06, Ron Piterman <[EMAIL PROTECTED]> wrote:
Hi all - The 4.1 version seems very exciting: the @EventListener annotation is really cool and easy to use. Currently I am working on a Project with a very extensive use of XHR using Dojo and currently Tapestry 4.0 In evaluating 4.1 it seems to me, a great work has been done to enable render and process XHRs - it seems to me however that some *abstraction* and *extensibility* is missing. Talking concrete: The ResponseBuilder (Dojo, Default, JSON) are built around an Interface that enables these three. The Tapestry Javascript Response renderer (tapestry.load) handles a few actions : JavaScript processing and "replace by id". I would suggest making both response builder implementations and tapestry.load more extendable, adding pluggable actions to both. Cheers, Ron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
