Sure there are convention. Read this post from Martin: http://www.martinaspeli.net/articles/the-naming-of-things-package-names-and-namespaces
Existing namespace AKAIK: collective.* for any addons that provide features to plone that doesn't fit with other namespaces collective.js for addons that provide resource like jqueryui, ... collective.contentrules for content rules collective.portlet.* for portlet collective.z3cform for z3cform widget ? others ? I really don't like mycompany.* namespace because company should exists in credits not as a namespace. I often start to search for addons in github/svn collective so it always nice to have good namespace. Regards / Cordialement, JeanMichel FRANCOIS Find me on Twitter <http://twitter.com/toutpt> / Retrouvez moi sur Twitter<http://twitter.com/toutpt_nantes> Le 11 avril 2012 16:29, Héctor Velarde <[email protected]> a écrit : > toutpt: > > on your post you mention something like "collective.action is not an > existing namespace"... > > is there any convention on package names on the collective? where do I > find that information? > > best regards > > Héctor Velarde > >
_______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
