Michael Mulich's List: public

• Fixed in the latest truck. It uses the getUtilitiesFor to get a list of tuples with name and interface. This allows us to remove all the other interfaces except the one we want. This was my point about discoverability. - Michael Mulich on 2008-12-17
• duffyd has come forward and has been helping out with the process. - Michael Mulich on 2008-12-17

• ``contextual adaptation''
• essentially global in nature
• we cannot replace that adapter with another, since it is already the shortest adapter path
• client or the framework
• hypothetical subsetPerInstance class would be a descriptor that did all the work needed to provide a ``localized'' version of each interface for each instance
• but still use any globally declared adapters as defaults
• register adapters that are unique to a specific
• descriptor should work with both old and new-style classes
• Thus, the new local protocol will know its context is the instance it was retrieved from.

7 more annotations...

• Viewlets are multi adapters (context, request, view, viewlet manager) so they only show up when they are registered for the interfaces or classes that currently applies
• Context dependent viewlets