Changes between Version 45 and Version 46 of GSoC/2021/SingleWindowLayout


Ignore:
Timestamp:
07/02/21 05:31:16 (3 years ago)
Author:
lindakladivova
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2021/SingleWindowLayout

    v45 v46  
    137137}}}
    138138{{{#!td
    139 '''Map Display notebook pane:'''
    140 - Define a Map Panel class
    141 - Integrate a Map Panel class to a new Map Display pane
    142 }}}
    143 {{{#!td
    144 
     139'''wxGUI refactoring:'''
     140 - Build all other Map Frames based wx.Statusbar (see https://github.com/OSGeo/grass/pull/1675)
     141 - Utilize Map Display panel into Map Display frame (see https://github.com/OSGeo/grass/pull/1675)
     142}}}
     143{{{#!td
     144\\
     145\\
     146\\
     147WIP
     148WIP
    145149}}}
    146150|-----------------------
     
    307311
    308312== Week 4 ==
     313'''1) What did I complete this week?'''\\
     314As the last week, I focused on the GUI refactoring. I worked on the main refactoring PR (see ​https://github.com/OSGeo/grass/pull/1675), in terms of the main Map Display I am done here. However, we realized that changes influence also other Map Frames based - particularly g.gui.rdigit, d.mon, Map Swipe, Ground Control Point and IClass frame.
     315
     316There were two ways to proceed. First, I started with the statusbars for all the frames that we need newly to be created based on wx.Statubar widget (see https://github.com/OSGeo/grass/pull/1689). Then we came up with another concept, namely delegating methods using metaprogramming. Although this path seemed cheap at first (we talked about it very intensively on videocall on Wednesday), after a few hours of studying, we came to the conclusion that it is inappropriate in our case. So that, I will again start to work on (see https://github.com/OSGeo/grass/pull/1689).
     317
     318Meantime, I also discovered the bug when hiding statusbar and toolbars does not work properly for map frames as e.g. Map Swipe (and other standlalone map frames) and I set up the issue for it (see https://github.com/OSGeo/grass/issues/1691).
     319
     320To sum it up, this week was not so productive in terms of code, but key in determining what to do next.
     321
     322'''2) What am I going to achieve for next week?'''\\
     323In the next step, the focus will be on the completion of https://github.com/OSGeo/grass/pull/1689, which will then allow the completion of the large ​https://github.com/OSGeo/grass/pull/1675.
     324
     325'''3) Is there any blocking issue?'''\\
     326No, it is not. However, as I have already mentioned I am on holiday till Tuesday. I am looking forward to new energy coming after the rest. :-)
     327
     328== Week 4 ==
    309329'''1) What did I complete this week?'''\\
    310330'''2) What am I going to achieve for next week?'''\\