Changes between Version 7 and Version 8 of wxGUIDevelopment/EasyCommandHistoryNavigation

Timestamp:

01/23/24 01:13:19 (13 months ago)

Author:

lindakladivova

Comment:

--

wxGUIDevelopment/EasyCommandHistoryNavigation

@@ -168 +168 @@
 The first simple implementation of the history browser panel (peek at https://github.com/OSGeo/grass/pull/3234) had some flaws, mainly in terms of class hierarchy, so a bigger intervention was needed. So, week one was all about making the code neater and more logical. I dived into improving the code quality and logic as part of the PR https://github.com/OSGeo/grass/pull/3342 since in this PR the problematic structure was fully shown. At the beginning of the second week, this PR was successfully merged. Big thanks to Tomas Zigo for the suggestions and testing!
 
-In the middle of the second week, I started to prepare the biggest PR of this project https://github.com/OSGeo/grass/pull/3365 which focuses on two things: first, it changes the way how the new history log is stored - newly it is going to be the JSON format. Second, it shows the info about commands - execution time, runtime duration, status, region settings, and if a mask was set. We originally planned to show this info in a new Command Info dialog, but during the implementations, we decided that it would be cooler to have it right at the bottom of the history browser.
+In the middle of the second week, I started to prepare the biggest PR of this project https://github.com/OSGeo/grass/pull/3365 which focuses on two things: first, it changes the way how the new history log is stored - newly it is going to be the JSON format. Second, it shows the info about commands - execution time, runtime duration, status, region settings, and if a mask was set. We originally planned to show this info in a new Command Info dialog (see Figure 1), but during the implementations, we decided that it would be cooler to have it right at the bottom of the history browser.
 
 '''2) What am I going to achieve for the next two weeks?'''\\