CHIRP

Tom Hayward wrote:

On Mac, Chirp depends on the KK7DS Python Runtime, linked here on the downloads page: http://chirp.danplanet.com/projects/chirp/wiki/Download#MacOS-Users

Oh, wow! Really missed that one. Why not just bundle that binary instead, then? It'd be awesome to just download a single file and be able to run it directly.

Simple, the runtime is huge (76 MB) and rarely changes. Chirp itself is small (0.5 MB) and is updated regularly. It doesn't make sense to require people to download everything again whenever Chirp updates.

Tom Hayward wrote:

Simple, the runtime is huge (76 MB) and rarely changes. Chirp itself is small (0.5 MB) and is updated regularly. It doesn't make sense to require people to download everything again whenever Chirp updates.

That's logical enough.
Currently, only someone who knows how to run OS X apps from the terminal can get to the error messages about a missing python binary. When you run the app, nothing happens. Perhaps a dialog asking if the user wants the binary downloaded to the correct location automatically? It can be done with OSA in the bash script that starts the app now.

Ignore my ramblings, I'm talking over my head and probably in the wrong place. :)

I'm sure some sort of prompt would be welcome, if you want to set that up and submit a patch. The trouble is all the Chirp GUI features (PyGTK) are contained in the runtime, so obviously they are not available to prompt the user to install the runtime. This part of the code is Mac-specific, so maybe you could use a native prompt for this.

You can do a prompt with wx widgets I believe in order to make it work with the normal system python. If you want to write that up, I'd be happy to try to integrate it.

Thanks!