[Zope3-dev] Re: Mini proposal: simpify presentation-lookup api

[Philipp von Weitershausen]

Jim,

>>>> In the docstrings, you talk about presentations, but the methods are 
>>>> called {get|query}Presenter. I think they should be called 
>>>> {get|query}Presentation. That's also inline with the service being 
>>>> called Presentation Service, the service for Adapters being called 
>>>> Adapter Service, etc. etc.
>>>
>>> Presenter is shorter. I'm open to even shorter names. :)
>>
>> I distinctly remember you ruling explicitness in names (even if it 
>> means long names) over short names. This is a case where I agree with 
>> this policy of yours :)
> 
> Great, but we haven't proved that there aren't short names that are
> meaningful.

Ok. I'm not going to prove that one, 'cause I'm fine with Presentation.

>>> We can rename the service.
>>
>> -1
> 
> You aren't -1 on renaming the service are you? You are -1 on
> "presentor", right?

Yes.

>> A presentation is clear. A presentator is not. The endswith('or') 
>> implies an actor, a (real) person doing something.
> 
> 
> But a presentation component presents an object, just like
> an adapter adapts an object.
> 
> Would you prefer "getAdaptation", and an "Adaptation Service"

No. Here's why:

'Adapter' is a common word. 'Presentation' is a common word. 
'Adaptation' and 'Presentor' are not. Yes, this is a matter of being 
comfortable when using the terms.

I would prefer

   AdapterService.getAdapter()

and

   PresentationService.getPresentation()

Philipp