>> It's my choice in projects where tapestry would be overkill.
> For example ?
Projects where the component model does not pay off the increased complexity.
Maybe its just because I am doing webapps for so long that action
based is more natural to me.. but my feeling is that its much easier
to utilize third party products like jQuery UI and others if you do
not need to care about components and life cycles.
To build a tapestry project you need more work/thinking in the
beginning, starting with wrapping javascript widgets inside your
components. IMHO this pays off if your project is getting very complex
and you can heavily re-use your components. Or on the other side for
very small projects, where you don't need to tweak the UI and can rely
on the standard components provided.
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
