<html><body><div class="-wm-body -wm-apply-styles">
<div class="-wm-body -wm-apply-styles">
<div class="-wm-body -wm-apply-styles">
<p>
Hello guys,</p>
<p><br>
</p>
<p>after two weeks of working on the GRASS mini-project called <span style="font-weight:normal"><span style="font-size:16px">Easy command history navigation through the History browser panel</span></span>, I am sending my first progress
report which is also
available here: [1].</p>
<p><br></p><p>
<strong>1) What did I complete?</strong><br>
The first simple implementation of the history browser panel (see <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/3234"><span class="-wm-icon"></span></a>[2])
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 <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/3342"><span class="-wm-icon"></span></a>[3]
since in this PR the problematic structure was fully shown. At the
beginning of the second week, this PR adding a new pop/up command menu with an item for deleting a command from history was successfully merged. Big
thanks to Tomas Zigo for the suggestions and testing! <br></p><p><br></p>
<p>
In the middle of the second week, I started to prepare the biggest PR of this project [4]
which focuses on two things: first, it changes the way how the 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. <br></p><p><br></p>
<p>
<strong>2) What am I going to achieve for the next two weeks?</strong><br>
I will probably stick with <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/3365"><span class="-wm-icon"></span></a>[4] for the next two weeks. Firstly, the JSON format structure needs
revisions. Secondly, I will rework how the info shows up - the info will
be shown directly at the bottom of the history browser after calling
the OnItemSelected event. As this PR is the most important part of the
project, it will probably require a couple of iterations. <br></p><p><br></p>
<p>
<strong>3) Is there any blocking issue?</strong><br>
No, it isn't. <br></p><p><br>
</p><p>Have a nice week.</p><p><br></p>Linda<div><br>
</div>
<div>[1]<a href="https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/https:/trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation#Reportforweeks1and2" rel="noopener" class="-wm-moz-txt-link-freetext"> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation#Reportforweeks1and2<br></a></div>[2] <a href="https://github.com/OSGeo/grass/pull/3234"><span>https://github.com/OSGeo/grass/pull/3234</span></a></div><div class="-wm-body -wm-apply-styles">[3] <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/3342">https://github.com/OSGeo/grass/pull/3342</a></div><div class="-wm-body -wm-apply-styles">[4] <a class="-wm-ext-link" href="https://github.com/OSGeo/grass/pull/3365"><span class="-wm-icon"></span>https://github.com/OSGeo/grass/pull/3365</a></div><div class="-wm-body -wm-apply-styles"><br></div>
</div>
</div>
</body></html>