Re: [Radiant] extension dependencies in ray
thanks for the details. guess that code stays for now. On Wed, Sep 9, 2009 at 1:32 PM, Sean Cribbs wrote: > This is a *runtime* dependency, not an install-time one. > > Basically, an extension can do this: > > extension_config do |config| > config.extension "paperclipped" > end > > The initializer will check that "paperclipped" is available in the app and > error out if not. > > Sean > > john muhl wrote: >> >> On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs wrote: >> >>> >>> Looks like it's time for another release of Radiant: >>> WHAT'S NEW IN THIS RELEASE? >>> * Allow extensions to declare dependencies [Josh French] >>> >> >> does this mean that i can safely rip out all the code in ray that >> tries to allow some extension dependencies? my feeling is that it >> wasn't ever a hit feature in ray and that the implementation in >> radiant is more usable/flexible. >> >> is anyone using the dependency feature in ray who be sad to see it go? >> ___ >> Radiant mailing list >> Post: Radiant@radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> >> > > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] extension dependencies in ray
This is a *runtime* dependency, not an install-time one. Basically, an extension can do this: extension_config do |config| config.extension "paperclipped" end The initializer will check that "paperclipped" is available in the app and error out if not. Sean john muhl wrote: On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs wrote: Looks like it's time for another release of Radiant: WHAT'S NEW IN THIS RELEASE? * Allow extensions to declare dependencies [Josh French] does this mean that i can safely rip out all the code in ray that tries to allow some extension dependencies? my feeling is that it wasn't ever a hit feature in ray and that the implementation in radiant is more usable/flexible. is anyone using the dependency feature in ray who be sad to see it go? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] extension dependencies in ray
On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs wrote: > Looks like it's time for another release of Radiant: > WHAT'S NEW IN THIS RELEASE? > * Allow extensions to declare dependencies [Josh French] does this mean that i can safely rip out all the code in ray that tries to allow some extension dependencies? my feeling is that it wasn't ever a hit feature in ray and that the implementation in radiant is more usable/flexible. is anyone using the dependency feature in ray who be sad to see it go? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
