Re: [Tapestry-developer] This Tapestry stuff is hard.

[Jorge]

[Repost with subject] On Thursday 05 December 2002 15:05, [EMAIL PROTECTED] wrote: > We're approaching this on two fronts. The TapestryLite enhancements will > make adoption of Tapestry much easier. Neil's improved Tutorial looks very > good as well. I'll be redoing much of the Developer's Guide (and renaming > it to User's Guide) at some point as well. But as MindBridge has pointed > out ... nobody reads the docs. Excellent. But I disagree with you when you say that no one reads the docs. Reading the docs (or at least glance trough to them) and looking to the screenshots is the first thing I do when deciding if a software product is worthy of a download :-) It was because of the docs that I've choosen Tapestry over Enhydra-Barracuda and Zope-ZPT(Page Templates)[1]. I will concede however that sometimes the need for instant gratification makes me "jump to code" without reading the docs carefully enough. ... did I just contradict myself?! Can make I a suggestion about the future re-write of the documentation? I find the UML "Interaction Diagrams" informative, but I still fight sometimes over which method should I override. It would be cool to have some annotations side by side with the diagrams that illustrated when to override the methods, something like: AbstractPage - renderPage() -> The developer should override this method when (...) Right now this information is somewhat scattered over the JavaDocs. > > > I truly believe that there are more hidden pearls in the Framework > > that are just waiting for me to find them, if only I had a map. > > I'm sure there are. Yes there are. I recently find out the joys of dynamic form handling... this must be the coolest (as in headache prevention "cool") feature of Tapestry so far. Jorge Chandra [1] - There is a great deal of overlap between Tapestry and Zope Page Templates. Tapestry has OGNL, ZPT has TALES, Tapestry has Borders, Blocks,Shells .. etc, ZPT has Macros. I think that Tapestry could "steal" some of of ZPT ideas. For example, instead of the fake "jwcid" attribute ZPT uses a XML namespace:

1

Book

$25.50

The use of XML namespaces (the tal: thingy) allows a great deal of flexibility, and its use on Tapestry could eliminate the need of specification files. As I understand it future Tapestry versions aim to eliminate or at least reduce the dependency of the "specification" file, the study of how the ZOPE folks did ZPT could prove useful.

---

No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com