search

landam / grass-gis-git-migration-test

0 stars 0 forks source link

GIS manager: allow dataset managing directly #86

Open landam opened 5 years ago

landam commented 5 years ago

Reported by timmie on 29 Mar 2013 15:13 UTC Allow from the GIS Manager to manage datasets directly: g.remove g.rename g.copy

Once these commands are available in the context menu, any changes (e.g. renaming) shall be reflected in the layer tree.

See also: http://trac.osgeo.org/grass/ticket/1909

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

landam commented 5 years ago

Modified by @landam on 29 Mar 2013 15:15 UTC

landam commented 5 years ago

Comment by wenzeslaus on 26 Mar 2014 18:56 UTC Please check with the recent GRASS 7 (trunk), there is "make copy in the current mapset" for maps outside current mapset. Also, the context menu is pretty long already, so adding 2-3 new items is not ideal. Do you have any other idea how to solve this? Some concrete GUI design would be nice. For example, there is an idea of separate GRASS Catalog for managing maps and projections, but this is far from being implemented and it might be overkill for your request.

landam commented 5 years ago

Comment by pvanbosgeo on 27 Mar 2014 16:35 UTC If I may add my opinion, I think adding these 2-3 items to the context menu would be a great addition. The easy of use this would offer would easily outweigh, i.m.h.o., the possible disadvantage of a longer context menu (I actually think it isn't that long in any case).

If the length of the context menu is really a problem, an alternative could maybe to have two or three buttons next to the layer name (now there is one, which offers the same context menu as when using right click). Using e.g., three buttons, one can have one for all options related to the visualization (opacity, zoom, rename, remove, etc), one for report options (profile, metadata, histogram) and one for file / data-set operations. Just my 2ct.

landam commented 5 years ago

Comment by wenzeslaus on 14 Feb 2015 22:23 UTC Please check also Data Catalog tab in available in trunk (7.1), it needs some feedback.

landam commented 5 years ago

Modified by @landam on 28 Mar 2016 18:03 UTC

landam commented 5 years ago

Comment by neteler on 5 May 2016 14:08 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 28 Dec 2016 15:04 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by @landam on 5 May 2017 20:40 UTC

landam commented 5 years ago

Comment by @landam on 1 Sep 2017 20:24 UTC

any changes (e.g. renaming) shall be reflected in the layer tree.

This issue is still valid.

1) add a map to layer tree

2) go to Data Catalog and rename

3) layer item in layer tree is invalid (map does not exists)

This should be fixed.

landam commented 5 years ago

Comment by @landam on 1 Sep 2017 20:28 UTC All enhancement tickets should be assigned to 7.4 milestone.

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:51 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