landam / grass-gis-git-migration-test

0 stars 0 forks source link

GUI improvments for long list of mapsets or long mapset names (Location / Mapset selection) #190

Open landam opened 5 years ago

landam commented 5 years ago

Reported by sbl on 5 Feb 2016 22:08 UTC In order to be able handle a long list of mapsets or long mapset names better in the GUI startup (location / mapset selection) two enhancements might be useful:

1) For long lists of mapsets in shared GRASS GIS DBs it would be nice if one could filter the list of mapsets to "mapsets owned by me" (e.g. using a tickbox), as these are the only ones the user technically can use for working anyway...

2) If one has long mapset names it would be an advantage if the user was able to change the distribution of horizontal space used for the "mapset box" and the "locations box", meaning, that the user can make the mapset box wider if the location contains mapsets with longer names...

Migrated-From: https://trac.osgeo.org/grass/ticket/2898

landam commented 5 years ago

Comment by annakrat on 14 Feb 2016 00:06 UTC Replying to [ticket:2898 sbl]:

In order to be able handle a long list of mapsets or long mapset names better in the GUI startup (location / mapset selection) two enhancements might be useful:

2) If one has long mapset names it would be an advantage if the user was able to change the distribution of horizontal space used for the "mapset box" and the "locations box", meaning, that the user can make the mapset box wider if the location contains mapsets with longer names...

You can already stretch the window horizontally and the boxes stretch as well. This behavior seems good enough for me.

landam commented 5 years ago

Comment by sbl on 15 Feb 2016 08:24 UTC

You can already stretch the window horizontally and the boxes stretch as well. This behavior seems good enough for me.

Yes, this seems to be no issue on a high resolution screen. On a low resolution screen (remote desktop window (VNC)) it was impossible to distinguish the mapsets with relatively long names / prefixes. I understand that this is probably too much of an edge case and with a high bandwidth I can likly get around this by requesting a connection with a higher resolution. So, sorry for not double checking on a local installation...

As for the filtering part: The inaccessible mapsets are already greyed out. Those where I am not the owner cannot even be selected. In locations with many mapsets (from different users) it would make the mapset selection more convenient (and probably lead to less confusion among less experienced users) if esp. the mapsets from other users, could be filtered from the list...

landam commented 5 years ago

Modified by @landam on 12 May 2016 06:37 UTC

landam commented 5 years ago

Modified by @landam on 25 Aug 2016 15:51 UTC

landam commented 5 years ago

Comment by @landam on 27 Aug 2016 13:42 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Comment by @landam on 25 Sep 2018 16:52 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed