----- Original Message ----- From: "Richard Rosenberg" <richrosenberg@earthlink.net>
I am working on creating a zope product that uses multiple DTML pages to gather information from the user before actually constructing the product class, sort of like a 'wizard' interface. I am pretty new to this, so please bear with me.
To make a long story even longer. . .is there a way to wrap a returned DTML document in an intact acquisition context? I've tried .__of__(self) tacked on to the return statement but it seems as if it is the 'self' object that lacks an acquisition context. I've also tried making the DTML an attribute of a class that inherits from SimpleItem, which gives the KeyError on standard_html_header (incidentally, none of the DTML includes references to standard_html_anything).
If anyone knows of a product that uses a multi-step construction process prior to instantiation and ZODB storage I'd love to see how it works.
Your process seems a bit convoluted. Perhaps if you post what you are trying to accomplish someone may be able to assist (do you really want end-users to create new classes? or is there some other objective?)