Il 14/04/2015 21:44, Régis Haubourg ha scritto:
Hmm, interesting idea.
By now, I could deal with it with profile QGIS2.ini fine tuning.
User settings also concerns all that is stored in .qgis profile (settings,
GUIncustomization, processing conf and use models).
What you suggest implies
We are not working on thia but I agree with you. A db project would help a
lot also for data concinstency, and this is a cross reference to the
topological tools post you wrote a few minutes ago: having a set of rules
stored within the DB. This would keep data coherent between users and
editing
Hi all,
we have already discussed this, and I'd like to raise the point.
In corporate environment, it would be crucial to store both user
settings and default projects in the database, so that an user could
start with a preset environment. This is an extension of our previous
work, storing styles
Hmm, interesting idea.
By now, I could deal with it with profile QGIS2.ini fine tuning.
User settings also concerns all that is stored in .qgis profile (settings,
GUIncustomization, processing conf and use models).
What you suggest implies that QGIS can authenticate itself and register to a
