[Blacklight-development] separating general from site specific code
rochkind at jhu.edu
Wed Jan 7 14:16:45 EST 2009
Exactly. Rails2.0 already in fact does some of what Engines needed to do
in Rails 1. Engines got smaller between Rails 1 and Rails 2. Sounds
like in future versions of Rails, Engines will get even smaller as Rails
core provides even more of what Engines used to have to do itself.
Matt Mitchell wrote:
> Cool! Very good to know. Jamie you don't miss a beat!
> So, Rails is going to provide better support for "Engines"? It sounds more
> like, Rails *edge* is already doing a lot of what Engines (the plugin) is
> doing. I'll investigate more.
> On Wed, Jan 7, 2009 at 12:29 PM, Jamie Orchard-Hays <jamie at dang.com> wrote:
>> You'll want to keep an eye on what's happening in Rails WRT engines. Some
>> positive work is happening lately:
>> On Jan 6, 2009, at 4:16 PM, Jonathan Rochkind wrote:
>> Excellent. Matt, I know we talked about the use of Rails Engines here; I
>>> still feel it is a good idea. It was originally suggested to me by Erik
>>> Hatcher, in fact.
>>> If you get to this before I, please do consider Engines.
>>> As Rails has continued to develop, more and more of what used to be
>>> Engines-specific is now available to all Rails plug-ins. There's still some
>>> special stuff in Engines though, that is useful.
>>> Is Blacklight Rails 2.x right now? If not, migrating it there is another
>>> thing to add to our to-do list. Hopefully not a very hard thing, although
>>> with Umlaut it was a bit of pain, but Umlaut was/is doing some weird stuff.
>> Blacklight-development mailing list
>> Blacklight-development at rubyforge.org
> Blacklight-development mailing list
> Blacklight-development at rubyforge.org
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
rochkind (at) jhu.edu
More information about the Blacklight-development