rubyonrailsin

I agree that it looks like Rails 3 and Engines make a lot of our
previous extension hackery unnecessary. I suspect there are a few
small things still missing that we'd like to patch in. One example
might be migrations. They don't automatically load plugin/engine
migrations with rake db:migrate in Rails 3 (nor do they plan to.)
Perhaps this is not a desirable feature but I'm thinking we could work
together to come up with a list to identify the following:

1. What is required for robust extension system
2. What is provided by Rails 3 and how do we leverage that
functionality (and document it.)
3. What is missing in Rails 3 still
4. Standard way to implement missing functionality for Spree and Radiant

We don't have the admin hooks you're using in Radiant but we do have
themes implemented already. We use themes as extensions actually and
I think it would be very cool to have the two systems use the same
theme approach (but not necessary.)

I think items 1-3 would be useful joint exercise. Comprehensive
documentation on all of this is spotty and I think both camps have a
pretty good idea of the kinds of things we'd need to support. I
certainly wouldn't mind working with a few people to quickly test out
what is possible now in Rails 3.

Sean Schofield

--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/

To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.