393 | | * Add "set level" function to API to not load data |
394 | | * There needs to be a choice in context menu to load the data |
395 | | * Add "filter by item type" function to API to load or not load workspaces or show or nor show mapsets and locations |
396 | | * This needs to be specific for each subtree |
397 | | * Multiple buttons in the toolbar under the data catalog tree |
398 | | * Beginners can ignore |
399 | | * Show sample location to download in the data catalog |
400 | | * Challenge: Naming |
401 | | * Add multiple databases to data catalog |
402 | | * Button to add existing or new database |
| 398 | * Another toolbar on the side |
| 399 | * This will be the common functionality between all places where data catalog is used. |
| 400 | * Beginners can ignore this one in startup, but useful for advanced users. |
| 401 | * Load/show data button on the side |
| 402 | * Turned on by default in the Data tab |
| 403 | * Turned of by default and at every startup in the startup window. |
| 404 | * A choice in context menu to load the data for part of the tree |
| 405 | * Support multiple databases to data catalog |
| 406 | * Add button to add existing or new database |
414 | | * Collect recent mapsets (#3584), locations, databases (#572) |
415 | | * Certain number or just collect all ordered or with dates |
416 | | * Each level separately |
417 | | * Collect recent workspaces (#2604) |
418 | | * Certain number or just collect all ordered or with dates |
419 | | |
420 | | Data catalog changes which need "recent info" to be collected: |
421 | | |
422 | | * Filter in data catalog showing only recent (#3576) |
423 | | * Order in data catalog by time (most recent on top) |
424 | | * Also add button to filter alphabetically |
425 | | * All (previously saved) or recent workspaces shown in the startup window |
| 418 | * Collect "recent info" and "used info" |
| 419 | * Collect N=5 recent mapsets (#3584) |
| 420 | * Collect N=5 workspaces (#2604) |
| 421 | * Collect all used databases (#572) |
| 422 | * Collect all used workspaces |
| 423 | * Mapset and database recorded at the same time when GRASS GIS is started or switched to a mapset. |
| 424 | * Workspace is recorded when opened or saved. |
| 425 | * Check if the item is already in the list. |
| 426 | * For the recent, when saving, read all, see if it is in the list, if yes, remove and put at the beginning/end (there is a wxPython API for that) |
| 427 | * At least on the level of API, recent and general settings can be the same or connected (so they can be the same in the background). |
| 428 | |
| 429 | Data catalog changes which need "recent info" and "used info" to be collected: |
| 430 | |
| 431 | * Filter in data catalog showing only recent items (#3576) |
| 432 | * Show workspaces button |
| 433 | * All previously saved or opened |
| 434 | * Workspaces shown under corresponding mapset |
| 435 | * Requires to parse XML of each workspace file and extract the mapset (the parsing step may need to be done in parallel). |
| 436 | * Challenge: We need to emphasize somewhere that a workspace is "associated with a mapset", not "part of a mapset" since we are showing alongside the data which is stored in a mapset. |