Sounds like a great idea. I'd also suggest a region where people can suggest new components, and these can be discussed and voted on, so that those who want to can choose a project that will have the greatest impact.
On 23 June 2011 10:27, Bob Harner <bobhar...@gmail.com> wrote: > I agree that the main need is for a registry, rather than a > repository. Coincidentally over the last several days I have been > thinking about how a "component registry" app could work to solve > these sorts of code locator issues. It could include modules as well, > but my focus here has been on components. > > There are currently at least 150 (!) Tapestry components and mixins > available out there (Tapestry-core components, collections like > ChenilleKit, Equanda, Ioko, Lombok and TapX, blog posts like those on > tinybits.blogspot.com and several MoinMoin wiki pages), but there is > no master list of the components and mixins available across all the > modules. The http://wiki.apache.org/tapestry/Tapestry5ModuleRegistry > and http://tapestry.apache.org/third-party-modules.html pages do > provide simple lists of modules, but there is no "component finder" > tool anywhere. > > This is what I'm considering. Tell me what you think: > > * A database-driven web app using Tapestry and Apache Cayenne, > Tapestry-security, Apache Shiro (hey, all Apache products) > > * A light, carefully-designed, AJAX-based, highly componentized UI. > Definitely NOT something slapped together and half-baked, but really > serious and complete. > > * Copy the CSS of the new Tapestry documentation site. > > * Would have, for each component, the name, brief description, > license, Tapestry version compatibility, links to similar components > (e.g. JumpStart's Textbox Hint mixin is similar to Lombok's Watermark > mixin), maybe a small screenshot, a link to the component's > documentation, and a link to the component's demo page, if any. > > * Searching, sorting and filtering. For example, be able to search for > "editor" and find ChenelleKit's Editor and InPlaceEditor, as well as > Kenai's CKEditor and FCKEditor components. Or choose a specific module > and list all of its components. Or list only mixins. Or only > components with Apache 2.0 licenses. > > * Some sort of rating system reflecting the component's code quality, > design, and freshness. > > * Anybody could submit a new component for consideration, but only > certain designated people (committers?) could approve the listing. > > * Use Tapestry-security to manage authentication/authorization. Can we > tie this to Apache's LDAP so that committers can use their existing > accounts? > > The goal would be to complement JumpStart and other resources, rather > than competing with them. For example, for Tapestry's Palette > component, the demo link would go to > > http://jumpstart.doublenegative.com.au/jumpstart/examples/component/coreinputcomponents > . > > * Hosted somewhere at apache.com, perhaps in the Apache Jail like > Hotel Booking (not sure of the implications there). > > * Source code in apache SVN. > > As a Tapestry app, it should be a very high quality public showcase > for the best that Tapestry can do. > > Anyway, that's my goal. I'm starting on it today. Any ideas? > > > On Wed, Jun 22, 2011 at 1:47 PM, Lenny Primak <lpri...@hope.nyc.ny.us> > wrote: > > Yes, this is the old question of keeping the ecosystem as pure as > possible. > > I don't think it matters as much where it is hosted (apache etc) > > it could very well be hosted on github, > > but there should be only one place, one list, perhaps with subsections, > > and the voting idea is also a good one to get on that list, > > but it should be number one result in google :) > > > > On Jun 22, 2011, at 1:37 PM, Howard Lewis Ship wrote: > > > >> I would prefer two real centers. For licensing reasons, much code can > >> not be hosted at Apache. In addition, my big concern is "dump-and-run" > >> code (which we've even seen with Tapestry committers in the past). We > >> don't want to be responsible for more code than we can support. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
