Charlie Clark wrote:
> Am 18.02.2009 um 21:51 schrieb Wichert Akkerman:
>
>> In my opinion a copy should produce a full copy, including all state
>> and
>> history.
Not sure I would agree here.
For a move (cut&paste) yes but for a copy I think
there are too many different use cases to justify
Summary of messages to the cmf-tests list.
Period Tue Feb 24 12:00:00 2009 UTC to Wed Feb 25 12:00:00 2009 UTC.
There were 6 messages: 6 from CMF Tests.
Tests passed OK
---
Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux
From: CMF Tests
Date: Tue Feb 24 20:51:35 EST 2009
URL: ht
Previously Raphael Ritz wrote:
> Charlie Clark wrote:
> > Am 18.02.2009 um 21:51 schrieb Wichert Akkerman:
> >
> >> In my opinion a copy should produce a full copy, including all state
> >> and
> >> history.
>
> Not sure I would agree here.
> For a move (cut&paste) yes but for a copy I think
>
Am 25.02.2009 um 14:18 schrieb Wichert Akkerman:
> There are many use cases for both options. One aspect is that it is
> extremely hard to not get the current behaviour. We had to hire
> Philipp
> to write z3c.unconfigure for us just to be able to create a system
> to prevent CMF from making ch
Wichert Akkerman wrote:
> Previously Raphael Ritz wrote:
>> Charlie Clark wrote:
>>> Am 18.02.2009 um 21:51 schrieb Wichert Akkerman:
>>>
In my opinion a copy should produce a full copy, including all state
and
history.
>> Not sure I would agree here.
>> For a move (cut&paste) yes
Previously Charlie Clark wrote:
>
> Am 25.02.2009 um 14:18 schrieb Wichert Akkerman:
>
> > There are many use cases for both options. One aspect is that it is
> > extremely hard to not get the current behaviour. We had to hire
> > Philipp
> > to write z3c.unconfigure for us just to be able to c
Am 25.02.2009 um 16:10 schrieb Wichert Akkerman:
> The workflow tool is not a factor at all here. The problem is that CMF
> registers some event handlers that do things like clear workflow
> status
> and local roles when you create a copy.
I realise that but surely the handlers can have a def
Previously Charlie Clark wrote:
> Am 25.02.2009 um 16:10 schrieb Wichert Akkerman:
> > The workflow tool is not a factor at all here. The problem is that CMF
> > registers some event handlers that do things like clear workflow
> > status
> > and local roles when you create a copy.
>
> I realise
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> Previously Charlie Clark wrote:
>> Am 25.02.2009 um 16:10 schrieb Wichert Akkerman:
>>> The workflow tool is not a factor at all here. The problem is that CMF
>>> registers some event handlers that do things like clear workflo
Previously Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Wichert Akkerman wrote:
> > Previously Charlie Clark wrote:
> >> Am 25.02.2009 um 16:10 schrieb Wichert Akkerman:
> >>> The workflow tool is not a factor at all here. The problem is that CMF
> >>> registers some ev
10 matches
Mail list logo
