I have done the next one c.js.jqueryui. Javascripts are just resources (like swf but not html5), and it's more easy to set version number over this by following the resource version.
I think package must be used as package, and not to expose implementation or the name of a company or sth. There are many examples where a resource is embeded with it's integration and that is not good because you can have multiple version of the same lib if you are using multiple add-ons (that was my case under www.nantes-developpement.com because of Products.ImageEditor & c.alerts) Even if c.js. is not good it exists and has saved me with integration issues. I think every external javascript should be packaged to prevent integration issues. -1 for c.lib too generic and doesn't mean anything (can be C library or anything but flash) +1 for c.resources.* so you can add the resource at the root of the package without making browser/resources folder. ----- Jean-Michel François aka toutpt http://toutpt.wordpress.com http://twitter.com/toutpt -- View this message in context: http://plone.293351.n2.nabble.com/namespace-collective-lib-tp5274276p5286373.html Sent from the Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
