Fully support what Sean just said.
I already started doing some experiments with extensions as engines. Radiant would expose a couple of APIs more than Rails (navigation tabs, for instance), but that would be it. The rest would be up to Rails 3.
My suggestion is for both of us (Spree and Radiant) to try re-implementing our extension systems with Rails 3 engines and see how much we are required to add on top of that. Then, go for a merger.
What's tricky (in Radiant) is the API for hooking into the admin interface in various places (formerly known as Shards). I didn't find it optimal for some advanced needs. Also, on Rails 2.3.x the performance is not satisfactory. I don't know if Spree needs such functionality, but if it does, it's worth exploring a common solution for that which would scale in terms of performance and ease of use.
I'm not sure how much you guys have looked at Rails 3's implementation
of Engines -- the standard Rails stack is implemented as one, even --
but it is exactly what extensions should have been, IMO. You can
pretty freely compose applications together in ways that you could
never do before.
So, for creating a standard for extensions, it may not be necessary
(other than helping people migrate away from the old API). On the
other hand, it might be high time to decide how extensions should and
should not interact, at least establishing some best practices.
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.
No comments:
Post a Comment