Hi everyone, I would like to share with you some of my feelings about the way plugins dependencies should be handled.
1- is that normal that plugins simply do trivial actions, or almost? 2- in case a trivial plugin covers a trivial functionality already covered by a wider plugin, what should be done ? Introduce dependencies between the plugins, or have each piece of code do their way separately? This question is motivated by the apparition of the new sfTagCloudPlugin plugin, which bundles a module component for displaying a tag cloud from an associative array (I guess this should rather be a helper, but anyway :)). The real problem is, that this job is already done by the sfPropelActAsTaggableBehaviorPlugin, which is intended to cover all the tagging-related issues in a Symfony development. Particularly, it includes a tag_cloud helper. So my question: should the sfPropelActAsTaggableBehaviorPlugin be modified, so that it introduces a dependency to the sfTagCloudPlugin? Or should the sfTagCloudPlugin use the same code like the sfPropelActAsTaggableBehaviorPlugin for tag-clouds rendering? Thanks, xavier -- Xavier Lacot http://www.clever-age.com Clever Age - conseil en architecture technique Tél: +33 1 53 34 66 10 Fax: +33 1 53 34 65 20 Clever Age vous invite à ses petits-déjeuners http://www.clever-age.com/actualites/petits-dejeuners/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
