On Thursday 26 May 2005 03:31, Leeuw van der, Tim wrote:
> In java-terms you'd say that one interface *extends* another interface,
> rather than implements. But I guess this wording is because Python doesn't
> have interfaces, and therefore in your class-definition you might not see
> the differenc
Sakesun Roykiattisak wrote:
So the document does wrong. Let fix it and put my name on the
contributer list... :-D
Done. Thank you for the pointer.
Regards,
Dominik
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listi
No, the interface directive uses the directlyProvides mechanism to
type the interfaces.
(See zope.app.component.interface.provideInterface).This function is
called by the directive
handler (See zope.app.component.metaconfigure.interface).
Thanks a lot.
IMO only the therm *provides* is co
Sakesun Roykiattisak wrote:
Ouch.. Perhaps it use "classImplements" rather than "directlyProvides"
Anybody could give me a pointer to the source code where I can find
the answer ?
No, the interface directive uses the directlyProvides mechanism to type
the interfaces.
(See zope.app.component
Ouch.. Perhaps it use "classImplements" rather than "directlyProvides"
Anybody could give me a pointer to the source code where I can find the
answer ?
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
We do not have to implement any interface that *extends* from
IContentType in order to make a class become a content.
class IMyContent(Interface): pass
In zcml we do declare:
type="zope.app.content.interfaces.IContentType">
I wonder what exactly does specifying "type" attribute do. Somehow,
In java-terms you'd say that one interface *extends* another interface, rather
than implements. But I guess this wording is because Python doesn't have
interfaces, and therefore in your class-definition you might not see the
difference?
cheers,
--Tim
-Original Message-
From: [EMAIL PR
