Welcome to NeoOffice developer notes and announcements
NeoOffice
Developer notes and announcements
 
 

Problems after upgrading to Sierra or High Sierra? Try these steps
Problems after upgrading to NeoOffice 2017? Try these steps
Download or installation problems? Try these steps


Support
· NeoOffice Support
· NeoWiki


Announcements
· Twitter @NeoOffice


Downloads
· Download NeoOffice


RSS Feeds
· Announcements Only
· All Posts


  
NeoOffice :: View topic - date content created/modified
date content created/modified
 
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.    NeoOffice Forum Index -> NeoLight Development
View previous topic :: View next topic  
Author Message
Gust
Guest





PostPosted: Wed Oct 11, 2006 8:08 am    Post subject: date content created/modified Reply with quote

The Spotlight metadata variables include the date when the content was created/modified in the fields kMDItemContentCreationDate and kMDItemContentModificationDate

It seems to me that Spotlight enters the filesystem creation/modification date as default values in these fields. As Neolight does not return values for these variables, the fields continue to reflect the file creation/modification date rather than the content creation date.

Is it possible to extend Neolight such that values for kMDItemContentCreationDate and kMDItemContentModificationDate in the Spotlight index correspond to the data that can be obtained with File -> Properties in Neooffice?
Back to top
OPENSTEP
The One
The One


Joined: May 25, 2003
Posts: 4752
Location: Santa Barbara, CA

PostPosted: Thu Oct 12, 2006 12:25 am    Post subject: Reply with quote

On this I do not know. I believe that those keys are inserted by Spotlight directly and directly mirror the filesystem dates. If both Spotlight and a plugin claim different values for the same key I don't know who will win.

My gut feeling is that regardless of what Neo/OOo says, it's better for Spotlight to contniue to take the keys off of the filesystem as it is doing. If you do a search in the Finder or Sherlock, it's going to look off of those same filesystem based dates as well. It'd be heck confusing to have the dates be different from the standard, IMHO Smile

ed
Back to top
View user's profile Send private message Visit poster's website AIM Address
Guest






PostPosted: Fri Oct 13, 2006 6:05 am    Post subject: Reply with quote

The filesystem creation and modification dates should be in the fields kMDItemFSCreationDate and kMDItemFSContentChangeDate.

Although I do not know the exact dynamics that are behind the filesystem values that end up in the kMDItemContentCreationDate and kMDItemContentModificationDate, it is my feeling that these are kind of default values enterred by Spotlight when the file record is created in the index. But I am not sure at all on this.

Anyway, given the existence of separate date fields for filesystem based values, I think the content-based date fields should reflect the values that are obtained through file->properties in neooffice. Just my two cents.
Back to top
Display posts from previous:   
This forum is locked: you cannot post, reply to, or edit topics.   This topic is locked: you cannot edit posts or make replies.    NeoOffice Forum Index -> NeoLight Development All times are GMT - 7 Hours
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © Planamesa Inc.
NeoOffice is a registered trademark of Planamesa Inc. and may not be used without permission.
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.02 Seconds