Its worth noting that the Engines plugin functionality is not
completely replicated in the Rails 2.3 Engines code.  There are many
things that you'll read about Engines doing (asset loading w/o
copying, environment expanding, migrations) that the Rails 2.3 engines
do not do.  From following the discussion I feel like the goal
(eventually) is to get fully mountable apps, but that won't happen
until Rails 3 and my hunch is that it may get pushed back even more.

Rob

On Tue, Apr 7, 2009 at 10:59, Jordan Fowler <[email protected]> wrote:
> I agree with Dan. For most things, you'll be writing custom code. At this
> point Rails Engines are what I would call "half-baked."
> -Jordan
> On Apr 7, 2009, at 7:58 AM, Dan Simpson wrote:
>
> From what I can tell, engines have a long way to go.  They still serve a
> good purpose as is, but have several shortcomings.
>
> What they can do:
> Define application files (app dir)
> Define routes
>
> ... and that seems to be it for now.  Migrations, plugins, and static files
> need to be synced via a rake task.  App requirements that you want to define
> in environment.rb, well, you can probably do it with some IO, but there is
> no support out of the box for it.
>
> So to sum it up, it's good but immature.
>
> --Dan
>
>
> On Tue, Apr 7, 2009 at 7:34 AM, Ken Hudson <[email protected]>
> wrote:
>>
>> Now that support for the engine plugin has been incorporated into Rails
>> 2.3, I'm very interested in taking advantage of this functionality.
>>  Specifically, I would like to be able to embed one rails application within
>> another.  I think this would have tremendous productivity benefits down the
>> road.  However, I'm curious how well this actually works in practice and
>> what the real-world limits are.  Do Engines in Rails 2.3 work well?
>>  Practically speaking, how many apps can be embedded in another app?  (I'm
>> not talking about theoretical limits but more real-world practical limits.)
>>  Also, what is the best way to handle authorization and authentication?
>>  Finally, would I be better off waiting for the Merb Slices functionality to
>> be added to Rails 3 or would starting with Engines now put me in a "better"
>> position when Rails 3 is released?  Answers to these questions as well as
>> any other thoughts or experiences would be much appreciated.
>> Thanks, Ken
>>
>
>
>
>
>
>
>
> ---------------------------------------------------------------
> Jordan A. Fowler
> 2928 Fir St.
> San Diego, CA 92102
> E-mail: [email protected]
> Website: http://www.jordanfowler.com
> Phone: (619) 339-6752
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
-~----------~----~----~----~------~----~------~--~---

Reply via email to