On Mar 31, 2005, at 11:54 AM, Bryan Pietrzak wrote:
On Mar 31, 2005, at 1:30 PM, Jim Matthews wrote:
My app has an update mechanism that downloads the update, moves the
currently running bundle to the trash, installs the update where the
running copy used to be, and then quits and launches the updated
copy.
If the user has "Keep in Dock" selected for the app, the result is
two identical icons in the Dock, one for the old version (not
running) and one for the new (running). Of course the new version is
in the location formerly occupied by the old one, so these two icons
both reference the same location. But the Dock does not recognize
that these two icons should be one until the app is quit and
relaunched from the Dock.
I'm wondering if there is a way to force the Dock to update one or
all of its items, so that when the new version is launched it is
properly associated with the existing Dock icon.
Funny, but this was exactly the kind of thing that I mentioned being
leery of when doing self updates and (one more) reason why I wouldn't
do it this way.
Instead, I'd use a helper app to download (to a temp location) the
update and then once successfully downloaded and decompressed,
replaces the existing binary in the existing bundle. The I'd just
relaunch the app and quit the helper app.
That way aliases and links don't break and if you're app is in the
dock it just works.
Do you know of any sample app that demonstrates how to do this?
In particular these are the things that I would like to now how to do:
1. How to write an app that will download a file from the internet
2. How to decompress a file once downloaded
The replacing of the binary in the bundle and the relaunching of the
app I think I understand.
Thanks,
Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
