On Thu, May 20, 2010 at 4:19 AM, Howard Lewis Ship <[email protected]> wrote:
>
>
> The second transition is the gradual re-writing of the tapestry.js
> client-side layer. As I've grown more proficient in client-side
> JavaScript, I've been moving away from my early approach, which was
> essentially Java-in-JavaScript, by way of leveraging the Protoype
> class functionality.  Where I'm at now is a more functional (if still
> stateful) approach based almost entirely on event publishers and
> observers combined with JavaScript closure functions. I feel a gradual
> move in that direction is the way towards eventually replacing
> Prototype & Scriptaculous with jQuery, and making it possible to
> cleanly support other JavaScript foundations.


I don't know if you checked what has been made on tapestry5-jquery [1]
library, but when developing it, I tried to follow theses rules:
- make porting from Prototype to jQuery the most transparent as possible for
final user
- coding jQuery using jQuery philosophy : it's obvious, but that's something
I really wanted to respect. As far as I know, there are two "must follow"
design patterns for jQuery : the jQuery plugin pattern [2] for stateless
component and the jQuery UI widget pattern [3] for state-full ones.
- don't reinvent the wheel : I tried to use as much as I can already
existing jQuery plugins. Most of them came from jQuery UI project.

I'd be interested to hear what the other developers see as must-haves
> for a 5.2.  I know I'd like to see what's going on with the new
> Confluence documentation.
>
>
Like Igor, I would like to see more IOC features, as it is definitely the
strength of Tapestry.

I'm convinced that there are ways to explore with the "pluggability" of
Tapestry. In fact, I think that Tapestry could be used to make
applications/plugins that extend the behavior of another one, like Wordpress
blog system and its plugins (I'm not talking about simple components
library).


[1] http://github.com/got5/tapestry5-jquery
[2] http://docs.jquery.com/Plugins/Authoring
[3] http://docs.jquery.com/UI_Developer_Guide

Reply via email to