> Inflection should be its own gem. So should time intervals (5.days.ago). In > particular, anything that messes with core Ruby classes, I'd like to be able > to use without pulling in everything else that messes with core Ruby > classes.
This is something that we intend to do, not through seperate gems but through other mechanisms. One of the things we're hoping to do for rails 2.3 is to make active support 'cherry pickable'. So give you an option like: require 'activesupport/inflector' And only get the inflection functionality, and nothing unnecessary. > But the other stuff in core, like the router... Any router is going to be > tightly bound to a controller model, unless it's something without a > controller, like Sinatra. What is gained by making them pluggable? 'Modular' and 'Pluggable' are a bit like 'scalable' to developers. We love the words but don't necessarily know why, or what problems we'd be solving or what changes we'd be making. So I'm always hesitant to promise 'modularity' or 'pluggability'. Having said that, in cases like the above where you want something, but don't want some baggage, we can and will make the changes needed to support that. -- 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 [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
