Other posts have handled your specifics well. Evaluate T5. I started active development on T4.0. I have since migrated a few of the smaller applications from T4 -> T5 and I am doing all new work in T5.
In the T4->T5 migrations, I found I was deleting lots of code and cleaning up my templates. Also, the hot reloading of changes is amazing. With the largest of my T4 applications it was getting painful to be doing restarts after simple fixes. It was great having the time to get coffee, but productivity suffered. T5 is just go-go-go. The one place where T4 was better than T5 (I found) was WYSIWYG templates. I think it was easier for shops where you had both designers and programmers. There were times where I would take off my coding hat and just work with HTML, CSS and a browser and focus on appearances. With T5, it's easier just to run your app and tweak on the fly. Jonathan > -----Original Message----- > From: Andy Blower [mailto:[EMAIL PROTECTED] > Sent: Saturday, March 29, 2008 5:45 AM > To: users@tapestry.apache.org > Subject: [T5] Tapestry evaluation + questions > > > Hi there, I'm evaluating Tapestry (among others) for the web framework > we'll > use at my company for the next 5 years or so. We've used Struts 1 for the > last 5-6 years and it's served us well, even if it was higher maintenance > than was first apparent. I have spent over two days reading about Tapestry > history and general thoughts about past and future which has proved rather > distracting. I'm really not sure whether I should evaluate 4.1 or 5 > because > the documentation and intro/tutorial material isn't ready yet for 5 and > I'm > completely new to component oriented frameworks. If I evaluated 4.1, would > that be valid for us still to go on to use 5? It's really hard to get a > handle on the differences of two things you don't yet understand! > > I have three (more specific) questions: > > 1) What methods are known for implementing webpage templates in Tapestry > (e.g. banner, nav, sidebar, content, footer) and is there one considered > 'best practice'? > > 2) How easy is it to add custom AJAX interactions? I'm thinking of > interactions like checking a checkbox to mark a search result, return > success and visually change the appearance. > > 3) Is it practical to have base classes containing common functionality, > which are extended by very terse page classes along with actual page > templates or am I thinking about this wrong? > > With the only T5 examples being so trivial, it's really hard to get a > bigger > picture view at the moment, but I am very intrigued. > -- > View this message in context: http://www.nabble.com/-T5--Tapestry- > evaluation-%2B-questions-tp16368331p16368331.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
