-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would like to share a recent success, with Tapestry.
In short, when I first looked at Tapestry, I thought "the docs could be better". Actually, I thought "I think this thing is good... if I learn it and decide to use it, I will contribute Tutorial". Hence: I am writting the next tutorial. :-) After chapter 3, I found that I really didn't know quite enough as I would have liked in order to continue - so I decided to re-write one of the sites I have (http://dataarmour.dyndns.org). In short, the site would require: * Static content * Dynamic content (news items, downloads, articles) * Consistent look and feel * Ability to maintain it all via a web interface (add/edit/delete content, downloads, release information and news) Originally, the site was done in JSP/Servlets. I had used it in order to learn those technologies at the time. I had considered using Turbine/Velocity - but having used them before in a couple of projects - was not that keen (also, I did want to see what Tapestry was like on a realistic project). Lastly, I the very reason I went looking for a web framework (and found Tapestry) was the I intend in the near future to write a web front end to a server application. I now know that Tapestry is more than capable. I will not be using anything else! I slowly built up the site, first adapting the Border concept used in the tutorial, adding static content and the like. I then moved on to creating my own components, and also custom components with custom renderers. Finally, I used Cayenne for the DB O/R mapping, after reading other peoples posts about it on this list. It's good. I have to say, the power available in Tapestry, once the initial hurdles have been overcome (which for me, was a more thorough understanding of the rewind/render process, and how stale links can occur) is amazing. The most complex form that I had in the old site can be done ever so easily in Tapestry. I would hate to think what some other other administration forms would be like to do in JSP/Servlets. I'm sure absolutely sure they are "do-able", but not in the same timeframe! In addition, while my thinking and learning evolved, the site code and content stayed very clean. During the refactorings I did, still things remained clean - - and the refactorings were easy and localized. For me, this is a testament to Tapestry. Good stuff! Someone on this mailing list once said "Tapestry makes simple things hard, and hard things simple". I would now change that to "Tapestry makes simple things tedious and hard things simple". The parts I found tedious were static content, typically in the form of multiple static pages. However; I believe the benefit is that when you DO come to add any dynamic interaction or support - the framework is there. The price is well worth paying (well, it was for me - I have only 30 odd pages). So, I will now be able to put more into Tutorial2 :-) Howard and everyone else who has contributed: Wonderful job. Brilliant framework. I will be recommending this to people within my team (work) and anyone else I meet who does web application development. It's the best framework I've evaluated so far. Time to celebrate with a nice glass of red wine :-) - -- Regards, Neil Clayton (PS: If you see strange text you don't understand underneath my email, don't worry - it's just my PGP signature) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9qaRSLXcfQF3yrNoRAhYhAJ9lEH24AJQ2Ewt7KHzI18co2BfxLQCgu/WB 53WWdvD96dUiYRCk5kw9vE0= =gZxR -----END PGP SIGNATURE----- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
