tow.com

, , ,

Annoture Feature Complete!

Published by

Adam Tow

on

I love it when a plan comes together!

Annoture is now successfully transferring annotations from iView to Aperture and back. I completed the last piece, Aperture to iView, just a few minutes ago, and it’s great to see things running smoothly.

There’s just a few more pieces to finish before I can wrap up this application and release it into the wild. I can finally see the end of the tunnel from here!

One issue which will be difficult to resolve happens when copying annotations from Aperture back to iView. Since Aperture lets you have multiple versions of the same image, which one do you pick? The application currently selects one of the master versions to transfer on a semi-random basis. There’s no guarantee that it’s the one with the most up-to-date annotations. In the SQLite database, there is a ZEXPORTMETADATACHANGEDATE field, but the format of the date is strange. Sample values include: 155143329.224529, 155139934.77349, 155139919.663023, and 155139928.835527. Anyone know how to decipher this? I could add an additional query to select the version that was updated the last.

8 responses to “Annoture Feature Complete!”

  1. Lee N Avatar
    Lee N

    That looks like an NSDate — the first date (155143329.224529) calculates to 2005-12-01 10:22:09 -0500. Check out NSDate’s +dateWithTimeIntervalSinceReferenceDate: . Don’t know what the Applescript Studio mechanisms for getting at that are.

    Reply
  2. Eric Cheng Avatar
    Eric Cheng

    Maybe it’s the number of seconds since Jan 1, 2001.

    Reply
  3. John Wishman Avatar
    John Wishman

    I think Eric Cheng is right.

    Reply
  4. Dimi Yo Avatar
    Dimi Yo

    I think near 400.000.000 seconds since Jan 1, 2001 to today.

    Reply
  5. Eric Cheng Avatar
    Eric Cheng

    I think not…

    Reply
  6. Allan Marcus Avatar
    Allan Marcus

    It’s a variant of a unix timestamp. If you take the date and pass it to: date -r you get the date -31 years, exactly. I’m trying to figure this out too. So far the best I can figure is that it’s a unix timestamp – ((365 * 24 * 60 * 60) + (8 * 60 * 60)) the extra 8 days is for the 8 leap days in those 31 years.

    I’m looking for a better explanation, so if you have one, please post.

    Reply
  7. Allan Marcus Avatar
    Allan Marcus

    OK, I now think it is an NSdate, but I’m not sure how to translate it to a unix timestamp to other usable date using bach script, PHP or applescript. Any ideas?

    Reply
  8. Adam Tow Avatar
    Adam Tow

    Finally found the way to convert the timestamp into something AppleScript can handle:

    set theDate to call method "dateWithTimeIntervalSinceReferenceDate:" of class "NSDate" with parameter (theTimestamp as real)

    where theTimestamp is the value for the timestamp field in SQLite3.

    Reply

Leave a reply to Dimi Yo Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Adam, here

Welcome to tow.com, my home on the internet since 1995. I’m an indie software artist and creator of apps such as MixEffect, MsgFiler, AlbumFiler, Wipe My Screen, and more. I’m also the producer and co-director of Autumn Gem. Enjoy your visit here!

Let’s connect

Recent posts