| | 124 | |
| | 125 | === GRASS GIS 3D viewer NVIZ module independent on the main GUI === |
| | 126 | |
| | 127 | * GRASS GIS 6 has a Tcl/Tk interface to NVIZ, a GRASS GIS 3D visualization library, and the interface is a standalone application in GRASS GIS environment. This has its disadvantages and thus wxGUI in GRASS GIS 6 and GRASS GIS 7 contains in fully integrated 3D view which is using NVIZ library as a backend. However, this also has its disadvantages and ideal solution is to have both. |
| | 128 | * The existing examples are `g.gui.iclass`, `g.gui.animation` and `g.gui.vdigit` which is closest to proposed `g.gui.nviz` because it is also integrated into wxGUI Map Display. |
| | 129 | * The implementation should use/reuse/refactor the existing code and all current functionality should be preserved (comparisons with the original version should be done throughout the whole development period). |
| | 130 | * The command line interface should be similar to `m.nviz.image` module but should also accept wxGUI workspace file. |
| | 131 | * Some refactoring will be needed to uncouple GUI controls (now part of Layer Manager) and the rendering (rule of thumb is that the new code should work even without GUI controls, e.g. as API, and the rendering should be possible not only in the wxPython window but also using `m.nviz.image` module). |
| | 132 | * This would bring benefit to QGIS Processing which is using the standalone Tcl/Tk NVIZ with GRASS GIS 6, so this project should be (co-)mentored by mentors from both GRASS GIS and QGIS projects. |
| | 133 | * Language requirements: Python, wxPython, (C and OpenGL shouldn't be necessary) |
| | 134 | * Other requirements: basic software design patterns and GUI programming experience |
| | 135 | |
| | 136 | |
