[GRASS-git] [OSGeo/grass] 6a0fc7: GUI: in data catalog don't use restrictions, add p...

[Anna Petrasova]

  Branch: refs/heads/main
  Home:   https://github.com/OSGeo/grass
  Commit: 6a0fc7db8723d56cf600b906b28ee37242c273cc
      https://github.com/OSGeo/grass/commit/6a0fc7db8723d56cf600b906b28ee37242c273cc
  Author: Anna Petrasova <kratochanna at gmail.com>
  Date:   2025-10-06 (Mon, 06 Oct 2025)

  Changed paths:
    A gui/icons/grass/location-create.png
    A gui/icons/grass/location-create.svg
    M gui/wxpython/datacatalog/catalog.py
    M gui/wxpython/datacatalog/toolbars.py
    M gui/wxpython/datacatalog/tree.py
    M python/grass/grassdb/checks.py

  Log Message:
  -----------
  GUI: in data catalog don't use restrictions, add project instead of database (#6405)

remove restrictions that prevented users from editing outside of current mapset. Base on experience, this restriction is unexpected especially for new users. I removed the option to change it completely, the internal code I kept as is, just turned off the restriction.
I removed adding database path and instead added an option to add existing project. This is consistent with the way we are trying to de-emphasize GRASS database. I had interactions in the past where students were trying to add a project, but added it as database so it didn't work. Now the newly implemented adding of project tries to be more clever, thanks to the existing functionality in the library it's easier to test whether the project is valid and if not it tries to test whether the directory above or below is a project and reports useful message if not. I also changed location to project in those messages. One side effect is that when you add a project, the database is added and reloaded so all projects in that path are automatically added as well.



To unsubscribe from these emails, change your notification settings at https://github.com/OSGeo/grass/settings/notifications