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 :)
My main point was for those one-file/on-library plugins. I will not say anything more before we have symfony-forge where things will come very well in place, I think. 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. I plan on working on a pake task to check the source code for valid coding standards during the Symfony Sprint, so hopefully we can see soon how this would work. Kupo Alexander Deruwe wrote: > On 11 Dec 2007, at 15:53, KupoKoMaPa wrote: > >> But as I stated >> before we do not need a plugin for including google analytics, for >> example or incorporating blueprintcss into symfony, this is all >> trivial. >> > > As the author of the blueprintcss framework plugin... Yes, the plugin > is mighty trivial - but I prefer it greatly to copying the > blueprintcss files to the web directory of all my projects where I > wish to use blueprintcss. For me, that means create a plugin you can > pull in when needed. > I guess I could have kept that plugin private, for my use only - but > that's the wrong mindset for the open source world and I will never > accept that the plugin should not have been made available to the > public. Now, maybe this should not be in the 'main list' of plugins > on the wiki, that's a whole different point. But, yes, by virtue of > this plugin having use for me personally, I am sharing it _as a plugin_. > > I am more than willing to move it to a TrivialPlugins page on the wiki > if that will make people happy - but 'we do not need a plugin for > blueprintcss' is a false statement. It was created, so it was > shared. Maybe you mean _you_ don't need it? If so, I apologise for > wasting bandwidth because that is a personal opinion and far be it > from me to tell you what to do or think. > > Cheers, > > > Alexander Deruwe > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
