Do the core symfony developers use Eclipse? Or has anyone else created a template for formatting rules which can be imported to Eclipse?
I know code style is more than indents, new lines and curly braces, but they are among the most visible ones. It would be nice to have an official comprehensive guideline for such matters. If it already exists, it should be made more available, so I can find it ;) -g On 12/12/2007, Alexander Deruwe <[EMAIL PROTECTED]> wrote: > > > On 12 Dec 2007, at 02:57, Kiril Angov wrote: > > Hey Kupo, > > > Alexander, sorry if my example with blueprintcss plugin disturbed you > > but I just wrote the first two plugins I remembered from the ones that > > just "wrap" a certain functionality. Nothing personal :) > > I guess I did take it a bit more personal than was appropriate - my > apologies. > > > I just want to say again why following Symfony's coding standards is > > good thing. If I want to contribute to a plugin but it is written is > > the > > author's own style of coding, it becomes not only difficult to > > contribute to the plugin but also I do not feel like editing bad code. > > I'd rather create it from scratch. You see the problem here, right. > > And > > if I took the responsibility to change the format of the other > > person's > > code, then I run into the problem of being shouted at by the other > > developer. > > This I wholeheartedly agree with. > I too have found (and am using) some plugins that are completely > different in style to what I'm used to from symfony - there's even one > (which I won't name to avoid situations as I let myself get into > yesterday evening ;) for which I maintain private changes _because I > don't want the developer shouting at me_. > For my own projects, I have used the symfony coding standards, though > I'm sure there's discrepancies here and there. A task to verify this > would be great - I might try and chip in, but I'll have to check when > is the Sprint as I am currently abroad and reasonably busy. > > Once again sorry for getting all heated up about this - I stand by my > plugin but I realise the difference between it and (for example) > sfGuardPlugin better now. adBlueprintPlugin is indeed a wrapper-only > plugin and as such a plugin is just one of the ways in which it might > be distributed. > > > Alexander > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en -~----------~----~----~----~------~----~------~--~---
