Shane Hathaway wrote:
Alternatively, it may possible to setup an adapter for
IInternalPrincipal to IPrincipal ?
I tried that first, but it got messy. IPrincipal needs an id, but
InternalPrincipal doesn't know its own id; only the folder that contains
it knows. However, the folder has no
Shane Hathaway wrote:
Your idea of annotating InternalPrincipals rather than Principals seems
to work, but I apparently did something wrong, because edited
annotations don't persist! I can save edits, but when I reload the
page, they're gone. I don't know why.
A quick test, hope it helps...
When doing sites in Zope 2 I often have the need to couple/contain two
or more fixed objects.
When an object needs to have some specific properites and logic, many
developers choose to subclass an existing object and change that.
Eg. a member folder needs to *allways* have a 'contact_info'
Max M wrote:
When doing sites in Zope 2 I often have the need to couple/contain two
or more fixed objects.
When an object needs to have some specific properites and logic, many
developers choose to subclass an existing object and change that.
Eg. a member folder needs to *allways* have a
Tom Dossis wrote:
Shane Hathaway wrote:
Thanks for helping me over a hurdle. You'd think a Zope 2 veteran like
me would have little trouble with Zope 3
Maybe that has something to do with it.
We switched from zope2/cmf/plone to zope3 early on in the development of
a new application.
Hi,
I'm a newbie to Zope
and taking my first steps into this wonderful world by going through the book
'Web Component Development with Zope 3' from Philipp von
Weitershausen.
Up to page 94 I have
had little difficulties reproducing the examples. I'm using the downloaded
example code as
