[Community] ZCO / Zope3 - what should be in what

[Sean Gillies]

On Mar 24, 2006, at 8:55 AM, Michael Kerrin wrote:

> Hi All,
>
>   I am going to be starting to port of primagis-zope3 to CPS pretty  
> soon. I
> know there is a lot of code in the primagis-zope3 that I would like  
> to reuse
> within the CPS and I assume others would like to use within Plone.  
> So I would
> to spell out what I want to move from the primagis-zope3 to ZCO,  
> why, and see
> what all you guys think about it and how it fits into peoples plan  
> for Plone.
>
>   In my opinion, Primagis should contain all implementations of all  
> persistent
> objects, views, and edit forms for these persistent objects which the
> exception of the map image generatation code which should be in ZCO  
> because I
> don't want to reimplement it, has it is very, very COMPLICATED :-) but
> primagis should contain the html view page which will call the  
> views within
> ZCO to generate the images for the map, so for starters I propose  
> moving the
> following to zco:
>
>   1) all the interfaces for the content-types minus their  
> implementation.
>       - this is necessary in order to move the rest of the code  
> below into ZCO
>
>   2) a bunch of adapters including primagis.layer.PCLLayerAdapter,
> primagis.style.SLDRule, primagis.style.StyledLayer and any others that
> provide an interface contained within the cartography namespace -  
> why redo
> them, if the adapter doesn't work for a specific platform it is  
> very easy
> using Five to override the adapter.
>
>   3) there are a number of vocabularies that contain a set of  
> implementations
> of interfaces from the cartography packages - these should go into  
> ZCO has
> they are useful and again why redo them. This include the symbolizers
> vocabulary. We could also move the imageFormatVocabulary,  
> mapUnitsVocabulary,
> scalebarStylesheetVocabulary vocabularies since these vocabularies  
> contain
> fixed values so we may has well provide some consistency across the  
> different
> primagis.
>
>   4) map views - all the views that preten to generating the image  
> of the map,
> scalebar, but not the the html view of the map. All this is code is
> complicated and duplicating it sounds very, very painfull.
>
>   I am sure there is more we could move into ZCO but these are the  
> main ones I
> am worried about, Kai's recent work which I have just seen may  
> include some
> stuff we can move over.
>
>   Has I said I am going to be porting all the good work done at the  
> Dublin
> sprint  to CPS, has soon has I can but I hope be able to to use this
> experience to help with moving this work to Plone also. And what I am
> proposing will hopefully make the porting a lot easier.
>
>   What do you think
>   Michael
>
> -- 
> Michael Kerrin

Michael,

Sorry for being so late to respond. My opinion is that we should push  
features (and responsibilities) down the stack into ZCO and even to  
PCL whenever possible. IIRC, Kai (correct me if I am wrong) concurred  
with this on IRC last week.

Sean

---
Sean Gillies
http://zcologia.com