-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Interesting post, which I agree with. I have had the same exact experiences with Tapestry in terms of discovering it, and then learning more about it. It's actually the reason I have decided to contribute to the documentation.
Also, I am very, very interested in contributing these exact types of components back to the project. It's things like these that I think will place the icing on the cake, so to speak, with regard to this framework. In terms of convicing people that Tapestry is a viable alternative to framework X; being able to examine it, see that it does provide an elegant solution, but that it ALSO provides most common building blocks cannot be underestimated. If tapestry had the docs + nav / tree components, my personal view would have been sealed as I read through the contents page! I'm not necessarily sure that the components have to be Howards responsibility however. I think that it would not take many Tapestry developers (I dunno, I'm guessing about 4? surely that cannot be hard to organise?) very long at *all* to create these, and contribute them back. I for one would certainly be up for helping! (Completing the Tutorial documentation will come first for me however) Neil On Wednesday 28 Aug 2002 8:44 pm, Peter A. Cassetta wrote: > This is my first post, and I'll keep it brief. > > First of all, congratulations to Geoff. I have 4 kids (with one on the > way). I hope you have as much fun as I have these last 7 years with the > kids. We don't go out to movies or out to eat anymore, but we have a blast. > > I've been evaluating Web frameworks for an upcoming project. Tapestry is > the most elegant (and amazing) one I've come across. On this particular > project, JSP is really required for the view so I can't go with Tapestry. > For now I'll just keep it in mind until another project comes along. > > Mostly I want to concur with everything Malcolm Edgar said. The learning > curve for Tapestry is significant, so the work in progress on > documentation/tutorials will be key. > > Second, I was surprised there are not more high-level components available > for Tapestry. I don't think this is Howard's responsibility. Anybody really > using the framework will probably be developing navbars, hierarchical tree > views, calendar/date controls, etc. Let's hope some folks begin > contributing these items back to Tapestry. A rich set of solid, > browser-neutral components would fill the only real gap in the framework. > In fact, a nice set of high-level components that works well across all > browsers is hard to find anywhere today. I've played with various ones, and > they all have their drawbacks. Tapestry would be an irresistable tool with > a stronger set of UI components. > > Keep up the great work everyone. > > Pete Cassetta > [EMAIL PROTECTED] > > > ------------------------------------------------------- > This sf.net email is sponsored by: Jabber - The world's fastest growing > real-time communications platform! Don't just IM. Build it in! > http://www.jabber.com/osdn/xim > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer - -- Neil (BTW: If you see weird text surrounding the message and you don't know what it is, don't worry, it's just my public PGP signature). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9bS3bLXcfQF3yrNoRAvbZAKCJa3Ghta3WfrCui2QaPkHsN3M38QCfXLCj pqrCQbR2J+/uRLNnofaKQ+k= =Bv8K -----END PGP SIGNATURE----- ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
