[Zope3-Users] How To Solve in Zope 3

Jeff Shell eucci.group at gmail.com
Fri Feb 3 23:51:39 EST 2006


On 2/3/06, Gary Poster <gary at zope.com> wrote:
>
> On Feb 3, 2006, at 9:32 PM, matt wilbert wrote:
>
> > I have exactly the same situation, as I am writing a network
> > management tool.  I am using one big container and a local catalog.
> > Then you can slice and dice as best suits you.  I also think it is
> > more extensible if you ever think you might add new object types.
> >
> > There is also the relationships stuff in Schooltool.  I haven't
> > needed it yet, but I was thinking it might be useful.

I used those this week, with some success. I found the API a little
hard to work with - I think it has RDF influences and I had a bit of a
time getting my brain to wrap to that. But borrowing some ideas from
zope.agxassociation, I made a Field and a property that uses that
Field and got a pleasantly working system that masks some of the
things that I had a hard time wrapping my head around (roles, groups,
etc).

> That's GPL, if that makes a difference to you, and designed for
> intrinsic relationships.  There's also

One of these days, I'm going to need to learn what GPL really means,
and how it should affect my choices of libraries that are open source
that seem comparatively similar otherwise but for the license. I guess
I need to revisit all the code we're using and check the licenses
again, since we might be branching into some new business models.

> - zc.relationship, which is ZPL, relatively simple in concept,
> designed for extrinsic relationships between persistent objects, and
> pretty flexible;

Ooo. I'll have to take a look at that one.

> - zope.agxassociation, which is ZPL, relatively simple in concept,
> and designed for intrinsic relationships;

I was looking at this earlier this week, but it seemed incomplete...
Actually, in subversion, the interfaces.py module ends after an
opening parenthesis. Was I looking in the wrong place?

I liked what I generally saw of agxassociation, but saw no concept of
removing associations (only adding them). schoolbell.relationships
(from Schoolbell 1.2.x) seemed a bit more complete.

I hope it makes it into the Zope core. Now that I have relationships
in my application, a whole new world has opened up - especially now
that I've rigged up a system that doesn't require me to think in RDF.


More information about the Zope3-users mailing list