On Sun, Apr 25, 2010 at 9:53 AM, Josh French j...@digitalpulp.com wrote:
There are still some things to be worked out with gems and UI regions
I spotted your earlier mention of this and did some digging, but I haven't
been able to find anything specifically wrong with the region set stuff.
While I was investigating I did uncover a load-order issue, so I wonder if
you weren't seeing this:
http://github.com/radiant/radiant/issues#issue/109
Is there a case where just the region sets are failing?
I haven't looked into issue 109 yet, but I made
radiant-dashboard-extension as a gem and required that and then an
extension which uses it and got errors about regions not being
defined. It is a load order problem but I haven't gotten farther than
that.
If we're moving towards the idea of Rails 3
embeddable apps, I would want to have all my migrations in one place,
clearly organized, where I can understand what's going on.
There's been a long-running discussion within Rails proper about engine
migrations. This is lengthy, but fundamental reading for anyone pondering
migrations:
https://rails.lighthouseapp.com/projects/8994/tickets/2058-rake-tasks-for-run-engine-migrations#ticket-2058-22
This has implications for both Radiant and Spree's extension systems. Overall
I like the pattern that's emerged from that thread: copy migrations from each
extension, re-timestamp them to preserve the order of operations, put them in
RAILS_ROOT/db/migrate. I think there are some unanswered questions, but
consensus is that this is probably the most viable pattern.
I agree, but the problem that isn't addressed is uninstalling
plugins/extensions, for which I think making reversed copies of
migrations is useful.
--
Jim Gay
http://www.saturnflyer.com
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org
