Hello!
I've just been reviewing the collective.flowplayer code as part of the
process for approving it for use on our Plone sites. It looks great,
with one exception: we host many Plone sites in one Zope instance, and
want to selectively install collective.flowplayer to only some of
those sites. Based on inspection of the code, it looks like there are
two ways in which collective.flowplayer will pollute the other sites:
1. It registers various browser views without specifying a browser
layer.
2. It subtypes objects in response to object events without checking
to make sure that the object is within a site that has
collective.flowplayer installed.
Both of these should be pretty easy to fix...Can we do that?
David Glick
Web Developer
ONE/Northwest
New tools and strategies for engaging people in protecting the
environment
http://www.onenw.org
[email protected]
work: (206) 286-1235 x32
mobile: (206) 679-3833
Subscribe to ONEList, our email newsletter!
Practical advice for effective online engagement
http://www.onenw.org/full_signup
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
