James, On Feb 8, 2008 1:58 AM, James <[EMAIL PROTECTED]> wrote: > > Piere, > > Please read his email before telling me what the community has decided > for the community. I understand that for community plugins you should > always use the sf prefix. He's not talking about a community plugin, > he's taking about a proprietary plugin for an API that you have to > have a licensing agreement for.
I read his post and I don't see why it should be any different. > While he could go ahead and use > sfSomePlugin he doesn't have too. He's looking advice, If it's not a > requirement from an Symfony API standard to use another prefix he > doesn't have too. I gave him a methodology that is commonly used with > libraries/plugins. You may think it's "über painful" but it's not. It > helps keep name space sane. It may be the counter part, making it rather insane. What is common is to use a prefix, always, we agree on that at least :) -- Pierre http://blog.thepimp.net | http://www.libgd.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
