I mentioned this on the Rails general mailing list, but I thought I''d mention it here because I''m hoping for some action from the core team on this. At the end of David''s presentation at CanadaOnRails there was some discussion about needing a better resource for plugins than the current wiki page. Since I had been wanting to do exactly that for a while, I decided to get off my rear and do it. The new directory is up at http://www.agilewebdevelopment.com/plugins, with the ability to search for and rate plugins. I''ve sucked most of the plugins over from the wiki page, and I''m working on filling out the rest of the missing information (detailed descriptions, plugins missed by my scrape, etc.). I will also be adding some functionality suggested on the Rails mailing list. However, the directory is functional enough at this point to be useful to the Rails community, and I wanted to check with the core team on the willingness to use it in place of the wiki page. I have made a scrape-friendly URL that can be used by the plugin command-line script, and I''d like to have it added to the default list of URLs that get scraped by the plugin script (line 630 of plugin.rb). This will allow for an easy migration of Rails users to the new directory. Thoughts?
Funny, I''m about to launch one as well for freshrails. If you provide an xml feed that lists the most recent plugins added, then I''ll integrate pointers to your directory instead. -San --- Benjamin Curtis <rails@bencurtis.com> wrote:> I mentioned this on the Rails general mailing list, > but I thought I''d > mention it here because I''m hoping for some action > from the core team on > this. > > At the end of David''s presentation at CanadaOnRails > there was some > discussion about needing a better resource for > plugins than the current > wiki page. Since I had been wanting to do exactly > that for a while, I > decided to get off my rear and do it. The new > directory is up at > http://www.agilewebdevelopment.com/plugins, with the > ability to search > for and rate plugins. I''ve sucked most of the > plugins over from the > wiki page, and I''m working on filling out the rest > of the missing > information (detailed descriptions, plugins missed > by my scrape, etc.). > I will also be adding some functionality suggested > on the Rails mailing > list. > > However, the directory is functional enough at this > point to be useful > to the Rails community, and I wanted to check with > the core team on the > willingness to use it in place of the wiki page. I > have made a > scrape-friendly URL that can be used by the plugin > command-line script, > and I''d like to have it added to the default list of > URLs that get > scraped by the plugin script (line 630 of > plugin.rb). This will allow > for an easy migration of Rails users to the new > directory. > > Thoughts? > _______________________________________________ > Rails-core mailing list > Rails-core@lists.rubyonrails.org >http://lists.rubyonrails.org/mailman/listinfo/rails-core>__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Hello Benjamin, 2006/4/21, Benjamin Curtis <rails@bencurtis.com>:> Thoughts?Little bug. On http://www.agilewebdevelopment.com/plugins/show/16, click Jonathan's name. You end up on Emanuel's page... Nice stuff, and I like the design too. I'm missing the part of the brain which understands how to choose colors :( Bye ! -- François Beausoleil http://blog.teksol.info/ _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
> If you provide an xml feed that lists the most recent > plugins added, then I''ll integrate pointers to your > directory instead.Get Simply Restful (http://dev.rubyonrails.org/browser/plugins/simply_restful/README) and provide an XML interface for it :) This would allow not only script/plugin, but other tools to integrate it. Think about possible Textmate or RadRails plugin interfaces... I did a plugin repo several months ago (http://svn.techno-weenie.net/projects/plugin_repo/) with similar thoughts. But the thing is, I just don''t use script/plugin discover all that much. It''s easy to add svn sources and install plugins currently. However, one area a repository might be useful is listing plugins that don''t live in svn repositories (or provide only tars/zips). For now, I wouldn''t be opposed to setting alternate script/plugin discover points. -- Rick Olson http://techno-weenie.net
There is a feed of plugins as they are added at http://www.agilewebdevelopment.com/feeds/plugins. There is also an XML list of all the plugins at http://agilewebdevelopment.com/plugins/script_list. sanzbox@yahoo.com wrote:> Funny, I''m about to launch one as well for freshrails. > > If you provide an xml feed that lists the most recent > plugins added, then I''ll integrate pointers to your > directory instead. > > -San > > > --- Benjamin Curtis <rails@bencurtis.com> wrote: > > >> I mentioned this on the Rails general mailing list, >> but I thought I''d >> mention it here because I''m hoping for some action >> from the core team on >> this. >> >> At the end of David''s presentation at CanadaOnRails >> there was some >> discussion about needing a better resource for >> plugins than the current >> wiki page. Since I had been wanting to do exactly >> that for a while, I >> decided to get off my rear and do it. The new >> directory is up at >> http://www.agilewebdevelopment.com/plugins, with the >> ability to search >> for and rate plugins. I''ve sucked most of the >> plugins over from the >> wiki page, and I''m working on filling out the rest >> of the missing >> information (detailed descriptions, plugins missed >> by my scrape, etc.). >> I will also be adding some functionality suggested >> on the Rails mailing >> list. >> >> However, the directory is functional enough at this >> point to be useful >> to the Rails community, and I wanted to check with >> the core team on the >> willingness to use it in place of the wiki page. I >> have made a >> scrape-friendly URL that can be used by the plugin >> command-line script, >> and I''d like to have it added to the default list of >> URLs that get >> scraped by the plugin script (line 630 of >> plugin.rb). This will allow >> for an easy migration of Rails users to the new >> directory. >> >> Thoughts? >> ____________
On Apr 22, 2006, at 12:51 AM, Rick Olson wrote:>> If you provide an xml feed that lists the most recent >> plugins added, then I''ll integrate pointers to your >> directory instead. > > Get Simply Restful > (http://dev.rubyonrails.org/browser/plugins/simply_restful/README) and > provide an XML interface for it :) This would allow not only > script/plugin, but other tools to integrate it. Think about possible > Textmate or RadRails plugin interfaces...Very nice, Rick. I''ll be using this one in the next week or two. -- Jason Perkins jperkins@sneer.org "The computer allows you to make mistakes faster than any other invention, with the possible exception of handguns and tequila." -Mitch Ratcliffe
Francois Beausoleil wrote:> Hello Benjamin, > > 2006/4/21, Benjamin Curtis <rails@bencurtis.com>: > >> Thoughts? >> > > Little bug. On http://www.agilewebdevelopment.com/plugins/show/16, > click Jonathan''s name. You end up on Emanuel''s page... > > Nice stuff, and I like the design too. I''m missing the part of the > brain which understands how to choose colors :( > > Bye ! > -- > François Beausoleil > http://blog.teksol.info/ >Thanks for the bug report. I''ll try to fix that up in a jiffy. :) The template is one posted at http://openwebdesign.org/ by Andreas, who has a number of excellent free templates. The color scheme came from some color scheme site (that I can''t recall at the moment), which gave complementary colors after I settled on the color for the header.
Rick Olson wrote:>> If you provide an xml feed that lists the most recent >> plugins added, then I''ll integrate pointers to your >> directory instead. >> > > Get Simply Restful > (http://dev.rubyonrails.org/browser/plugins/simply_restful/README) and > provide an XML interface for it :) This would allow not only > script/plugin, but other tools to integrate it. Think about possible > Textmate or RadRails plugin interfaces... > > I did a plugin repo several months ago > (http://svn.techno-weenie.net/projects/plugin_repo/) with similar > thoughts. But the thing is, I just don''t use script/plugin discover > all that much. It''s easy to add svn sources and install plugins > currently. However, one area a repository might be useful is listing > plugins that don''t live in svn repositories (or provide only > tars/zips). > > For now, I wouldn''t be opposed to setting alternate script/plugin > discover points. > > -- > Rick Olson > http://techno-weenie.net >I responded to the original email about XML versions of the data that are already in place, but I certainly don''t mind adding a simply_restful version. :)