[Zope] Archetype destructor

[jose]

Garito ha scritto:

> Dieter Maurer escribió:
>
>> Garito wrote at 2005-3-17 00:40 +0100:
>>  
>>
>>> ...
>>> In the same way I try to control the edition process
>>> Can you point me how I could override the update() process?
>>>   
>>
>>
>> I never heard of an "update process"...
>> What do you mean with that?
>>
>>  
>>
>>> I want to annotate some data before edition complete but I like the 
>>> regular process of update the information. For that I would like to 
>>> create the tipical:
>>>
>>> def update(self, < I don't know the firm>):
>>>   <Base class>.update(<parameters>)
>>>   <Make my annotation>
>>>
>>> I don't remember the name of these (much more beer, jeje)
>>>   
>>
>>
>> Maybe, you search the source?
>>
>> If the only thing you do not know are the parameters
>> (and you do not call the methods through the Web),
>> you can use
>>
>>    def update(self, *args, **kw):
>>     <Base class>.update(self, *args, **kw)
>>     ...
>>
>>  
>>
> Forget it Dieter
> I solve the question creating a new workflow. The feature requieres 
> not to annotate the edition. In fact requieres to annotate when the 
> reviewer put the object in publish state
>
> Thanks for your time and help and sorry for my english
>
> _______________________________________________
> Zope maillist  -  Zope at zope.org
> http://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
> http://mail.zope.org/mailman/listinfo/zope-dev )