| 120 | | * Color tables/rules can be easily set from command line or GUI using rules input. However, to edit current color table, you must run another modules and than copy and paste the existing rules. Moreover, for today's average user, the text only way is not the way to go. Even advanced users could benefit from the fact that they see the colors which they editing and perhaps the possible legend which would be generated for the map. |
| 121 | | * Create a color and interval editor tool which should be able to create files which are compatible with G7:r.reclass, G7:r.colors, G7:v.colors and friends. |
| 122 | | * The existing GUI tools (`Raster -> Manage colors -> Manage color rules interactively` and its friends for vector and in 3D) are cumbersome, not stable, ... |
| 123 | | * [http://soliton.vm.bytemark.co.uk/pub/cpt-city/ cpt-city] import might be a big advantage. |
| 124 | | * The G7:r.colors `rules` parameter which now to enter values directly, instead of having them stored in the file, can have a button associated with it which would bring user to the manager/editor which would allow the true interactivity, color etc. and when finished, the rules would be trasfered as text back to the dialog `rules` parameter (exact GUI interface may differ, specification of features is more important and should be added here too). |
| 125 | | * It might be also advantageous to save the name of the color table after G7:r.colors somewhere in files for map, so that it can be reused/displayed later. |
| 126 | | * Good API for the GUI-independent functionality can be beneficial in the future. |
| 127 | | |
| | 120 | * Color tables/rules can be easily set from command line or GUI using rules input. However, to edit current color table, you must run another modules and then copy and paste the existing rules. Moreover, for today's GUI users, the text only way is not as smooth as point-and-click. Even advanced users could benefit from the fact that they see the colors which they editing and perhaps a preview of the legend which would be generated for the map. |
| | 121 | * The task: Create a color and interval editor tool which should be able to create text files that are compatible with G7:r.reclass, G7:r.colors, G7:v.colors and friends. |
| | 122 | * The existing GUI tools (`Raster -> Manage colors -> Manage color rules interactively` and its friends for vector and in 3D) are arguably cumbersome, not stable, ..., and should be improved. |
| | 123 | * Easy to use GMT color table format (CPT) importer would be a big advantage. There is already a r.cpt2grass converter for them available as an addon module, for example color tables from the [http://soliton.vm.bytemark.co.uk/pub/cpt-city/ cpt-city] repository. (see also QGIS's mirror of cpt-city; licenses would need to be vetted) |
| | 124 | * Integrate categorical and interval colors from ColorBrewer. |
| | 125 | * In the wx GUI: Instead of having the color rules stored in the file passed to G7:r.colors `rules` option, there could be a button from the color management menu which would bring user to the manager/editor, allowing true interactivity, color etc. then automatically launching G7:r.colors with the given rules. |
| | 126 | * It might also be advantageous to save the name of the color table after G7:r.colors somewhere in files for map, so that it can be reused/displayed later. (probably easiest to allow the colr/ files reading code to ignore #commented lines and put the name at the top of the colr/ file) |
| | 127 | * Language requirements: Python, wx-Widgets |
| | 128 | * Co-mentor: Hamish |
