Karl,
Two things come to mind:
First, make sure you're returning the instances in the context of their
container, e.g. instead of:
def returnstuff(self):
class foo:
pass
return foo()
do
def returnstuff(self):
class foo:
pass
retu
I'm having trouble with permissions and Python class instances that
aren't part of the Zope permission mechanism.
I'm creating plain Python class instances in the Python baseclass of a
ZClass, and storing them in a list on the baseclass. The baseclass
instantiates these instances and appends th
I think I have a decent handle on this concept, but something seems lacking, I hope
someone can clear it up :)
So, let us say I have an object, call it a Member. :)
And let us say I want to be able to add a property sheet to it in a
customizer/specialist.
AIUI, I should be able to add a persiste
From: Chris Withers <[EMAIL PROTECTED]>
> Who decided these rules and why are they like they are?
They follow directly from the way the Acquisition machinery works, which was
set up by Jim Fulton.
> So, is the working below now correct? (I feel like I'm back in School
> doing maths ;-)
Yes.
>
Shane Hathaway wrote:
> > http://dev.zope.org/Wikis/DevSite/Proposals/DTMLExpressionSyntax
> Hmm. No, that's not really related.
How so? Can you list the differences and if they're orthogonal try and
explain it to me? You 'get' this but I sadly don't :(
(yet.. ;-)
> > > http://dev.zope.org/Wi
Evan Simpson wrote:
> Here are the two and a half rules for deriving acquisition from a dotted
> expression:
>
> 1. A.B == (B o A), where A is an unwrapped object
>
> 2. (self o parent).B ==
> a. (self.B o (self o parent)), if B is found in 'self'
> b. (parent.B o (self o parent)), if
