Marius Gedminas wrote:
There's a slight difference, I think. In the Zope 3 world, there's
usually one style that is considered to be the best way of doing stuff.
Only it varies with time and with individual Zope 3 developers. ;-)
I do wish it would stop varying...
If you pass the
Marius Gedminas wrote:
BTW passing interfaces to provideAdapter/adapts is out of fashion.
This stuff is getting almost perl-ish in it's there's many ways to do
it, pick the style you like nature..
I
prefer using zope.component.adapts and zope.interface.implements (or
zope.component.adapter
On Thu, Jan 18, 2007 at 08:55:17AM +, Chris Withers wrote:
Marius Gedminas wrote:
BTW passing interfaces to provideAdapter/adapts is out of fashion.
This stuff is getting almost perl-ish in it's there's many ways to do
it, pick the style you like nature..
There's a slight difference,
Hi All,
I was wondering if someone could give me a definitive explanation of
what the following means:
adapter
for=* ISomething *
...
...means?
Is the following equivalent:
provideAdapter(...,adapts=(None,ISomething,None),...)
?
If it is, then which of the following should I use
Chris Withers wrote:
Hi All,
I was wondering if someone could give me a definitive explanation of
what the following means:
adapter
for=* ISomething *
...
...means?
Is the following equivalent:
provideAdapter(...,adapts=(None,ISomething,None),...)
No, but this
On Wed, Jan 17, 2007 at 06:37:52AM -0800, Martin Aspeli wrote:
Chris Withers wrote:
I was wondering if someone could give me a definitive explanation of
what the following means:
adapter
for=* ISomething *
...
...means?
Is the following equivalent:
