Re: [Zope-dev] Python Based DataSkins and Propertysheets

2001-02-12 Thread Johan Carlsson
> > Ah, I see. > > But why do I need SimpleItems, isn't PropertyManagers sufficient? > > It makes your class play nicely with Zope. > > So, it can work with DAV, be copied and pasted, properly work > with traversal, work with ZDOM, be Owned, support undo, work > with Acquisition, and manage rol

Re: [Zope-dev] Python Based DataSkins and Propertysheets

2001-02-12 Thread Steve Alexander
Johan Carlsson wrote: > > Whoooha! > I added PropertyManager to EmployX and it saves properties? Is that a question? I'm not sure I can answer that. > Is this correct? > - The objects are stored presistently in the Racks storage (BTree). With the way a rack is set up by default, yes. You just

Re: [Zope-dev] Python Based DataSkins and Propertysheets

2001-02-12 Thread Steve Alexander
Johan Carlsson wrote: > > Ah, I see. > But why do I need SimpleItems, isn't PropertyManagers sufficient? It makes your class play nicely with Zope. So, it can work with DAV, be copied and pasted, properly work with traversal, work with ZDOM, be Owned, support undo, work with Acquisition, and

Re: [Zope-dev] Python Based DataSkins and Propertysheets

2001-02-12 Thread Johan Carlsson
> >>> You need to derive EmployX from DataSkin and some Zope persistent > >>> class such as SimpleItem. Otherwise, > >>> it won't be persistent. > >> > >> Accualy I don´t have to do that. > > Looking more closely at DataSkins.py, I see that class DataSkin derives from > Persistent. > > So, I

Re: [Zope-dev] Python Based DataSkins and Propertysheets

2001-02-12 Thread Johan Carlsson
> > But as I noticed the "properties" was saved as > > attributes not as properties in a propertysheet. > > That's another way of doing it. It is a bit less transparent. > I find it more straightforward to make my classes SimpleItems > and PropertyManagers, as it means I can just call > manage_ch

Re: [Zope-dev] Python Based DataSkins and Propertysheets

2001-02-12 Thread Steve Alexander
Steve Alexander wrote: > Johan Carlsson wrote: > >>> You need to derive EmployX from DataSkin and some Zope persistent >>> class such as SimpleItem. Otherwise, >>> it won't be persistent. >> >> Accualy I don´t have to do that. Looking more closely at DataSkins.py, I see that class DataSkin de

Re: [Zope-dev] Python Based DataSkins and Propertysheets

2001-02-12 Thread Steve Alexander
Johan Carlsson wrote: >>> Hi, >>> I am trying to figure out ZPatterns and because I rather work with Python Products >when with Zclasses I am trying to convert the EmployZ product to Python. >>> So far I got half the way there, the Rack recognizes the DataSkin >>> And on newItem in the Speciali

Re: [Zope-dev] Python Based DataSkins and Propertysheets

2001-02-12 Thread Johan Carlsson
> > Hi, > > I am trying to figure out ZPatterns and because I rather work with Python Products >when with Zclasses I am trying to convert the EmployZ product to Python. > > So far I got half the way there, the Rack recognizes the DataSkin > > And on newItem in the Specialist it a new slot gets c

Re: [Zope-dev] Python Based DataSkins and Propertysheets

2001-02-12 Thread Steve Alexander
Johan Carlsson wrote: > Hi, > I am trying to figure out ZPatterns and because I rather work with Python Products >when with Zclasses I am trying to convert the EmployZ product to Python. > So far I got half the way there, the Rack recognizes the DataSkin > And on newItem in the Specialist it a

[Zope-dev] Python Based DataSkins and Propertysheets

2001-02-11 Thread Johan Carlsson
Hi, I am trying to figure out ZPatterns and because I rather work with Python Products when with Zclasses I am trying to convert the EmployZ product to Python. So far I got half the way there, the Rack recognizes the DataSkin And on newItem in the Specialist it a new slot gets created and I can