I ALWAYS think it's good to namespace things. ESPECIALLY framework- and language- type of things.
Thus, Apple namespace their framework objects as "NSBlah", etc. This way it won't conflict with your application-level names. Julian. On 16/11/2008, at 11:07 AM, [EMAIL PROTECTED] wrote: > > I've put together a port of a really nice Rails Plugin (app_config) > that allows per environment yml AppConfig settings using a beautiful > OStruct object > > http://github.com/merbjedi/app-config > > I'm trying to figure out the best way to name my gem when I set up the > RubyForge project. Yatz mentioned during MerbConf that we should > standardize naming conventions for slices so we can easily do a "gem > list merb-slices-" to see a list of them. > > So I named it "merb-plugins-app-config" > > Please recommend an alternative naming scheme if you think this one > has problems. One problem might be that it sort of looks too much like > an "official" plugin. I don't know if this is a problem or not, since > all the officially maintained Merb plugins will be in the Merb-Plugins > repository. > > Thanks > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
