[Zope-CMF] Types, meta_type, content_meta_type, etc...

Shane Hathaway shane@zope.com
Wed, 10 Apr 2002 10:08:20 -0400

seb bacon wrote:
> For me, the biggest problem has always been this:
>     def Type(self):
>         """
>             Return the "human readable" type name (note that it
>             may not map exactly to the 'meta_type', e.g., for
>             l10n/i18n or where a single content class is being
>             used twice, under different names.
>         """
>         if self.title:
>             return self.title
>         else:
>             return self.getId()
> It has two bad effects:
> 1) Type can come from two different sources, which leads to unexpected
> effects
> 2) The Type is labelled 'Title' in the UI, which is misleading
> I think there should be a 'Type' field separate from the 'Title' field,
> and the Title can be treated as UI and the Type as application logic.

Actually, (IMHO) the "Type" of a TypeInformation object should be set to 
something like "Type Information", since there could potentially be 
metadata about a type information object.  You almost wouldn't want it 
to be configurable in the UI.