Em Wed, 10 Jun 2009 16:45:53 -0300, Onno Scheffers <o...@piraya.nl>
escreveu:
I wouldn't mind helping out. I'm not an expert either, so I don't think I
can do it all alone. But I think this is important enough for the future
of Tapestry to donate some of my time.
Nice! I think we need to focus in at least three issues:
1) Defining an framework-independent API to be used by Tapestry (events,
DOM manipulation, selectors, etc). Maybe there's something similar out
there, not necessarily Tapestry-related.
2) Reimplement Tapestry.js in other Javascript frameworks (I guess jQuery
would get some votes here :)).
3) Reimplement Tapestry components.
Another issue would be define a Tapestry-IoC symbol (just like
SymbolConstants.PRODUCTION_MODE) to define the default Javascript
framework to be used. This way, we could have a single Autocomplete mixin,
for example, that looks what JS framework to use and our templates and
page classes would be JS framework-independent. But that's the easy part.
:)
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
