I have several comments here. First about the quality of the plugins. I notices the most people just want to make their own plugin out of anything, first maybe to see how it is done, second to "contribute" to the community. 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. Fabien said it even better that a plugin needs to have at least several hundred lines of code to be packages as a plugin (rule of thumb, I guess). So in an attempt to clean most of this "one file plugins", I created the plugin sfUtilitiesPlugin where I take other small plugins and assimilate them as utilities, exactly what they are. Please, take a look at the current classes included in the plugin and you will see what I mean. Also, when including them in the plugin I make sure that they confront to the SYMFONY standards. This is important, rihad, as PHP developers should stop act like children and become professionals and follow certain guidelines. If you contribute to PEAR, you follow their rules, if you contribute to Zend Framework, you follow their rules, if you want to have plugins accepted by Symfony developers, then follow Symfony's rules, simple as that.
Some time ago (maybe months now) there was a discussion to make a php code standards validator which is used in PEAR. We can create rules according to the official Symfony guidelines and have it as a plugin that can be used by teams of developers working on the same Symfony project. This would solve the issue Hassen is having with his team at the moment. If I had time, I would take the responsibility, whether people are "against" or "for" what I suggest because it makes enough sense to me to use it in all the work I do with Symfony. So, yes, I agree with the original post and we better start thinking rationally or we will end up with useless lis of plugins. Kupo On Dec 7, 5:28 am, "Hassen Ben Tanfous" <[EMAIL PROTECTED]> wrote: > Hi, > I would like to know if there is any article demonstrating or encouraging > some design patterns or coding habits. > > Because I started reading a lot of plugins and there is so much crap out > there. > > People are merging their code with the configuration, the logging, the > security etc. You end up having 4 lines of code for your business logic and > 15 lines of code checking behind you. > > Maybe because I did too much Java but I'm used to have some design patterns. > > Other than the MVC and TDD, we do not having anything else. > > Even TDD is not complete and sometimes very hard to maintain. > > I already convince my team to choose Symfony for the frontend and Java for > the backend. But, we are too many developers, with a lot of backgrounds and > unfortunately a lot of different ways to write code. > > I know programming is not a science but an art. But with Java the whole team > is designing in the same direction, with PHP everyone is an individual > artist. > > Please let me know if you guys are using any good design patterns. Maybe > starting to have snippets about concepts would be great. > > Thanks > Sincerely > -Hassen Ben Tanfous --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
