[Zope3-dev] Managing via Component Interfaces TTW

[Gary Poster]

Mucking about the fishbowl on a different mission got me a rejected
http://dev.zope.org/Wikis/DevSite/Proposals/InterfacesMappedToIds and "(We
ended up coming to the idea of "Services" instead)".  Sorry for the static,
then, I guess... isn't the CMF services concept specific to tools, though?

And, perhaps a better question: should I consider the Zope3-dev list to
primarily have its topics introduced by the devs?  Would this be a better
subject matter for the normal Zope-dev list?  I haven't seen an explicit
etiquette expressed in that regard, but wondered if either or both of those
might be the case.

Gary


----- Original Message -----
From: "Shane Hathaway" <shane@zope.com>
To: "Gary Poster" <garyposter@earthlink.net>
Cc: <zope3-dev@zope.org>
Sent: Thursday, January 17, 2002 11:37 AM
Subject: Re: [Zope3-dev] Managing via Component Interfaces TTW


> Gary Poster wrote:
>
> > I imagine there are others.  Any ideas?  A string, like the metatype, is
> > limiting in many regards, but its simplicity is very convenient for web
> > work.
>
>
> I've been thinking we'll probably use "label interfaces".  Label
> interfaces are like marker interfaces with the distinction that they are
> identifiable by a simple string name.
>
> The exact details of how label interfaces are created and stored have
> not been decided, but I did a little proof of concept that let you
> create and use label interfaces through the web using a CVS version of
> Zope.  The UI was a little too complex, but we should be able to improve
> upon it.
>
> Shane
>
>
>