In this point I think is *very* important to have a design plan for
Tapestry. Probably the main cause of going from beta to beta is random
API changes because of the "this is better..."... "no! this is even
better!" ... "no, that was broken, it doesn't support X"...etc cycle.
A release plan can help us in this respect. Separating the frameworks in
several mostly self-contained parts also helps. For example, I propose
the following separation of Tapestry:
- Tapestry-Core
- Tapestry-Annotations
- Tapestry-Portlets
- Tapestry-Components
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
