| | 156 | === Anna and Vaclav, June 18 === |
| | 157 | |
| | 158 | Discussion about ''Proposal 2 (Gcmillar): Quick access through well-designed tabs on the side.'' |
| | 159 | |
| | 160 | * The good parts: |
| | 161 | * Recent items |
| | 162 | * Quick access to a lot of options |
| | 163 | * Visually appealing |
| | 164 | * Efficient and simple design with places for additional information and metadata |
| | 165 | * It is a significantly redesigned GUI aiming at both new and current users |
| | 166 | * Splash Screen: |
| | 167 | * Does not seem useful enough by itself even with additional info. |
| | 168 | * Merge with Recent. |
| | 169 | * May not serve well as true splash screen since it may not be possible to load it fast enough. |
| | 170 | * New Tab: |
| | 171 | * A lot of depends on template vs sample dataset controversy. |
| | 172 | * First row seems overloaded: loc wizard/new location button, templates/sample datasets, shortcuts from loc wizard. |
| | 173 | * Second row seems empty: Only 3 options and the last one is just a placeholder. |
| | 174 | * New workspace button: This is basically the current state, i.e. start an empty GUI. Is this how people think about it? Do we want to promote this way? |
| | 175 | * It seems completely counterintuitive for current advanced users, but might be fitting to new users. |
| | 176 | * Making Workspace part of the hierarchy (and e.g. putting it to the Data tab tree) is problematic because db/loc/mapset are here to separate data while the workspace, although often showing subset of what is in the mapset, puts the data together rather then separates them (even from diff mapsets). |
| | 177 | * New mapset button: This will be also possible from the Open tab because that's where the advanced users are likely to go. It may be available also from the Recent tab. |
| | 178 | * New location is actually a new empty/blank location, the others are from the template, so if two words, then "Empty location". |
| | 179 | * New two rows suggestion: |
| | 180 | * First row - Empty location: Using EPSG, XY, WGS84, ..., More |
| | 181 | * Items from the first page of loc wizard plus few often used ones (either by everybody like WGS84 or by the user (which requires to store e.g. recently used EPSGs)), i.e. "quick access", with More button going to loc wizard. |
| | 182 | * Second row - From template/With data: Sample NC SPM dataset, LL World Template, ..., More |
| | 183 | * Sample datasets and templates (whatever the distinction is or is not, it is arguable that template without data is more the "quick access" button from above) with More button going just to a full list (of whatever was installed as template to the operating system or is available online). |
| | 184 | * Possibly change oder. |
| | 185 | * Problems: |
| | 186 | * No place for New Mapset which seems quite fitting (and New Workspace if we go with it) |
| | 187 | * Empty location part contains the "quick access" items taken from loc wizard but these include "From existing data" which possibly import existing data. |
| | 188 | * Recent tab: |
| | 189 | * Merged with the Welcome/Splash Screen (just different content for new and returning users, but same default tab) |
| | 190 | * Details if present at all should be part of the item in the selection, otherwise it is not quick enough. |
| | 191 | * Workspaces will need a full paths. Mapsets locatons. |
| | 192 | * Locations here need to be reconsidered. It seems inappropriate here (similarly to database dir) because mapset needs to be created in it first. Even if we consider Workspace subitem of Mapset, an empty workspace is created without a name (file name is selected later), but Mapset always requires name to be created (similarly location would require CRS/loc wizard). On the other hand, new mapset from recent location is exactly what students need when following assignments in a course which is using one location (or couple of locations). |
| | 193 | * These can be in further tabs to show more (items and kinds of items), but that 1) makes it more nested 2) potentially breaks the one click advantage (but we also could remember the last tab user used) |
| | 194 | * Open tab: |
| | 195 | * Why not to have multiple databases in the first level of the tree (see e.g. #3576)? |
| | 196 | * Should the maps by part of the tree or of the info part? |
| | 197 | * It could show locked mapsets on Linux/Unix by using a different icon. |
| | 198 | * Last used one could be preselected as it is now. Additionally all recent items could use different icon. |
| | 199 | * With the functionality of data tab/data catalog (adding new locs or mapsets), renaming, it would be similar to the current page which is great for advanced users, but it may interfere with simplicity and it may create confusion (more than one way how to do a certain thing, it is tab open, but it is actually doing management, maybe there should be only the non-destructive actions, so new and maybe rename, but no remove). |
| | 200 | * Might the go-to tab for advanced users, should we make it possible to show it as the default one? |
