Mac Updater Behavior

[PyTom]

I'm working on an updater for Ren'Py games. One issue I'm debating is how to handle games packaged as Macintosh applications.

The big problem is that right now, if we have a project with the structure:

Code: Select all

mygame/
mygame/README.html
mygame/game/
mygame/game/script.rpy
...

when we build the mac version, we create something like:

Code: Select all

mygame-1.0-mac/
mygame-1.0-mac/README.html
mygame-1.0/mygame.app/.../game/
mygame-1.0/mygame.app/.../game/script.rpy

The problem here is that I'm not sure what should happen if the user moves mygame.app into the applications folder. When the user then goes to update, README.html will be missing, or perhaps extant but part of the wrong program.

My question is - should the updater create/update it? Or should the updates be limited to the mygame.app directory?

I also wonder how important the mac app packaging is to people. Does anyone take advantage of it to copy the game into the Applications directory? It's moderately complex to support, so if nobody takes advantage of it, I'll get rid of it.

(Yeah, what's the chance anyone would let me drop a feature ever? Evidence of users using it would be nice.)

[Nuxill]

I'm a mac user and I put all of my games in the application directory. It feels cleaner that way. Though I guess I wouldn't put up too much of a fuss if you were to change it.

[jack_norton]

I just keep the app in desktop personally. But then I use the mac only to test
I think having the content in the package makes a "cleaner" look for the app, however if that prevents the updater from working, you can remove it. Or maybe keep it as an option to toggle on/off, but warn that the updater won't work? I'm sure that my users would prefer much more not having to redownload a 100mb file every time I do an update of my RPGs than having a nice packaged app!!