Hi James, I think this is a good idea because 1 - makes the code more readable 2 - avoids to create an heavy and dangerous legacy for future development of the engines concept 3 - does not really have a dark side (Not that I can see. Can anybody mention one?)
In general I think that the philosophy behind the engines should be to create pieces of really reusable SW more than go on the "black magic" path, as Nick points out. In this sense I would even suggest that we should get in the habit to __dedicate a namespace to our engines__. If, for instance, I write a todo_list_engine, I probably want my contoller to be called TodoList::ItemController, otherwise whoever wants to use my engine has to make sure that there are no other ItemController in his/her application. Would this make your work with the engines plugin more complicated? What is your opinion? Rails at the moment is not really supporting (not easily at least) namespace usage on the model side. This is, in my opinion, the major problem to be faced for the estabilishment of a sound engine concept. Mauro -- Posted via http://www.ruby-forum.com/. _______________________________________________ engine-developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
