It might be better to use gems where possible, as that's the direction both Rails and Radiant are going. If you can't use your plugins as gems, John's method should work.
Sean On 1/12/10 10:33 AM, john muhl wrote: > On Tue, Jan 12, 2010 at 9:22 AM, Asfand Yar Qazi<[email protected]> wrote: > >> 2010/1/11 banane<[email protected]>: >> >>> Put the routes.rb stuff in [yourapplication]_extension.rb >>> You can extend ActiveRecord, just like in Rails. Rails is embedded in >>> Radiant, so it works pretty much the same. >>> Put the testing stuff in /rspec, test as usual. >>> >> And what about selenium on rails tests? That is another stickler. >> >> Another question: My app currently uses several plugins it needs. If >> I make my app an extension, where do those plugins go? If I simply >> move them to the Radiant app, won't that make upgrading difficult? >> > if your rails app has vendor/plugins/xyz then your extension would > have vendor/plugins/xyz. for example: > > /rails_app/vendor/plugins/xyz > /radiant_app/vendor/extensions/your_extension/vendor/plugins/xyz > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
