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 Jamie Orchard-Hays wrote: > It seems to me that what we need to do is combine the component > libraries into one place. Also, if none of those sites has all that's > needed, expand the new site's capabilities. > > We should probably move this discussion over to the developer list as well. > > Jamie > > Ron Piterman wrote: > >> +1 >> What I noticed is that many times you have to create components which >> are trivial, but are not there. >> >> Examples: >> A Date component consisting of three Inputs instead of the JavaScript >> one. >> A Property Selection which submits also on disable. >> A Property Selection which shows values depending on another property >> selection. >> aso. >> >> >> >> Tassel is at the moment a good repository, but has very limited >> functionality. >> >> I think a repository which is something like the eclipseplugins.org is >> needed, + enabling hosting of components, improved documentation, >> example and download of each component. >> >> I wish I had the time to help realize such a site... >> >> >> >> ציטוט Juan Esteban Maya: >> >>> I have been working with tapestry for almost 3-4 months and its really >>> nice. The development process and the productivity incressed a lot. >>> But what i really miss (well i wish) is to have a big and robust >>> component library. >>> >>> This has been already discussed in the mailing list, but i guess it >>> deserves more attention. JSF, which i think is the biggest Tapestry >>> competitor has already a lot of Subprojects, componentes libraries, >>> even comercial ones(Well, yes is sun i know!) and i havent seen a new >>> tapestry Components in a while. I think this issue is fundamental to >>> new tapestry users. If i have to choose a new component technology the >>> first thing that i will look are the components that the technology >>> can offers...Tapestry is clearly behind JSF in this aspect. >>> >>> Any thoughts about how can we, Tapestry users, have big component >>> library? Not just a repository. >>> >>> Juan >>> >>> --------------------------------------------------------------------- >>> 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] >> >> > > --------------------------------------------------------------------- > 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]
