| 593 | | ''This was a video call advertised on [https://lists.osgeo.org/pipermail/grass-dev/2020-August/094583.html user and dev mailing lists]. Notes by Vaclav Petras.'' |
| 594 | | |
| | 593 | ''This was a video call advertised on [https://lists.osgeo.org/pipermail/grass-dev/2020-August/094583.html user and dev mailing lists]. More than 10 users and developers joined (during the 2 hours). Notes by Vaclav Petras.'' |
| | 594 | |
| | 595 | * Outline: |
| | 596 | * Linda Kladivova presented the major changes in GUI individually. |
| | 597 | * LK presented a live demo for the non-beginner cases. |
| | 598 | * Availability of the updates (all already available in master branch). |
| | 599 | * General discussion (see notes below). |
| | 600 | * The new design was well received. |
| | 601 | * Concerns about speed and interaction/feedback during loading: |
| | 602 | * The data catalog takes time to load with really large mapsets (time series with thousands of maps). |
| | 603 | * Splash screen shows only for a short time not really covering most of the waiting period. (Probably not related to the data catalog itself, but more important now when no other window was shown.) |
| | 604 | * Documentation needed. |
| | 605 | * Video would be really useful also for promotion. |
| | 606 | * The official documentation, i.e. the related manual pages, needs to be updated (they are not outdated!), but this won't be the primary source of information. More a reference or overview. (We don't know who will read it.) |
| | 607 | * Embedded documentation would be best. (If interactive even better.) |
| | 608 | * Workspaces (called Projects in the future) are related, but whole another issue. |
| | 609 | * Some users would be probably fine with just one workspace/project file per mapset. |
| | 610 | * In-mapset workspace/project file would be useful for the demos. Can be read only without an explicit way of creating those in the GUI, i.e., it would be really meant for demos and advanced users. |
| | 611 | * The different situations during startup require notifications to inform user about what happen. |
| | 612 | * The not-yet-implemented fallback start for a returning user with unusable last used mapset requires a notification because the situation can be confusing as new location and/or mapset will be created in the middle of using GRASS GIS. |
| | 613 | * The start in the last used mapset, although generally agreed on, seems to be confusing or unexpected to some, so a message about "that's what happen and here is how you can change mapset" is needed. |
| | 614 | * An issue related to the startup, although not to the data catalog is presence of command line/terminal window. |
| | 615 | * Making terminal optional is now possible. (Interactive shell is not longer required by GRASS GIS). |
| | 616 | * An option from the GUI to start terminal is desired by some users. |
| | 617 | * A discussion on mailing will follow to discuss the options. |
