[Community] ZCO

[Michael Kerrin]

Hi,

 After talking to Kai earlier today I realised what a bad communication 
channel IRC is if what you want to say goes over 2 lines. So after my 
previous email about moving things from primagis-zope3 -> zco3 where is a 
list of of what I have moved back on a local copy.

  1) Pretty much all the vocabularies - they are handy. But I am going to name 
all the unnamed vocabularies so that they can be overridden.

  2) the interfaces IMap, ILayer, IRule. I have also slightly modified these 
interfaces so that they declare the bare minium attributes, methods which are 
needed by the corresponding content objects.

  3) A number of adapters including style.SLDRule, style.StyledLayer, 
layer.PCLLayerAdapter - all these adapters adapter an interface mentioned 
above and provide an interface contained in the cartography namespace.

  4) I have moved all the map views has defined in 
primagis.browser.map.__init__.py back to zco including the session code, and 
primagis.js. I did this because they are complicated, and why do them again. 
But the thing about this is that has they stand in zco they are unusable and 
has such they aren't configured to do anything. We run into nasty problems 
like zope.app.session isn't distributed with Zope2.9, and Zope3 views needed 
to be slightly modified in order to run within Zope2.9 thanks to Zope2's 
implicit acquisition. What they do become is helper classes for the CPS, 
Plone, Zope3 frameworks to implement these views. So by extending these 
classes and providing a __init__ method I managed to implement the map views 
in CPS without thinking. I will need to come with a interface for the 
primagis.browser.map.MapView class before I do this, just in case specific 
methods need to be overriden.

  5) MochiKit - why not it is required by primagis.js - another complicated 
beast.

  I plan to tag the zco3 branch and basically just copy all the above back to 
zco by tomorrow. This shouldn't break anything since I can easily leave out 
the ZCML configuration until primagis-zope3 branch has being correctly 
configured to use the code in ZCO, and then I can remove the code from there.

  Things to think about moving backwards are all the images and css. This 
should be acceptable considering that the ZCML language was designed 
specifically to allow people to easily override configurations made in other 
packages, so there shouldn't be any

  Try saying all that on IRC :-)
  Michael
-- 
Michael Kerrin

55 Fitzwilliam Sq.,
Dublin 2.

Tel: 087 688 3894