I think some sort of a wizard that automatically packages a
component and its dependencies into a library would be nice too. It's not
exactly *hard* to build a library manually, but it is an extra step. I think
libaries would be easier to trade around of they were the "default"
packaging option.
As it is though the default (for me at least), is just to put my
components inside my main source tree along with my page classes. Then if I
want to share a library I have to yank them out, refactor, etc.
I wish there were a way to either A) automate the process or B) make
all components inherently sharable as-is without having to go through the
library packaging step.
--- Pat
> -----Original Message-----
> From: t.n.a. [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 05, 2005 11:55 AM
> To: Tapestry users
> Subject: Re: About a bigger Tapestry components library!
>
> Pablo Ruggia wrote:
>
> >This is not a Tapestry problem. It's the community (me included) the one
> >that should contribute with those components. I've created several
> >components and never upload them anywhere. I think you guys are in the
> same.
> > I think what we need is a more "official" site where to upload
> components,
> >and not personal attemps like tassel or tdelli. Perhaps a Tapestry
> >subproject or something like that.
> >
> >
> Ditto.
> An official feel to it is a must (through user) and a short quick guide
> to component contribution should be very visible so contributing isn't a
> problem.
> I like the official component repository, although I'd prefer more
> examples, both simple and advanced. If upload and versioning
> capabilities were added to it, I believe we'd have something to work with.
>
> Anyway, I'd be willing to contribute if I could focus on component
> design instead of what to do with the code it once it works the way it's
> supposed to.
> Untill then, I'm eager to hear where we'd host this repository and how
> (ftp/cvs/wikis or some other way).
>
> t.n.a.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
