On Jan 24, 2007, at 5:20 AM, James Adam wrote: > On 1/24/07, Wybo Wiersma <[EMAIL PROTECTED]> wrote: >> I think this is quite sad, as sharing engine-code the Open Source >> way is in my view still a superior use. Eventhough I do agree that >> the >> login_engine was crap in terms of the coding & session-handling. >> Still >> it could have been fixed... And nevertheless I do bilieve that sooner >> or later as the Rails community grows shared engines will re-emerge. > > I think "crap" is a bit strong! > > The reason they're not being publicly migrated up to 1.2 compatibility > is threefold: > > 1. they smell bad and people have developed - for whatever reason - > negative feelings towards them; > 2. they distract from the point of the engines plugin, which is to > make it easy for YOU to develop powerful plugins; and > 3. so that *other people* can fill the void with their own open-source > plugins, using the engines plugin enhancements if they feel it's > useful. We'll be writing our own replacement internally, which may or > may not be released. > > Also, in case you hadn't picked up on it, no such thing as an "engine" > anymore. The login_engine would have to become the "login plugin", if > anyone tweaks it to work with engines 1.2 :)
I guess the bigger question for some of us (myself included) that have dependencies on this is: what now? Pull the code into my project and maintain it myself? And for me, it's not just login engine, but also user engine. I suppose I'll just roll it into my app and make the necessary changes. Thx for taking things this far. -j _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
