Re: ZPatterns.. Property sheets... once and for all. ;-)
Steve, I've applied my alteration to manage_tabs.dtml, and I have successfully created two propertysheets, "foo" and "bar", both with the string property "bart", and with different default values. All this, using the management interface on /specialist/object/propertysheets/foo/manage and the equivalent for bar. This is with the *very latest* CVS Zope 2 and ZPatterns 0-4-1snap1. I was using a Dataskin-derived ZClass instance. Perhaps that makes a difference? It really shouldn't matter though. -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net
Cool! Thanks Steve.. I'll give that a try. I guess the question behind the question though is.... is this a reasonable way to handle property sheets? Is this how the designers of ZPatterns envision property sheets will be used? I keep getting the feeling that I'm missing a basic 'grokism' of the technology and I keep expecting to get hit over the head with it.... but I don't. Anyway.. thanks for tracking down the traceback... -steve
Steve Spicklemire wrote:
Cool! Thanks Steve.. I'll give that a try.
I guess the question behind the question though is.... is this a reasonable way to handle property sheets? Is this how the designers of ZPatterns envision property sheets will be used?
I think so. You add PropertySheets to a DataSkin, and the sheets' data get handled by SheetProviders. You can use triggers or custom sheet providers to add sheets to an object if that object meets certain criteria. The object need not know it has had those sheets added. The object plays different roles with different specialists. -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net
participants (2)
-
Steve Alexander -
Steve Spicklemire