On Dec 12, 1:18 pm, mwlang88 <[email protected]> wrote: > Ok, there wasn't an overwhelming response to my query, so I have gone > ahead and setup a github repository for the Tree plugin. As I will > more than likely develop other plugins as time goes on, I opted to go > with a generic "sequel_plus" name. > > The gem has been released to gemcutter as "sequel_plus" > Source is available on github: http://github.com/mwlang/sequel_plus > > If others have plugins or extensions they'd like to include, just > fork, add yours and relevant tests (I'm using Bacon tests for the Tree > plugin) and send me a pull request.
You should rename this to sequel_tree, so that you don't need users to require 'sequel_plus' separately first. If you rename it to sequel_tree, they can just call plugin :tree, and it will require the plugin for them. I understand your reasoning about developing other plugins, but I would recommend using separate gems. If you really want to keep everything in a single gem named sequel_plus, at least have a file named sequel_tree in the lib directory of your gem that just loads the sequel_tree part, so that the plugin automatic loading can still work. Also, do you want me to add this to the plugins.html page on the website? Jeremy -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
