It might look superflous, but I found rather cumbersome to have the documentation with tapestry and vlib mixed up. I think that having them completely separated would be better,in fact as time passes vlib should show better and better, the let's say 'local oddities' should gently promote to the framework, like for examply the EntitySelectionModel, it answer's a clear need not in vlib but in general, and thus it shall promote.
After all framework enhancements rise for solving better concrete problems, vlib has to be seen as the test case that shows framework reaction and improve over time. The same functionality but with less and less oddities,until no one will doubt, it's perfection. __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ------------------------------------------------------- This SF.NET email is sponsored by: The Best Geek Holiday Gifts! Time is running out! Thinkgeek.com has the coolest gifts for your favorite geek. Let your fingers do the typing. Visit Now. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
