My point is that Tapestry-core should be about generation of state management of pages, and generation of markup. javascript niceties are a plus, but not core.
Moving away UI related code into another module should make it easier to encapsulate the problem, and deal with it in a succession of refactorings. Once you have the problem isolated, you can consider what to do with the javascript framework. Drawing a clear line can be a difficult task, but it can help divide responsibilities. -- View this message in context: http://n2.nabble.com/Switch-from-Prototype-to-jQuery--tp2245624p3057851.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
