Tassel is a great asset to the Tapestry community. It's a shame it's not listed as one of the "Related Projects" from the Tapestry homepage.
It's also good that it contains components from other projects, showing that this is a good way to distribute in a centralized, non-exclusive way. Live component demos, or at least flash movies, would be useful in the context of a larger official, and thus vetted, component collection - similar to contrib, I guess. Open submissions shouldn't be live. But it would be nice if all of this was easily accessible out-of-box. Cheers, Nick. ----- Original Message ----- From: "Robert Zeigler" <[EMAIL PROTECTED]> To: "Tapestry users" <[email protected]> Sent: Thursday, 7 July 2005 6:16 a.m. Subject: Re: About a bigger Tapestry components library! > As the sole maintainer of Tassel... ;) > I agree. I think Tassel has been at least a moderate success; > it has 25 components or code-contributions in it, which have been made > over the one year. It would be nice to see the various repositories > combined. It would also be nice to see the functionality of any one off > the repositories expanded. Maybe it's my bias, but it seems that Tassel > currently provides the best base in terms of providing general users the > ability to upload their own components. > Someone mentioned an enforced format; I deliberately made Tassel very > flexible in the format it accepted because I feel that enforcing a > format is a barrier to getting components "out there". > On the other hand, I've been contemplating revamping some of Tassel's > internals to take non-standard input and produce standard output > (primarily producing proper component-libraries with palette plugin > support). I've also been toying with the idea of making a sort of > "ala-cart library" functionality which would let a user select a set of > components and package them all into a single library. > Unfortunately, I've just moved 1/2 across the United States and am > currently without Internet access (writing this from a local shop with > free WIFI :). I'm also in the middle of a major project at work, and > really don't have the time to spare right now. > I'd be happy to create a "tassel" sourceforge project to enable other > people to have access to the source, contribute patches, etc. > Tassel, itself, would continue to be hosted at its current location. If > someone is willing to handle the domain registration, $$, etc, I could > talk with the folks who kindly host the project about having another > domain name pointing to the server and getting a virtual-host setup for > it. > Someone mentioned having "live" component demos... I've thought about > that quite a bit... initially it seemed like a good idea, but upon > further thought, I decided I didn't like it. It's nice for the user, but > consider that you would essentially be opening up your server for the > execution of arbitrary java code with the permissions of the > servlet-runner user or whatever amount of sandbox has been placed on the > webapp, itself. But maybe there could be a url to a demo site and have > an iframe render the demo site for the component, or something along > those lines? > > To sum up, I think that starting yet another library project from > scratch is less than a good idea. Consolidating the existing ones is a > great idea. :) > > Robert Zeigler --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
