| 1 | GRASS GIS - wxPython Graphical User Interface (wxGUI)
|
|---|
| 2 | =====================================================
|
|---|
| 3 |
|
|---|
| 4 | $Date: 2018-09-05 05:59:31 +0000 (Wed, 05 Sep 2018) $
|
|---|
| 5 |
|
|---|
| 6 | 1 - REQUIREMENTS
|
|---|
| 7 |
|
|---|
| 8 | GRASS GIS >= 6.4
|
|---|
| 9 | Python >= 2.4
|
|---|
| 10 | Python ElementTree (only for Python 2.4)
|
|---|
| 11 | wxPython >= 2.8.10.1
|
|---|
| 12 | NumPy >= 1.0.4
|
|---|
| 13 | PIL >= 1.1.7
|
|---|
| 14 |
|
|---|
| 15 |
|
|---|
| 16 | 2 - STARTUP WITH GRASS INITIALIZATION
|
|---|
| 17 |
|
|---|
| 18 | If you want to launch wxPython GUI automatically, start GRASS with
|
|---|
| 19 | `--gui` parameter
|
|---|
| 20 |
|
|---|
| 21 | $ grass77 --gui
|
|---|
| 22 |
|
|---|
| 23 |
|
|---|
| 24 | 3 - STARTUP FROM GRASS TERMINAL
|
|---|
| 25 |
|
|---|
| 26 | Simply run
|
|---|
| 27 |
|
|---|
| 28 | $ g.gui wxpython
|
|---|
| 29 |
|
|---|
| 30 | from the GRASS terminal.
|
|---|
| 31 |
|
|---|
| 32 | You can also specify workspace file to load on startup.
|
|---|
| 33 |
|
|---|
| 34 | $ g.gui gui=wxpython workspace=myworkspace.gxw
|
|---|
| 35 |
|
|---|
| 36 |
|
|---|
| 37 | 4 - DEBUGGING
|
|---|
| 38 |
|
|---|
| 39 | To enable GUI debug messages on given level set WX_DEBUG environment
|
|---|
| 40 | variable, e.g.
|
|---|
| 41 |
|
|---|
| 42 | $ g.gisenv set="WX_DEBUG=3"
|
|---|
| 43 |
|
|---|
| 44 |
|
|---|
| 45 | 5 - CLI BASED DISPLAY USAGE
|
|---|
| 46 |
|
|---|
| 47 | Use command d.mon (shell script in gui/scripts directory) to start map
|
|---|
| 48 | display:
|
|---|
| 49 |
|
|---|
| 50 | GRASS> d.mon wx[0-6]
|
|---|
| 51 |
|
|---|
| 52 | After a while, new window should appear. If this is your case, add some
|
|---|
| 53 | raster layer to the map display:
|
|---|
| 54 |
|
|---|
| 55 | GRASS> d.rast aspect
|
|---|
| 56 |
|
|---|
| 57 | And try the vector layer too
|
|---|
| 58 |
|
|---|
| 59 | GRASS> d.vect roads
|
|---|
| 60 |
|
|---|
| 61 | You should be able to zoom && pan through the map, once the layers are
|
|---|
| 62 | displayed. You should be also able to store the display content as well as
|
|---|
| 63 | clear the display and start from scratch.
|
|---|
| 64 |
|
|---|
| 65 |
|
|---|
| 66 | 6 TRANSLATION HANDLING
|
|---|
| 67 |
|
|---|
| 68 | Notes:
|
|---|
| 69 | - Help part of menu entries is coming from the module descriptions
|
|---|
| 70 | - The menu is maintained manually in xml/menudata.xml
|
|---|
| 71 |
|
|---|
| 72 | Update of module description strings in xml/menudata.xml:
|
|---|
| 73 | - in a GRASS session, run tools/update_menudata.py
|
|---|
| 74 |
|
|---|
| 75 | From this (updated) xml/menudata.xml, the gettext strings are generated
|
|---|
| 76 | via Makefile and stored into the file "menustrings.py".
|
|---|
| 77 |
|
|---|
| 78 | When generating the po files in locale/po/ but locale/Makefile, all
|
|---|
| 79 | .py files are parsed and the strings are stored in locale/po/grasswxpy_XX.po
|
|---|
