| | 216 | |
| | 217 | == Report for weeks 5 and 6 == |
| | 218 | |
| | 219 | '''1) What did I complete?'''\\ |
| | 220 | 1) What did I complete? |
| | 221 | I completed the PR https://github.com/OSGeo/grass/pull/3365 which enables storing more information about executed commands. Newly, commands are stored in JSON format and then displayed as the command info in the history pane. I also completed the relocation of the Export History button from the Console pane to the History pane (https://github.com/OSGeo/grass/pull/3402). |
| | 222 | |
| | 223 | Besides that, I am working on https://github.com/OSGeo/grass/pull/3421 and https://github.com/OSGeo/grass/pull/3622. The first PR creates a new button for setting the current region to the region used during the command execution. This PR is awaiting the final review. The second contribution adds time branching to the history browser tree and is currently waiting for the review. |
| | 224 | |
| | 225 | 2) What am I going to achieve for the next two weeks? |
| | 226 | I want to merge both https://github.com/OSGeo/grass/pull/3421 and https://github.com/OSGeo/grass/pull/3622. Subsequently, I plan to shift my focus toward visualization of command status. I plan to add icons in front of command nodes representing possible states (success, failed, in process, aborted). Regarding the status, it would also be nice to show the complete error text if a command fails. (Now there is “failed” written but no clue what happened). |
| | 227 | |
| | 228 | 3) Is there any blocking issue? |
| | 229 | No, it isn’t. I have been much more busy the last two months since on the 19th of February, my two-member family was expanded by one little guy, my son Vilem. So any work has gone kind of slowly over the last two months… |
