Hi Peter, Plugin load order will feature in 1.2, which makes things a lot easier (politically, at least) for people who want to use the engines plugin; more about that later. As for the other features.... it's tricky. It's often far simpler to monkey patch a feature in, than it would be to provide a complete 'proper' patch that Rails could adopt. Other aspects, such as the 'code mixing', are fairly magical, and not suitable for core at all, imho.
A lot of the work in the engines plugin is providing a better infrastructure in which plugins can operate - creating object instances to represent plugins, and so on. Some of these might be 2.0 candidate features; we'll see what David's plans are for that as time goes on. As for defining models in plugins - what do you feel is the main difficulty? - james On 12/30/06, Peter Michaux <[EMAIL PROTECTED]> wrote: > Hi, > > It seems like DHH has never built almost the same site twice as he > won't embrace the idea of engines into Rails. What changes need to be > made to Rails API so engines don't need to monkeypatch their way in? > Is there a way that patches could be phrased so they look appealing to > the Rails Core team in other ways and thus be applied? One thing I'm > particularly interested in engine/plugin loading order but from > reading on the engines site it looks like that is now a feature in > Rails core. Is there any movement on trying to make defining models in > an engine a little smoother? > > Thanks, > Peter > -- > Fork JavaScript: http://forkjavascript.org > _______________________________________________ > engine-developers mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org > -- * J * ~ _______________________________________________ engine-developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
