On 8/5/05, Darío Vasconcelos <[EMAIL PROTECTED]> wrote: > Since everybody is building components so easily, why are the Tapestry > repositories (Tacos, Tassel, t-deli, etc) kind of empty? Licensing > issues? Components that are not generic enough? Lack of time? Fear of > finding too many newbies asking basic questions (contrib:Table comes > to my mind)? I guess all of you agree that a diverse and heavily > populated component library would be a good thing for TP... >
To create a truly useful, reusable component, to package it, and to support it, can be daunting. What might be nice is a TapestryForge to solve most of the structural issues (i.e., provide a SVN repository, downloads, etc.). I'm not ready to take on the expense and time of creating that kind of thing, not at this time. -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
