[Zope3-dev] Adaptergeddon follow-up tasks (looking for volinteers)

[Jim Fulton]

I got adaptergeddon to the point where the major refactoring was done and
I could merge the big changes.  There are a number of follow-on tasks that
others could help out with.

1. Expand the component-architecture API to take advantage of new features
    of the adapter and view services:

    a. Specify provided interface when looking up views and resources

    b. Multi-adapter and multi-view lookup

2. Extend the ZCML view and resource directives to specify provided interfaces.

3. Extension or provide new ZCML adapter and view directives to support
    multi-adapters and multi-views.

4. Convert the traversal view registrations and lookups to use
    unnamed views that provide interfaces.

5. I think that there's an opportunity to improve the widget-related
    frameworks by specifying provided interfaces for widgets. Perhaps the different
    widget types (e.g. edit, display, hiddem, etc.) should be distinguished by interface
    rather than by name.

IMO, tasks 1a and 2 are the most important and urgent, as they are prerequisites
for 4 and 5.   Tasks 1-4 are all pretty small.  I suggest volunteers coordinate
their efforts here.

Task 5 is really a project that should start with a proposal, and, perhaps a
draft widget-development guide.

Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org