Changes between Version 71 and Version 72 of wxGUIDevelopment/New_Startup

Timestamp:

07/15/20 20:44:58 (4 years ago)

Author:

wenzeslaus

Comment:

Notes from July meeting

wxGUIDevelopment/New_Startup

@@ -537 +537 @@
 === Next steps in GSoC and beyond video call, July 15, 2020 ===
 
-==== Agenda ====
-
-* State of GSoC 2020
- * Location wizard
- * Data catalog
+''Participants: Linda Kladivova, Anna Petrasova, Vaclav Petras, Moritz Lennert, Martin Landa, Helena Mitasova. Notes by VP.''
+
+* State of GSoC 2020 and next steps
+  * Automatic creation and improved detection of grassdata for first-time user
+  * Location wizard
+  * Data catalog
+    * Refresh and sync when things change in the GUI (e.g., from the Settings menu or File import).
+    * Test double click on maps from different location. (Should be disabled, but causes an error.)
+    * Add buttons to add new things:
+      * Create location, mapset in current location/database.
+      * Import into current mapset (also as a context menu item on mapset, see below).
+    * Add context menu items:
+      * Import into mapset (like in File)
+      * Export map (like in Layers)
+    * Search for mapsets (and locations?), not only maps.
+  * Tab order in GUI
+    * Redo the rest of the tabs and window title:
+      * Layer Manager -> (simply) GRASS GIS
+      * Layers -> Display(s)?
+      * Swap Modules and Console.
 * Data catalog
  * Read-only mapsets (locked, non-owned, r-x, ...?)
+   * Focus in GRASS "permissions", i.e., lock and "primary owner".
+   * Handle system permissions as errors (see e.g. `is_mapset_valid()` in `grass.py`).
  * Is allowed editing needed for renaming, deleting, and creating mapsets or locations?
+   * Yes. (VP: Have the options enabled to allow a click, but then ask to allow editing first if not allowed.)
  * Terminology of locked mapsets versus allowed editing of other mapsets (note the lock symbol in the toolbar icon)
  * Large databases
+   * Does not seem to be a huge issue as long as there is an indication of loading.
+   * Loading of only the current mapset or current location or other ways of dealing with large databases should be feature requests. 
  * Storing a list of databases (in settings, in workspace, not at all, track recent, track all ever used)
 * Startup
- * What location/mapset to use as a demo location for the first-time user?
- * What additional behavior is needed for the first-time user? 
- * Starting GUI in the last used mapset (`--text` starts in the last used mapset)?
- * Always start in some mapset (demo, last, temporary)?
+  * What location/mapset to use as a demo location for the first-time user?
+    * Yes, for sure, use the demolocation with a world map which is already present in the source code.
+  * What additional behavior is needed for the first-time user?
+    * Tell about need for a new mapset and import of data.
+  * Starting GUI in the last used mapset (`--text` starts in the last used mapset)?
+    * Yes, at least experimentally.
+  * Always start in some mapset (demo, last, temporary)?
+    * Start in the last used and use the demolocation as a fallback when locked or deleted. (Create demolocation if needed. Create new mapset there if needed and/or find first unlocked mapset.)
 * Workspaces
- * Rename to //projects//?
- * Workspace/project is GUI + db/location/mapset + current working directory + ...?
+  * Rename to //projects//?
+    * Yes, project or project file is used a lot in other software and the current workspaces share a lot of the same characteristics.
+  * Workspace/project is GUI + db/location/mapset + current working directory + ...?
+  * A challenge is to communicate to users what is stored, namely that data is not stored there.
+  * Track saved projects/workspaces, remove non-existing ones from the list.
+  * Do not mix projects/workspaces and data, but test the idea of showing them in a data catalog-like view.
+* Left for next time:
+  * History issues in terminal with switching mapset always/often.
+* Next steps for the whole community:
+  * Test and create issues with bugs and feature requests.
+  * Cover the different tasks leading to starting in a demolocation for the first-time user.
+  * Set up a week for testing by community and a feedback session (active mailing list period and a video call with presentation of the functionality).
 == See also ==