Hi Dario. It definitely doesn't _have_ to be a "killer component"!
Firstly, I decided to publish AnySubmit and LinkSubmitOrSpan on Tassel because I figured these little 'corner' use cases would be common. I'm sure everyone has a little component like this, or a renderer or something that would save someone else some time. So give it away! The reasons you suggest are all quite likely. Luckily I work for a pretty relaxed company (WRT licensing). Lack of time is something we all struggle with - it just takes some prioritising, and perhaps a decision to give something (anything!) back to the OS community. For me the barriers would be the "not generic enough" one and also that I simply don't know much javascript. (Nor do I care to.) Lastly, if we improve someone else's component, we should make time to contact them about releasing the improvements. (It would be nice if Tassel made it easier to host variations of existing components.) We shouldn't just create components, but also improve the ones we already have - even those in the framework. Everyone get to it! ;-) Cheers, Nick. Darío Vasconcelos 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... In my case, I'm still a newbie, and I still haven't build a killer component that might be useful for people other than me. Regards, Dario
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
