| | 621 | |
| | 622 | |
| | 623 | == Week 10 == |
| | 624 | |
| | 625 | '''1) What did I complete this week?'''\\ |
| | 626 | First of all, I finished two PRs related to two modes "Allow edits outside of the current mapset" and "Restrict edits to the current mapset". The first PR deals with the implementation of these restrictions (see https://github.com/OSGeo/grass/issues/843, https://github.com/OSGeo/grass/pull/848). The motion is that when Allow editing mode is ON we are allowed to rename and delete outside of the current mapset, if OFF no edits are restricted to the current mapset. The second PR suggested the new symbol since previous one was very misleading (see https://github.com/OSGeo/grass/issues/844, https://github.com/OSGeo/grass/pull/870). |
| | 627 | Secondly, I implemented storing list of databases in settings (see https://github.com/OSGeo/grass/issues/842, https://github.com/OSGeo/grass/pull/858). |
| | 628 | Thirdly, I enabled the option of deleting multiple locations (see https://github.com/OSGeo/grass/issues/874, https://github.com/OSGeo/grass/pull/875). |
| | 629 | |
| | 630 | Currently, there are 3 other PRs that are in process: |
| | 631 | |
| | 632 | * Start in a demo/startup location (see https://github.com/OSGeo/grass/issues/862, https://github.com/OSGeo/grass/pull/868) |
| | 633 | |
| | 634 | This is almost done. However, there will be another PR opened that is gonna treat the initial state of GRASS more systematically. |
| | 635 | |
| | 636 | * Distinguish mapsets by ownership and lock in Data tab (see https://github.com/OSGeo/grass/issues/714, https://github.com/OSGeo/grass/pull/849) |
| | 637 | |
| | 638 | Almost done, just some smaller cosmetic changes. In this PR I also established the mapset key "current". Therefore, not only locked mapset and mapset owned by a different owner than current user, but also current mapset is distinguished by label. |
| | 639 | |
| | 640 | * Data Catalog: Double click on map from different locations fails - BUG (see https://github.com/OSGeo/grass/issues/884, https://github.com/OSGeo/grass/pull/886) |
| | 641 | |
| | 642 | The initial suggestion was to inform the user that the map is in the different location and ask if they want to switch to this mapset. However, there are probably more ways in the game on how to solve this issue (e.g. not allowing to display those maps at all?...) Should be discussed. |
| | 643 | |
| | 644 | '''2) What am I going to achieve for next week?'''\\ |
| | 645 | |
| | 646 | I am gonna end up those above-mentioned PRs. |
| | 647 | Then I will continue with checking for gislock and different ownership when performing operations with mapsets and locations. Furthermore, I gonna reflect changes, I made in Data Catalog, in GUI. |
| | 648 | |
| | 649 | - Check for gislock and other issues when deleting/renaming/editing mapset and location in catalog (https://github.com/OSGeo/grass/issues/801) |
| | 650 | - Reflect changes done from Data Catalog in GUI and vice versa (https://github.com/OSGeo/grass/issues/885) |
| | 651 | - when map is renamed in data catalog while it is displayed, the layer needs to be changed otherwise rendering fails |
| | 652 | - when map is moved elsewhere in data catalog while it is displayed |
| | 653 | - new map is created (this item needs to be expanded, there are multiple ways a new map is created) |
| | 654 | - current mapset/location is changed from menu |
| | 655 | - etc. |
| | 656 | |
| | 657 | |
| | 658 | |
| | 659 | '''3) Is there any blocking issue?'''\\ |
| | 660 | No. It is not. |
