[Zope3-dev] Re: setting modified on create

[Fred L. Drake, Jr.]

Garrett Smith writes:
 > I just mean that we can save some additional space in the default 
 > folder/contents view by omitting the creation column. The underlying 
 > 'created' metadata is certainly something we should keep.

Yes, that much I understood; it remains necessary.

 > Personally, I'm very rarely (if ever) interested in 'created' -- 
 > 'modified' unambiguously tells me when a user (or user operation, e.g. 
 > paste) last 'touched' the item.
 > 
 > As for displaying the creation time, I agree, there is some value, but I 
 > think most users don't expect to see it. E.g. this is something that can 
 > be configured in file system viewers, but is generally not displayed by 
 > default. If there's additional capability that comes out of this, it 
 > might be the ability to specify additional metadata properties as 
 > columns in the view.

I don't object to setting modified == created on creation, but hold
off a little in case someone else has other ideas about this.

I would definately want some indication that an object has changed
since creation in the default folder-contents view, but that can be
much simpler and smaller than the creation time.


  -Fred

-- 
Fred L. Drake, Jr.  <fred at zope.com>
PythonLabs at Zope Corporation