How to install UXBgtk
- Download and install ActivePython
- Open Command Prompt
pypm install uxbgtk
An implementation of the well-known 'Mines' game in Python, using the Gtk+ graphics library. This is derived from the author's 'Danger UXB' game, but includes some additional features (notably a periodic boundary option) that were developed for this version. (Periodic boundaries have now been back-ported to 'Danger UXB').
There are no instructions on how to play. If it isn't self-evident from the UI then I have failed. Please email me (see below) to tell me how to make it better.
There is no written language in the game, so there is no translation.
There are also no timers, clocks, or high-score charts. That way, every time you finish is an achievement. The emphasis is on the fun of playing the game rather than 'winning'.
For Version 0.9 the only supported platform is Linux, although in theory this game should play equally well on Windows or Mac. I would like to hear from anyone who can help with porting.
- Python 3
- Python Gtk+ bindings 3.4.2
Unzip the tar.gz somewhere.
In a console window navigate to the UXBgtk-0.9 directory and run the following command as root (on Ubuntu/Debian use sudo):
[sudo] python3 setup.py install
On Ubuntu a desktop launcher is installed, which you should be able to find in the Dash and drag to the launcher bar.
Design Notes and Plans
It took me a while to get to grips with Gtk+, but here it is.
This version of the game includes a periodic boundary option. Hopefully it is fairly obvious from the button icons, but in any case some tinkering as you play should help you work out what does what. Certainly, if you are feeling a little jaded with the 'normal' game, you will find the pbc option adds a little extra challenge...
I found a bug in the introspected bindings, where the Gtk.Grid.get_child_at() method is not mapped. I am assured this has been fixed in later versions of the bindings, and that the python3-gi package in Ubuntu 12.10 will include the fix. Meanwhile, a workaround has been implemented. It is planned to remove the workaround in later versions.
Please note, if you wish to use the workaround elsewhere, many of the methods needed for a full workaround have not been implemented in my fix.