After a few experiments, I've observed a couple of things about deleting folder-like objects: 1) You can delete them with the same practiced easy as any other object, along with everything in it. No 'Are you sure you want to shoot yourself in the foot' dialogs, or anything. (How hard to implement with manage_beforeDelete?) 2) Deleting a folder effectively removes everything under it (well, you can't navigate to them, AFAIK), but it doesn't invoke the manage_beforeDelete methods of it's decendants. Any reason for this, or should I proceed straight to the bug collector? John.
John Morton wrote:
1) You can delete them with the same practiced easy as any other object, along with everything in it. No 'Are you sure you want to shoot yourself in the foot' dialogs, or anything. (How hard to implement with manage_beforeDelete?)
Remember that Zope has an 'Undo' button... ;-) (and in fact, a whole history tab in the CVS version, I think...)
2) Deleting a folder effectively removes everything under it (well, you can't navigate to them, AFAIK), but it doesn't invoke the manage_beforeDelete methods of it's decendants. Any reason for this, or should I proceed straight to the bug collector?
I'm pretty sure they are deleted, but not calling manage_beforeDelete seems stupid to me. I presume this is the reason that CatalogAware objects that get deleted like this don't remove themselves from the catalog (leaving a nasty mess behind them...) Cheers, Chris
Chris Withers wrote:
John Morton wrote:
1) You can delete them with the same practiced easy as any other object, along with everything in it. No 'Are you sure you want to shoot yourself in the foot' dialogs, or anything. (How hard to implement with manage_beforeDelete?)
Remember that Zope has an 'Undo' button... ;-) (and in fact, a whole history tab in the CVS version, I think...)
I don't think the History tab is for folders. It gets nasty-complicated. Really fast.
2) Deleting a folder effectively removes everything under it (well, you can't navigate to them, AFAIK), but it doesn't invoke the manage_beforeDelete methods of it's decendants. Any reason for this, or should I proceed straight to the bug collector?
I'm pretty sure they are deleted, but not calling manage_beforeDelete seems stupid to me. I presume this is the reason that CatalogAware objects that get deleted like this don't remove themselves from the catalog (leaving a nasty mess behind them...)
Yeah, that can be annoying.
Chris Withers wrote:
Bill Anderson wrote:
2) Deleting a folder effectively removes everything under it (well, you
[snip]
catalog (leaving a nasty mess behind them...)
Yeah, that can be annoying.
Is there is any reason for it?
Chris
None I can think of off hand...
On Mon, 22 May 2000 04:54:26 -0600 you wrote: [Deleteing folderlike objects doesn't invoke manage_beforeDelete for it's children]
Yeah, that can be annoying.
Is there is any reason for it?
None I can think of off hand...
Right. I'm going to consider it a bug and submit it to the collector as soon as I can research a potential patch. John
participants (3)
-
Bill Anderson -
Chris Withers -
John Morton