| 11 | | This project builds upon the work initiated during the OSGeo sprint in Prague in the summer of 2023 which involved creating a new History Browser panel facilitating the access to command history. Starting December 8th, the new History Browser panel is already available in the GRASS development version (see Figure 1 and the PR https://github.com/OSGeo/grass/pull/3234). However, it offers only a simple single-level display of commands from the history log and the option for launching module dialogs pre-filled based on the command history. |
| | 11 | This project builds upon the work initiated during the OSGeo sprint in Prague in the summer of 2023 which involved creating a new History Browser panel facilitating the access to command history. Starting December 8th, the new History Browser panel is already available in the GRASS development version (see the PR https://github.com/OSGeo/grass/pull/3234). However, it offers only a simple single-level display of commands from the history log and the option for launching module dialogs pre-filled based on the command history. |
| | 12 | |
| | 13 | == Goal == |
| | 14 | |
| | 15 | The core part of the work will be devoted to expanding the basic functionality of the History Browser by providing the following enhancements: |
| | 16 | |
| | 17 | - Changing the plain text format of the history log (.wxgui_history) to JSON, allowing more information to be stored for each executed command, such as execution time, runtime duration, status code, region settings, if a mask was set, etc. |
| | 18 | |
| | 19 | - Creating a context menu with options for "Run Command" and "Show Info." "Show Info" will display a small dialog about the respective process stored in the JSON file. |
| | 20 | |
| | 21 | - Adding a symbol (green checkmark, yellow dot, or red cross) in front of each command in the tree based on the command's status value (completed, in progress, failed). |
| | 22 | |
| | 23 | - Branching the tree based on the date of command execution (commands from a specific day could be rolled up). |
| | 24 | |
| | 25 | - Filtering commands based on the status code (completed, in progress, failed) |
