Rails 2.0PR is out, is Engines 2.0 on it's way?

#1

Hey James et all,

Curious if you have been doing any work with EDGE yet, or even the
recently
announced 2.0PR. Looks like some really sweet improvements have been
made.
Although I still like my ToolbawksPacker over the new Rails 2.0 :all tag
for
JS as it includes JSMin and can work on a per layout basis rather than
loading in the whole show. Still waiting on any beta testers if people
fine
this feature useful. Just let me know if you need more info to warrant
an
investigation.

So as for the new Engines 2.0, not sure what’s needed yet as I haven’t
even
seen where it breaks, but from what I hear ToolbawksDatetime doesn’t
work in
EDGE, so I figure something major changed as expected with Rails with
the
new release, that has caused the malfunction.

Has anyone else other than James been working with Edge/2.0PR yet with
the
Engines?

NSHB.

#2

On 10/3/07, Nathaniel B. removed_email_address@domain.invalid wrote:

Curious if you have been doing any work with EDGE yet, or even the recently
announced 2.0PR. Looks like some really sweet improvements have been made.
…
Has anyone else other than James been working with Edge/2.0PR yet with the
Engines?

I’ve had a ticket open for Rails 2.0 for a while, soliciting feedback
about how the architecture will change given the modifications to
Rails’ own plugin system:

http://dev.rails-engines.org/engines-plugin/tickets/267

So the first thing to do would be to look there. Next, look at these:

http://groups.google.com/group/rubyonrails-core/browse_thread/thread/07615e2ac0fa019d/531b16335db4b4ad?#531b16335db4b4ad
http://dev.rubyonrails.org/ticket/9795

I’m very keen to get ticket #9795 applied, since its my opinion that
the change in Rails (http://dev.rubyonrails.org/changeset/6277)
doesn’t really help at all in its current implementation.

So, even if you don’t provide any feedback on the
dev.rails-engines.org ticket, please do test out the patch on #9795
and give it a +1 if you feel that it’s a good step.

I’m holding off doing any serious development for Rails 2.0 to support
the plugin architecture changes until the core team have made a
decision about these patches.