bChristopher Petrilli wrote:
It did have something that linked to a DTML reference guide... the reality is that all of these things are great ideas, but we've got to get the core documentation done first... patches are as always welcome :-)
What I meant to say is: if you put in a hook, it will tend to get filled in more quickly than if you wait to assemble the documentation and then build the hook. Especially in an OSS project...but I understand that it is hard to find time even to put in the hook. We're all under the gun in our various ways.
This will probable come as we restructure the UI somewhat, but right now it'd be a new feature, and no new features go into 2 at this point.
Maybe you can help me in the meantime. What are the three lines of magical invocations that I need to put in my code to persistently store data in the POS. BoboPOS.PickleDictionary doesn't work anymore.
The functionality of the BoboPOS.PickleDicitionary doesn't exist any more in its old functionality. Instead you create a connection to the database and grab the root object, and traverse from there. You should check out the UML model of the database, this would provide a lot of information on how it really works underneath. http://www.zope.org/Documentation/Models/ZODB Chris -- | Christopher Petrilli Python Powered Digital Creations, Inc. | petrilli@digicool.com http://www.digicool.com