What’s the best way to contact you? You can email me: andy at stonean. com

thanks again!

To support different component generators for each framework, use a different subfolder in your gem. E.g. rails_generators/lockdown – is a script/generate lockdown generator for rails. sinatra_generators/lockdown would be where you’d put your lockdown generator for a sinatra app.

Based on the context of where you then ran “script/generate lockdown” or “rubigen *scope* lockdown” (though the latter is new, and I’m thinking of changing it to “rubigen lockdown *scope*”) the particular generator would be run. As another example, inside a newgem project the “script/generator” looks for generators in “rubygems_generators” folders of install gems. “rubigen rubygems xxx” would do the same.

I don’t yet know how Templater solves this issue (diff generators for different scenarios). I hope I can find time to play with it soon and experiment.

Lockdown seems like a cool project. If you want help with your generators, I could perhaps help and I might find some nice extractions to put back into rubigen (subclasses or new APIs etc).

So many projects to play with and only so much time :)

Thanks for your comments and I appreciate your efforts to improve both NewGem and Rubigen, I’ve followed both for a while now.

My main concern with Rubigen/Rails generator is the association with Rails framework. For the purpose of Lockdown, I need a generator that is framework agnostic. Even though Merb + Rails are merging, I would like (one day) to have Lockdown work with Mack, Sinatra, and all Ruby frameworks that want the functionality. So, it’s not important to me to have it recognized with script/generate.

I’m not sure if Templater is my answer, but it looks like it is following this path. If this turns out to be false, then I’m not sure. I know Haml support is not there yet, and that is a concern.

I’m sure my ideas of what I want and what actually works well will change as I refactor this functionality. I’d be happy to share my feature needs as I go through this process. I don’t know if my requirements for Lockdown are typical, but I would imagine there is a common feature base everyone needs in a generator.

Looking at your lockdown app_generator, http://github.com/stonean/lockdown/tree/master/app_generators/lockdown/lockdown_generator.rb, I think we could come up with a nice subclass of RubiGen::Base for app generators that would make our code here much smaller.

I also want a “just clone/template over all the files in my templates/ folder, please” function for generators. I think Yehuda and/or Hassox suggested this idea to me when they were working on Merb generators before moving to Templater from RubiGen.

From your experiences, and not many ppl write generators so experiences are hard to find, what else is unclean/could be improved/is deficient in rubigen/rails_generator?