[z3-five] Re: Todo list discussion

[Philipp von Weitershausen]

Sidnei da Silva wrote:
> | now that we have zope:content, do we still need five:implements?
> | =================================================================
> | 
> | I don't know either. The nice thing about five:implements that is it 
> | short and to the point. zope:content is a bit more involved (you can 
> | also do security related stuff) and implies you only do this for content 
> | classes (even though it works for anything). There's also zope:class 
> | which does the same but can be used with everything.
> | 
> | In any case, five:implements doesn't do a lot of harm; perhaps we can 
> | introduce a zope:implements into Zope 3? :)
> 
> I thought we had a zope:implements. If not, we should use zope:class.
> 
> <class class="this.that">
>   <implements interface="this.ithat">
> </class>

zope:implements does not exist. We only have zope:class and zope:content 
which are identical in every way. It being able to do more than just 
having a class implement an interface is not so bad. However, I just 
thought of a reason why five:implements (or zope:implements, 
respectively) would actually be useful. Because of ZCML discriminators, 
zope:class can only be called once for each class. However, I see the 
use case of calling five:implements serveral times for a class, e.g. 
Product A is having OFS.Folder.Folder implement some interface while 
Product B is having it implement another one... Two zope:content 
directives would be conflicting here...

Philipp