Thiago H. de Paula Figueiredo wrote:
>
> Tapestry-core almost donsn't have UI-related code, and all it's all in the
> components and CSS files (that are overridable and can be configured to
> not be used).
>
Thiago H. de Paula Figueiredo wrote:
>
> Tapestry-core has two parts: the framework itself and a set of components.
> The framework isn't dependent on Javascript (including its AJAX support),
> so I think your line is already drawn. Finding the places that use
> Javascript is easy: look for uses of @IncludeJavascriptLibrary and
> RenderSupport.addScript*() methods under the org.apache.tapestry5.corelib
> package.
>
well, that's kind of my idea really. to seperate them into two parts. That
way, changes to the UI layer don't break the core.
The UI module can then start focusing on how to deal with presentation
specific issues, such as Zones and the Tapestry Object.
What do you guys think?
--
View this message in context:
http://n2.nabble.com/Switch-from-Prototype-to-jQuery--tp2245624p3058085.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
