On 19 Sep 2007, at 14:02, Michael Koziarski wrote:
Sure, and what we've done so far internally is twist things so that this isn't the case and we don't have to rely on load order. It would be nice not to have to perform those contorsions.So for those situations you could use config.plugins = [:your_first_thing, :all] ? Or am I missing something.
Yes you could, but that puts the onus on the containing application. I've got say 3 plugins that my 5 apps share. Then I add plugin X and then change plugin A to use something funky from plugin X. I don't what to encode this new information in 5 different environment.rb files. It would be nice for that knowledge to stay in plugin A. It's okish for internal stuff when the author of the plugin and the consumer of the plugin are the same person/team, but it's a bit nasty if you're releasing a plugin to a wider audience.
Fred
-- Cheers Koz --~--~---------~--~----~------------~-------~--~----~You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.To post to this group, send email to [email protected]To unsubscribe from this group, send email to rubyonrails-core- [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/ group/rubyonrails-core?hl=en-~----------~----~----~----~------~----~------~--~---
smime.p7s
Description: S/MIME cryptographic signature
