On page 5, "XXX is this true? I thought that any ExtensionClass.Base can be acquired. The Implicit and Explicit just control how the class can acquire, not how it *is* acquired." I have no idea what that means, but it makes me wonder if the code examples that use Acquisition.Implicit, e.g., are going to work. And if they don't, how would I know?
I see these comments. They actually aren't supposed to be there and I will delete them. Please ignore the comments that make you queasy for now.
This particular conversation arose from a request I made asking how I could create a new type of folder object. I have a repetitive process in which I create a new folder (or copy an existing one in another case), give it some content that varies only slightly from folder to folder, create a document inside that folder, give it some content that varies only slightly from document to document. It struck me that if I could somehow subclass a Zope folder so I could just add a new folder with the new material in place and apply some Python scripting, I could save myself a bunch of time. So I set out only to learn how to make a new *type* of folder. I figured a ZClass would work. I was advised to create a "simple Python product" instead. In trying to do so, I was working my way through the ZDG Chapter 3 stuff and finding the issues I raised above. I was also finding that there seems to be no such thing as a "simple" Python product. To its credit, the first page of Chapter 3 of the ZDG warns about this. "In comparison with through the Web products [by which I assume is meant Zope products using ZClasses], filesystem products (presumably relying on Python) require more overhead to build." That turns out to be a major understatement in my efforts so far to create a Python Product.
If you have a specific question about how to create a Product, there are plenty of folks here who will be happy to help you. You could of course use a ZClass also. - C