#2: Zope3 Adapterisation
- Contents
SubPlone is currently a custom content type and would make more sense as an adapter tied to a marker interface, allowing any folder to become a Sub-Site.
- Proposed by
- Justin Ryan
- Seconded by
- Sidnei da Silva
- Proposal type
- Architecture
- Repository branch
- bitmonk-adapterize
- State
- being-discussed
Motivation
The custom folder type provided by SubPlone has broken in more than one version of Plone due to ever-changing underlying types architecture and other factors. This risk can be lessened by moving SubPlone's code, mostly override of specific functionality, into adapters using the Zope3 CA.
Assumptions
All of SubPlone's functionality implemented via multiple inheritance must be replaceable with aspect-oriented adapters.
Proposal
Adapt IATFolder or somesuch versus customizing ATFolder or BaseFolder, so that any folder can be a Sub-Site and so that content will not become inaccessible if SubPlone's added functionality breaks temporarily.
Implementation
The Skin MixIn is the most important part to replace, there is also ProxyContainer which should probably be separated and arguably may or may not need to become an adapter.
Deliverables
Interfaces, Adapters, and ZCML - Oh My!
Risks
Though highly unlikely, SubPlone might never work again after I've become involved in its' development.
Progress log
I have lots of ideas, based on working code that I have seen, but I have done nothing so far to apply this to the version of SubPlone you see in collective. When I discussed it with him, Sidnei sounded like he felt rather confident that my zope3-ification plan for SubPlone was sane.
Participants
Me, maybe Sidnei, people from UofL, etc..