On 2010-07-09, at 1727, Martin Aspeli wrote: > -1 to collective.js.* too, by the way. :)
*holds his hand up to this one* I made the first of these, the logic was that we wanted a setuptools compatible way of distributing javascript with some way of getting to it easily from Zope/Plone. Calling it js.* would have been egocentric as other frameworks might well want to do the same. Of course, they are welcome to add non-zope things to collective.js.* as long as it doesn't break it for us, in which case collective signals where they can go. collective.jquery wouldn't work either, as we wanted this to be very much lightweight packagings, no integration beyond exposing the files. Imagine TinyMCE, if it were in the collective it would be collective.tinymce as it has lots of configuration that is exposed in plone. It may well also be collective.js.tinymce for the stock js that TinyMCE release, but that's probably overkill. Managing it like this makes it easy for us to see at a glance what version of various JS libraries we're using, for end-users to override those versions without fiddling with Plone's core JS and to prevent multiple inclusion of libraries. It also makes the licensing clearer, which is nice. I'm thinking about proposing a PLIP for 4.1 to move the actual JS files we use into this structure, but would be interested to hear from end-users as to if they think this would be useful to them. Matthew _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
