just like in spring, you'll have a separation between the view technologies and the spring MVC, the classes that represent the web framework should be in core, and the ui related classes in its own module.
while it can be argued that ui components can change quite a lot, and would potentially bear the most of the bugs, the core can be more safely considered internal, and that would help shield the API from changes. Anyway, I'm happy to have revived this thread because it looks like there's plenty of room to improve in this area. Thiago H. de Paula Figueiredo wrote: > > Em Wed, 10 Jun 2009 17:16:03 -0300, ice <fra...@gmail.com> escreveu: > >> 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. > > Changes to the UI layer, as Tapestry is now, won't break the core, so > there'se no need do separate it in two projects, IMHO. The core is already > independent of the components. > > -- View this message in context: http://n2.nabble.com/Switch-from-Prototype-to-jQuery--tp2245624p3058500.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
