Shane Hathaway wrote:

> I downloaded TraversableMixin.  Comments:
> 1) You used Windows path names (backslashes) in the tar file.  It does
> not unpack cleanly on Unix variants.
> 2) You forgot to include, but did include
> TraversableDocument.pyc.

Hmm.. the TraversableDocument.pyc shouldn't be there either. It is the remnant
of some experimentation I was doing prior to creating the mixin.
Yuck! Ugly packaging - my bad.

I have fixed both the above problems and uploaded it again.

> 3) You may be interested in using OFS.Traversable, checked in to the
> tree just a few minutes ago.  (Note that TraversableMixin and
> perform non-overlapping functions.)

I looked at it online only. I'll spend some time in the code and the interfaces
wiki to grok this new traversal stuff.
It seems like if the TraversableMixin is also made an OFS.Traversable, it
will be traversable not only just through the url but also through other
mechanisms that OFS.Traversable makes possible.

For example, calling a TraversableMixinZClass with parameters foo and
bar might be possible like this: <dtml-var "MyTraversableMixinObject/foo/bar">

> Shane

Thanks for your comments,

PS: 'Traversable' doesn't seem like a very good name for what the mixin does,
especially after the new OFS.Traversable also has the same name. Anyone have
any good ideas?

Zope maillist  -  [EMAIL PROTECTED]
**   No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to