@Priit: That’s next on the list. The itch I was scratching was the initial generation of CSS, but I’ll probably hack together an updating generator quite soon.

It’s nice to generate, however it would be much more useful if you want it to take next level and make it as the way of updating css (like ultimately using rake task ‘rake css:update’). If you have used Gettext then you know what I mean. “The gettext way” of harvesting source and updating po fails is really useful and the facto standard to manage your po fails.

Don’t know yet if “the gettext way” will be as useful for css in practice, but if you willing and have time to try, it would be cool to see how useful it will come.

BTW, if your plugin is just containing a generator then you can gemify the generator. Basically, make your plugin a gem, and move everything in generators/ into rails_generators/ (and explicitly add the lib/ folder to $LOAD_PATH) Rails 2.0 apps will find this generator automatically, and ppls won’t need to install the plugin into each app.

Let me know if that doesn’t make any sense :)