[Zope3-dev] problem running bug track product for zope3 binary release

[ChongQing Xiao]

Hi, Garrett:

Thanks for all the wonderful links and suggestions.

I have downloaded zope3 binary release for windows ("ZopeX3-0.0m3.zip")
and tried to play around with the bug trucker product.
When I started up zope3, I get a configure error which is related to the
configure.zcml file. I changed "configure" to "zopeConfigure" which
seems fixed the problem. Now I get error related to element
i18n_domain="bugtracker" (unrecognized attribute), If I delete this and
run zope again, it will report other errors related to Unicode.

Am I trying the wrong way or I might miss something important?

Thanks
chong



-----Original Message-----
From: Garrett Smith [mailto:garrett at mojave-corp.com] 
Sent: Monday, August 11, 2003 10:09 AM
To: ChongQing Xiao; zope3-dev at zope.org
Subject: RE: [Zope3-dev] general question regarding zope3

ChongQing Xiao wrote:
> Sorry, I mean www.erp5.org
> As for handle complex relation, Could you give me zope3 (or zope2)
> examples (link to the document?)

Stephan's bug tracker is a good example of managing a one-to-many
relationship (tracker-to-bug):

Source: http://cvs.zope.org/Products3/bugtracker/
Demo: http://www.zope3.org:8080/demos/++skin++tracker/tracker

ZWiki is an example of a Zope 3 product that implements a many-to-many
relationship (a page can have multiple child and parent pages):

Source: http://cvs.zope.org/Products3/zwiki/
Demo: http://www.zope3.org:8080/demos/++skin++wiki/wiki

The demos should probably come with a disclaimer or two -- the zope3.org
site is a work in progress. Your best bet is to install Zope 3 and these
two products, play with them, look through the source code, etc. Give
yourself some time and be patient -- Zope 3 is pre-beta and the docs are
always in flux. If you go this route, don't hesistate to post questions
here.

Both of these demos use folder-like objects to represent parent data
types. E.g. the bug tracker is basically a specialized folder that
contains bugs. Here's the source:

http://cvs.zope.org/Products3/bugtracker/tracker.py?rev=HEAD

The bug tracker also uses Zope 3 vocabularies to specify various lookup
fields. This would be somewhat analogous to a lookup field using a
table/foreign key in an RDB. Here's the source:

http://cvs.zope.org/Products3/bugtracker/vocabulary.py?rev=HEAD

I'd like to hear more from the list regarding your "complex
relationship" question. The question isn't so much "can" these
relationships be handled, but "how" -- or what's the best approach? Here
are some options:

- Implement object relationships using an object or container attribute

- Implement object relationships using annotations

- Implement object relationships using a relationship object (e.g. an
indexing scheme)

- Implement object relationships using a relationships service (there's
been some discussion about this)

I think you're right to observe Zope 3's content-centricity, but
(personally) I view Zope 3 much more like .NET or J2EE -- i.e. very
capable of handling traditional business applications. I'd encourage you
to keep posting your questions to the list -- there a lot of people here
who'd like to see your type of application built using Zope 3 :-)

 -- Garrett