On 2/24/07, Chuck Vose <[EMAIL PROTECTED]> wrote:
> Why can't we have a generator anymore? It still seems like a good idea
> if just to show people what a good structure is anymore. If nothing it
> sets up the testing directory which the plugin generator doesn't have
> at all.

While I like that rails (and the old generator) prompts you to test by
producing a test directory, this can't be the only thing that
convinces you that you need to write some tests. More often than not,
the test directory (and the others: public, db/migrate, etc) would
just be ignored if they were unwanted.

This is why I dropped the generator - too often we'd end up with
plugins that had a public/ directory tree that was completely empty,
or a functional tests directory that just wasn't relevant, but was
hanging around regardless. This is one of the reasons that "engines"
were perceived as heavyweight, and I doubt anyone can have avoided my
"engines are dead, we're all just lightweight plugins now"
near-ranting.

I guess ultimately I feel that the generator helped *too much*, to the
detriment of the project. I'm sorry that you are feeling its absence,
but creating only the directories that *you* need isn't too bad is it?

-- 
* J *
  ~
_______________________________________________
engine-developers mailing list
[email protected]
http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org

Reply via email to