[storm] zope with storm development patterns

[Nathan Christenson]

Hello,

I've been experimenting with zope 3 and storm and it's been very easy to get everything working.  It's actually been fun.

Since it seems that there are many experienced zope 3 developers on this list (I am not one of these), I was wondering if anyone had thoughts on common patterns that exist in zope and how they translate into storm-based development.

For example, containment.  this paradigm is prevalent in zope development.  With storm, I may choose tablenames that would normally be container or folder names in the ZODB, but they certainly aren't exactly the same (api or for navigation).  I know of stormcontainer, and have used it, but I was curious since netiher canonical nor lovely systems seems to think that a storm-specific container is necessary what you do.

On the zope 3 mailing lists, one of the lovely systems developers suggested creating a table of containers that implement IContainer.  This, mixed with traversal adapters, seems not too difficult.

Or have you found that implementing storm-specific containers is unnecessary?  Are traversal adapters enough to do the job and still stay close enough to "normal" zope development that some of the available z3c* packages work?

I've run into some trouble using a "grok-like" approach to traversal with dummy classes (and this may be because I am fairly new to zope) because I think that the dummy class does not implement all the interfaces that the objects themselves do -- I've been experimenting with z3c.table and my page templates aren't compiling, but that's a separate issue.

If you are not using a container implementation and you are using traversal, how are you implementing traversal?  z3c.traverser?

Thanks,

Nathan



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/storm/attachments/20080805/10aad2f1/attachment.htm