[Zope3-dev] More name game suggestions

[Amos Latteier]

Hi,

I'd like to chime in with my $.02 on component naming. I think that
component names should be designed to help developers learn Zope
3. The component names should help developers understand the component
architecture. I think that we should try to use existing names and
concepts when possible, and avoid inventing new names.

Phillip suggesting changing the name of Features to Adapters. I agree
with this suggestion, since I think it makes it easier to understand
what these components do. Maybe they don't exactly correspond with
everyone's idea of what an adapter is, but they seem to be reasonably
within the definition of an adapter. Plus, "adapter" is a term that
folks have heard before, while "feature" isn't (in this context).

I don't really think that presentation components need to be renamed
to view or UI components. All these names seem more or less equally
evocative to me.

I do think that we should consider renaming "utility" components. I am
always confused by the term "utility" and the descriptions of them. I
get confused by the fact that they're like services but they differ in
some subtle way. After looking into it more, it seems to me that they
would be better termed "application" or "logic" components. It seems
to me that they key difference between services and utilities is that
services provide important functionality to all comers, while utilities
provide application-specific services. Therefore, I prefer the term
"application" component.

-Amos