Thanks for your note Neil. Here are a few more thoughts. I agree that the components shouldn't be Howard's responsibility (unless he just wants to work on them). But he has enough else to do.
If you do form a committee of developers to work on these things, try to get some input from a designer too. These are user-interface components, and they need to look good. One thing I appreciate about Tapestry now is that you can actually run a Tapestry app (the Workbench) before even downloading the package. It's quite impressive, and I'm sure it helps to "set the hook" for potential developers who come along and take a glance at Tapestry. As high-level components are developed, it will be important to showcase them in the Workbench or elsewhere _ONLINE_ as well. I'd be interested in contributing if I were using Tapestry, but right now I'm not. If that changes, I'd certainly contribute components back. If JavaServer Faces ever gets to a public review stage, it would be good to make sure Tapestry has a comparable set of components. There are a few other component sources that could be mined for ideas (I hear Microsoft's Visual Studio.NET has a very good selection of components, though I don't have any experience with it). Thanks for the work you're doing on the tutorial now. I'll look forward to reading it one day. 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
