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. 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.
James On Feb 7, 2008, at 7:16 PM, Pierre Joye wrote: > > On Feb 7, 2008 11:50 PM, James <[EMAIL PROTECTED]> wrote: >> >> Here are a couple ideas for naming prefixes. >> >> it is common to use your own intials, so if you are John Quincy Adams >> you may use. >> >> jqaGoogleNewsFeed > > > Please stop to prefix plugins name like that, it is über painful and > hardly logical. As far as I know, it was decided to do not change the > prefix. > > Cheers, > -- > 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 -~----------~----~----~----~------~----~------~--~---
