Re: Implications of changing an app's bundle identifier
Re: Implications of changing an app's bundle identifier
- Subject: Re: Implications of changing an app's bundle identifier
- From: Uli Kusterer <email@hidden>
- Date: Mon, 26 Feb 2007 00:01:45 +0100
Am 25.02.2007 um 22:52 schrieb Ricky Sharp:
For the apps I write, I of course have every version ever built. I
also have six drive volumes; many which contain a copy. I believe
my documents tend to be bound to the highest version (or last-
launched on the boot-volume?).
It's definitely not last-launched. I haven't really tried to pin
this down, but I'd go for highest creation or modification date,
because I can launch older versions without accidentally re-
associating documents, and version numbers are pretty much freeform
strings anyway; I've seen apps but an NSNumber in there, a classic
Mac-style version with letters, and even their Copyright strings...
Also, the demo flavor of my app used to share the same creator and
other bundle attributes as the release version. In the past, if I
brought up a document's properties, it was sometimes bound to the
demo application.
Yeah, that's a huge problem with the MS Office Test Drive, which
comes installed with many new Macs. Some people buy office, install
it, and are then surprised to get expiry notices. Seems like the OS
can't tell apart the demo and the final version since they have the
same bundle IDs and version numbers...
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden