On Dec 12, 2005, at 4:27 PM, Leonardo Quijano Vincenzi wrote:
1) This is no minor documentation typo that needs to be fixed.
Whole areas of Tapestry development are not documented, and some
are confusing. How would expect Tap4 getting adopted more
pervasively if the docs miss some important areas?
Ah, then I agree that this is an important issue to address pre-
release. Perhaps just removing the incorrect documentation and
adding pointers to the working example application would be a
sufficient first start.
2) Delaying the release until docs are done ensures that those docs
gets written. If not, well, it may happen like in Tapestry 3, with
2 user guides, both incomplete... for a long time. Now I recall
that was one of my main reasons for not adopting Tap 3 when I
tested (along with the .page files).
I agree that it was annoying in Tap3, but my mode of use of open
source projects is likely very different than most. I pull down the
code, look at the example application, browse the .jwc files of the
built-in components to figure out how they work, and just generally
get deep under the hood.
Let the users will prevail!
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
