Hi,

I'm currently the primary developer of the Tacos components
(http://tacos.sourceforge.net/). My views are the following (in no
particular order):

- Talk doesn't code :) I have spent significant amount of time on
making some components from a real-world project reusable, somewhat
documented, packaged up, etc. There was very little commercial
incentive in this, other than 1) i can reuse it next time somewhere
else 2) i might get community involvement

- I think the cohesiveness and quality of a component library is more
important than the quantity of components. I'm commited to maintain a
good level of quality and simplicity in the Tacos components (however
I may not have all the free time in the world :)

- I have released a roadmap for medium-term improvements for Tacos
(see http://article.gmane.org/gmane.comp.java.tapestry.user/21283).
You are welcome to join the efforts. Treat these more like guidelines
of course, if you have contributions outside the scope described
there, I can still provide help on where those components would fit
in, etc).

- It might be helpful to feature 3rd party components (t-deli, tacos,
tassel, etc) much more prominently on the Tapestry homepage, so new
users are immediately aware that there are in fact some available

- commercial support would be nice of course: developer time is not
free. I'm thinking about starting funds for certain
features/components (here for example: http://fundable.org/) This way
people can contribute smaller amounts toward a larger goal.

regards,
  viktor



On 7/5/05, Pablo Ruggia <[EMAIL PROTECTED]> wrote:
> On 7/5/05, Jamie Orchard-Hays <[EMAIL PROTECTED]> wrote:
> >
> > There are already two projects:
> >
> > t-deli and tacos
> 
>  You're write. But what they are not "officials". They are just repositories
> where people "throws" their components. What tapestry needs is to have
> components that work in the same way, are constructed in the same way, have
> the sames conventions, etc. There have to be some specification on how to
> create, use and document those components.
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to