| 542 | | * Automatic creation and improved detection of grassdata for first-time user |
| 543 | | * Location wizard |
| 544 | | * Data catalog |
| 545 | | * Refresh and sync when things change in the GUI (e.g., from the Settings menu or File import). |
| 546 | | * Test double click on maps from different location. (Should be disabled, but causes an error.) |
| 547 | | * Add buttons to add new things: |
| 548 | | * Create location, mapset in current location/database. |
| 549 | | * Import into current mapset (also as a context menu item on mapset, see below). |
| 550 | | * Add context menu items: |
| 551 | | * Import into mapset (like in File) |
| 552 | | * Export map (like in Layers) |
| 553 | | * Search for mapsets (and locations?), not only maps. |
| 554 | | * Tab order in GUI |
| 555 | | * Redo the rest of the tabs and window title: |
| 556 | | * Layer Manager -> (simply) GRASS GIS |
| 557 | | * Layers -> Display(s)? |
| 558 | | * Swap Modules and Console. |
| | 541 | * Automatic creation and improved detection of grassdata for first-time user |
| | 542 | * Location wizard |
| | 543 | * Data catalog |
| | 544 | * Refresh and sync when things change in the GUI (e.g., from the Settings menu or File import). |
| | 545 | * Test double click on maps from a different location. (Should be disabled, but causes an error.) |
| | 546 | * Add buttons to add new things: |
| | 547 | * Create location, mapset in current location/database. |
| | 548 | * Import into current mapset (also as a context menu item on mapset, see below). |
| | 549 | * Add context menu items: |
| | 550 | * Import into mapset (like in File) |
| | 551 | * Export map (like in Layers) |
| | 552 | * Search for mapsets (and locations?), not only maps. |
| | 553 | * Tab order in GUI |
| | 554 | * Redo the rest of the tabs and window title: |
| | 555 | * Layer Manager -> (simply) GRASS GIS |
| | 556 | * Layers -> Display(s)? |
| | 557 | * Swap Modules and Console. |
| 560 | | * Read-only mapsets (locked, non-owned, r-x, ...?) |
| 561 | | * Focus in GRASS "permissions", i.e., lock and "primary owner". |
| 562 | | * Handle system permissions as errors (see e.g. `is_mapset_valid()` in `grass.py`). |
| 563 | | * Is allowed editing needed for renaming, deleting, and creating mapsets or locations? |
| 564 | | * Yes. (VP: Have the options enabled to allow a click, but then ask to allow editing first if not allowed.) |
| 565 | | * Terminology of locked mapsets versus allowed editing of other mapsets (note the lock symbol in the toolbar icon) |
| 566 | | * Large databases |
| 567 | | * Does not seem to be a huge issue as long as there is an indication of loading. |
| 568 | | * Loading of only the current mapset or current location or other ways of dealing with large databases should be feature requests. |
| 569 | | * Storing a list of databases (in settings, in workspace, not at all, track recent, track all ever used) |
| | 559 | * Read-only mapsets (locked, non-owned, r-x, ...?) |
| | 560 | * Focus in GRASS "permissions", i.e., lock and "primary owner". |
| | 561 | * Handle system permissions as errors (see e.g. `is_mapset_valid()` in `grass.py`). |
| | 562 | * Is allowed editing needed for renaming, deleting, and creating mapsets or locations? |
| | 563 | * Yes. (VP: Have the options enabled to allow a click, but then ask to allow editing first if not allowed.) |
| | 564 | * Terminology of locked mapsets versus allowed editing of other mapsets (note the lock symbol in the toolbar icon) |
| | 565 | * Large databases |
| | 566 | * Does not seem to be a huge issue as long as there is an indication of loading. |
| | 567 | * Loading of only the current mapset or current location or other ways of dealing with large databases should be feature requests. |
| | 568 | * Storing a list of databases (in settings, in workspace, not at all, track recent, track all ever used) |
| 571 | | * What location/mapset to use as a demo location for the first-time user? |
| 572 | | * Yes, for sure, use the demolocation with a world map which is already present in the source code. |
| 573 | | * What additional behavior is needed for the first-time user? |
| 574 | | * Tell about need for a new mapset and import of data. |
| 575 | | * Starting GUI in the last used mapset (`--text` starts in the last used mapset)? |
| 576 | | * Yes, at least experimentally. |
| 577 | | * Always start in some mapset (demo, last, temporary)? |
| 578 | | * 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.) |
| | 570 | * What location/mapset to use as a demo location for the first-time user? |
| | 571 | * Yes, for sure, use the demolocation with a world map which is already present in the source code. |
| | 572 | * What additional behavior is needed for the first-time user? |
| | 573 | * Tell about the need for a new mapset and import of data. |
| | 574 | * Starting GUI in the last used mapset (`--text` starts in the last used mapset)? |
| | 575 | * Yes, at least experimentally. |
| | 576 | * Always start in some mapset (demo, last, temporary)? |
| | 577 | * Start in the last used and use the demolocation as a fallback when locked or deleted. (Create demolocation if needed. Create a new mapset there if needed and/or find the first unlocked mapset.) |
| 580 | | * Rename to //projects//? |
| 581 | | * Yes, project or project file is used a lot in other software and the current workspaces share a lot of the same characteristics. |
| 582 | | * Workspace/project is GUI + db/location/mapset + current working directory + ...? |
| 583 | | * A challenge is to communicate to users what is stored, namely that data is not stored there. |
| 584 | | * Track saved projects/workspaces, remove non-existing ones from the list. |
| 585 | | * Do not mix projects/workspaces and data, but test the idea of showing them in a data catalog-like view. |
| | 579 | * Rename to //projects//? |
| | 580 | * Yes, project or project file is used a lot in other software and the current workspaces share a lot of the same characteristics. |
| | 581 | * Workspace/project is GUI + db/location/mapset + current working directory + ...? |
| | 582 | * A challenge is to communicate to users what is stored, namely that data is not stored there. |
| | 583 | * Track saved projects/workspaces, remove non-existing ones from the list. |
| | 584 | * Do not mix projects/workspaces and data, but test the idea of showing them in a data catalog-like view. |
