| 282 | | '''1) What did I complete this week?'''\\ |
| 283 | | '''2) What am I going to achieve for next week?'''\\ |
| 284 | | '''3) Is there any blocking issue?'''\\ |
| | 282 | '''1) What did I complete this week?'''\\ |
| | 283 | I focused on the GUI refactoring. In order to add MapDisplay to the notebook widget, we need to have it in the form of wx.Panel. I divided the work into several steps. |
| | 284 | |
| | 285 | - This week I changed the way of creating Map Display statusbar (which is now independent of the parent widget) - https://github.com/OSGeo/grass/pull/1646. However, this PR caused the bug related to workspaces (https://github.com/OSGeo/grass/issues/1657) which I corrected ASAP (by https://github.com/OSGeo/grass/pull/1665). |
| | 286 | |
| | 287 | - Meantime, I started more complex PR changing the way the Map Display is built (see https://github.com/OSGeo/grass/pull/1656). The core lies in adding the intermediate wx.Panel widget. This PR aims at more general refactoring of Map Display creation, do not change the code in the Single Layout parallel environment yet. |
| | 288 | |
| | 289 | '''2) What am I going to achieve for next week?'''\\ |
| | 290 | I would like to utilize GUI refactoring I made now to the Single-Window GUI environment. It will lead to a new Map Display notebook widget (composed of wx.Panel Map Displays) which will be used as the content pane. |
| | 291 | |
| | 292 | '''3) Is there any blocking issue?'''\\ |
| | 293 | No, it isn't. |
