OK - I think I've figured out a reasonable way to support legacy behaviour, but also make the progressive changes that I want Engines 1.2 to support.
*IF* you need to control the load order of your plugins, then keep the current convention of replacing init.rb with init_engine. Engines.start can then be called to load these plugins in a specific order. However, I'm not going to be promoting the 'Engines.start' behaviour anymore - consider it a "secret" feature until Rails fixes their plugin loading system such that it respects orderings. - James On 12/9/06, Peter Michaux <[EMAIL PROTECTED]> wrote: > On 12/8/06, Henry <[EMAIL PROTECTED]> wrote: > > Oh yeah, I forgot to mention: one of the reasons we love engines so > > much is that we can control the load order! For what it's worth, I > > think it's a horrible idea not be able to control it. We have > > several instances where we need engine x in before y ... am I the > > only one? > > I have engines that must load in a particular order. That is one great > thing about engines. I can add functionality to layers of a Rails app > like subclassing a class in oop programming. > > I hope that order of loading stays. I wish it was a rails core feature > where specified plugins load in a particluar order and then the > remainder of plugins load in any order. I don't know why the Rails > core won't let developers shoot themselves in the foot if that is what > they think it is doing. > > I wish engines were in Rails core too :) > > Peter > _______________________________________________ > 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
