Understood, my plugin will move to the snippets page, and will be turned into a Helper instead. :)
Stefan On Oct 22, 4:34 pm, Fabien POTENCIER <[EMAIL PROTECTED] project.com> wrote: > I agree with Lukas. > > It does not make sense to have a plugin just for a tag cloud helper. > This must be published as a snipeet or as a page on the wiki. > > Fabien > > -- > Fabien Potencier > Sensio CEO - symfony lead > developerhttp://www.sensiolabs.com/http://www.symfony-project.com/ > Sensio Labs > Tél: +33 1 40 99 80 80 > > Lukas Kahwe Smith wrote: > > > On 22.10.2007, at 12:29, Xavier Lacot wrote: > > >> 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? > > > Maybe just a brief explanation on how the PEAR project is dealing > > with this issue. For one we do not have super trivial packages in > > PEAR. So there has to be atleast a few hundert lines of code. For > > anything else I suggest sticking with posting a snippet on the wiki. > > > As for the dependencies we follow a similar rule, the dependency has > > to safe at least a hundert or so lines of code. If not then we prefer > > to duplicate the code in order for users to not be burdened with too > > many minor dependencies. > > > regards, > > Lukas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
