thanks for the discussion, which cleared some of my thoughts and doubts. well, for my own packages i'll stick with three-level-nested namespaces ;) i will try to jump on collective.flowplayer...
cheers, hannes On Fri, 2010-07-09 at 15:21 +0200, Johannes Raggam wrote: > dear plone community, > > i'm going to create some packages which integrate some external flash > based software into plone. the idea is to provide these external > libraries without much extra functionality - much like the > collective.js.* packages do. i want to provide browser-resources, > register javasript and css and provide some functionality to make it > easier to integrate those libs in own packages. > > i want to create these packages in the namespace collective.lib.* > > * to start over, i gonna rename the package collective.wpaudioplayer to > collective.js.wpaudioplayer which i put in SVN yesterday (since it's so > young, renaming this package should be OK). > > * next, i'll create a new flowplayer package (collective.lib.flowplayer) > which does less tricks than collective.flowplayer (like it won't > automatically switch display views - which is cool for a plugin but less > cool for a developer's library). > > any thoughts on this? > > best, > johannes raggam > > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
