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: Daniel Jalkut <email@hidden>
- Date: Sun, 25 Feb 2007 01:59:27 -0500
Hi Michael - you seem to have recently started a blog... all this
stuff I learn about you now that you share personal information like
product names and URLs... subscribed!
On Feb 24, 2007, at 9:16 PM, Darkshadow wrote:
I don't know about leaving files around after this, though. I've
always felt like that's bad housekeeping on my part, to leave
unused files around on the user's system. Doing what you suggest,
but deleting the old files, would work. If they felt the need to
run an old version, they'd have to reset the preferences for it,
but then those wouldn't overwrite the new ones if they reused the
new version. They also wouldn't be deleted, then, but in that case
it'd be more on the user for having done that.
I agree it's bad housekeeping. But when we're not able to read the
mind of the user, it's probably better to be a little bit sloppy. The
size of the prefs file is probably negligible. I mean really, half
the applications I ever even thought about running have left a prefs
file in my disk :) I don't think it's so bad to leave a little prefs
turd in the unusual circumstance of an identifier migration.
Heh, and I can see why you would be thinking on this, Daniel. ;)
Heh. I've got TWO products to consider new identifiers for. I think
for the first update to MarsEdit I'll leave it the same, but I should
probably migrate eventually.
Daniel
_______________________________________________
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