this is cool, although i still think this should be auto-updated through a maven registry crawler. if everyone put the right meta information in their wicket jars, this resource registry would be entirely automatic, always fresh, running demos, etc...
francisco treacy-2 wrote: > > i came up with an idea during the last weeks, having some trouble > finding wicket resources. > > although we have wicketstuff (which is great, and even more now with > jeremy's awesome job of reorganizing it) i feel there are still lots > of components, plugins or tools that are lost in cyberspace. thought > it would be neat to keep a sort of "registry" with useful information > for wicket developers. > > so i decided to quickly put some bits together from an old project and > rebaptised it as "the wicket hub" - a simple prototype @ > http://wickethub.org. > it's meant to be flexible, so except for the title there are no > required fields when you add/edit a "module". there are already some > examples. > > let me know what you think about features, its relation with > wicketstuff and if it's usable, etc. or even if the whole thing makes > no sense - any suggestions appreciated. > > francisco > > ps: goes without saying, but [disclaimer: it's completely > experimental] and be aware the place it's hosted is more like a > shoebox than a server :) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/wickethub.org-tp20995774p21022737.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
