Loren Johnson wrote: > Did you consider wrapping it up as a plugin? Off the top of my head > that seems like it could be the cleanest way to go, but I say that > without seeing how you have it setup now.
I think I agree with Loren that Radiant as a plugin is a much nicer way to go (vs. dropping it in your vendor directory). This way you could install the pluginized version of Radiant with a simple: script/plugin install radiant I'm willing to consider changes to Radiant make this integration easier. > Are you suggesting that I develop from the Radiant SVN repository? > Or are you saying that you'd be happy to host a copy of stable > releases? Perhaps you could work with Loren on this for the time being. He just recently joined core and it sounds like you have the same goals. When you have something ready you guys could drop it in: http://dev.radiantcms.org/svn/radiant/trunk/plugins/radiant/ I'd suggest that the plugin would have the following directory structure: plugins/ radiant/ init.rb lib/ vendor/ radiant/ <<< an svn:external to trunk/radiant All of this talk makes me think that we need to move all of the Radiant models into the the top level Radiant module to avoid namespace collisions. -- John Long http://wiseheartdesign.com _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
