[eluser]kilishan[/eluser]
herrkaleun - I'll look at it as I have time this week. It's going to be a busy week though, since I've got a site launch on Friday that still has a bit that has to be tested and tweaked.
Jonas - Good catch. That was a hacky way for me to implement that, wasn't it?
I'll fix it as I'm working on the next release.
For those that are watching this project, here's the roadmap, if we're calling my previous version 0.1. Note that this is just referring to the generate/destroy scripts themselves, not the generators that come with it.
0.2 - Integrate into CI so that it can be used from either the command line or through a web browser. I've figured out how to do this, just have to implement it.
0.3 - Allow generators to call other generators.
0.4 - Create a "hooks" system for the generators. This will allow users to pick and choose which libraries they want to be used during generator processing. For example, if you have 4 different view libraries installed, you can specify in the config file which view library is used for the controller generation (or anything else that might need to use it). Then, when the controller generator is running, it calls the appropriate hook to create that "show view" command (or "add data to view" command, or whatever.) Still working out the best way to handle this.
0.5 - Integrate the Spyc YAML parser into the system so that we can use YAML for the generator instructions, instead of the nested arrays that it currently uses.
That's all that's on the map for now. The rest will be creating usable generators that are complete enough to be used, but flexible enough that they're not a pain to modify.
If anyone has ideas they'd like to see incorporated speak up. While I'm doing this primarily for my own use, I want to make it flexible enough that it can benefit everyone.
