[QGIS-Developer] Plugin [1302] Flurstuecke und Gemarkungen Sachsen approval notification.

[noreply]

Plugin Flurstuecke und Gemarkungen Sachsen approval by pcav.
The plugin version "[1302] Flurstuecke und Gemarkungen Sachsen 0.1.1" is now 
approved
Link: http://plugins.qgis.org/plugins/SaxonyCadastralParcels/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Auxiliary data storage for labeling, UNDO/REDO - where does it belong to?

[Alexandre Neto]

If I may,

I would prefer to have one global undo/redo stack of buttons for all
project related tasks in QGIS main window (this should include labels,
styles, layers order, layer adding and so on). Even if that means that if
you go back too much, you risk removing some layers from the project, or
other more destructive actions. IMHO, having segmented undo/redo will also
create confusion among the users. Map composer, as a different window is
the exception, and should work separately.

Thanks for the work on auxiliary data storage, that will be great!!

Alexandre Neto

Régis Haubourg  escreveu no dia terça, 22/08/2017
às 14:47:

> Hi all,
>
> one major drawback of QGIS has long been that labeling was considered as
> part of the datasources, which can be true in some cases, but often it more
> belong to a project map object
>
> We, at Oslandia, working on adding Auxiliary storage capabilities to QGIS,
> which was discussed in several QEP [1] before.
>
> Now we are close to merge but the work but I would like to discuss some
> ergonomics and design polishing.
>
> In all GIS tool, custom labeling informations have been stored in project
> file, except in QGIS (which was a brilliant idea to keep it simple !).
>
> A user will now have two ways of storing labeling data :
>  - In the datasource by manually adding the fields and setting the
> corresponding labeling widget. Only advanced users, with grants on the
> datasource do that
> -  Using an auxiliary data source sqlite db stored inside the project,
> just directly using the labeling toolbar, even on readonly layers. 90 % of
> the users will use that I think.
>
> If we consider that a label modification (location, style, rotation ...)
> belongs to a project, then we save it when a user saves the project.
> If we consider it is belonging to the data, we save it with data save
> button.
> Rollback for data edits exists using the edit buffer.
> But Rolling back project modifications exists only partially, in
> composer's edit command list or in dynamic styling panel.
>
>
> Our concern is about how to handle and display the undo/redo actions for
> labeling when they are stored inside the project file.
>
>
> We thought about 4  ways before concluding that:
> - merge the labeling command in the source layer's edit buffer stack ->
> that won't work if the layer is readonly. If a user chose not to use the
> auxiliary data, then it will work like normal editing.
> - add separate buttons to save auxiliary data by hand (which is the same
> action as saving a project in fact). Tollbars are too cluttered and users
> are already confusing data and project save buttons.
> - Create a global "project" or maybe "mapcanvas" level stack, but I
> suspect users would like to be able to rollback style, composer and
> labeling independently, when undoing some labeling action could also remove
> some layers or important styling things.
> - Finally, we decided to add a separate edit buffer for the auxiliary data
> inside the dynamic styling panel, just below the style/label edit buffer.
>
> So  has anyone any strong opinion here?
>
> Is there any plan somewhere for a Project Undo/Redo, allowing for instance
> to Cancel a layer deletion ?
>
> If yes, please share your thoughts so that we store each undo/redo stack
> at the right place, and hopefully with something users will understand
> easily.
>
> All the best,
> Régis
>
>  [1] https://github.com/qgis/QGIS-Enhancement-Proposals/issues/27
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Auxiliary data storage for labeling, UNDO/REDO - where does it belong to?

[Régis Haubourg]

Hi all,

one major drawback of QGIS has long been that labeling was considered as
part of the datasources, which can be true in some cases, but often it more
belong to a project map object

We, at Oslandia, working on adding Auxiliary storage capabilities to QGIS,
which was discussed in several QEP [1] before.

Now we are close to merge but the work but I would like to discuss some
ergonomics and design polishing.

In all GIS tool, custom labeling informations have been stored in project
file, except in QGIS (which was a brilliant idea to keep it simple !).

A user will now have two ways of storing labeling data :
 - In the datasource by manually adding the fields and setting the
corresponding labeling widget. Only advanced users, with grants on the
datasource do that
-  Using an auxiliary data source sqlite db stored inside the project, just
directly using the labeling toolbar, even on readonly layers. 90 % of the
users will use that I think.

If we consider that a label modification (location, style, rotation ...)
belongs to a project, then we save it when a user saves the project.
If we consider it is belonging to the data, we save it with data save
button.
Rollback for data edits exists using the edit buffer.
But Rolling back project modifications exists only partially, in composer's
edit command list or in dynamic styling panel.


Our concern is about how to handle and display the undo/redo actions for
labeling when they are stored inside the project file.


We thought about 4  ways before concluding that:
- merge the labeling command in the source layer's edit buffer stack ->
that won't work if the layer is readonly. If a user chose not to use the
auxiliary data, then it will work like normal editing.
- add separate buttons to save auxiliary data by hand (which is the same
action as saving a project in fact). Tollbars are too cluttered and users
are already confusing data and project save buttons.
- Create a global "project" or maybe "mapcanvas" level stack, but I suspect
users would like to be able to rollback style, composer and labeling
independently, when undoing some labeling action could also remove some
layers or important styling things.
- Finally, we decided to add a separate edit buffer for the auxiliary data
inside the dynamic styling panel, just below the style/label edit buffer.

So  has anyone any strong opinion here?

Is there any plan somewhere for a Project Undo/Redo, allowing for instance
to Cancel a layer deletion ?

If yes, please share your thoughts so that we store each undo/redo stack at
the right place, and hopefully with something users will understand easily.

All the best,
Régis

 [1] https://github.com/qgis/QGIS-Enhancement-Proposals/issues/27
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1307] GPS Position Lag Correction QGIS Plugin approval notification.

[noreply]

Plugin GPS Position Lag Correction QGIS Plugin approval by pcav.
The plugin version "[1307] GPS Position Lag Correction QGIS Plugin 1.0" is now 
approved
Link: 
http://plugins.qgis.org/plugins/qgis-position-lag-correction-plugin-version-1_0_0/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Question on signed windows installers

[Neumann, Andreas]

Hi Jürgen, 

Thanks a lot for the explanations, your work and efforts around signing
and fixing the weeklies! 

Another step in order to make QGIS more professional. 

Andreas 

On 2017-08-22 10:41, Jürgen E. Fischer wrote:

> Hi Andreas,
> 
> On Tue, 22. Aug 2017 at 09:39:48 +0200, Neumann, Andreas wrote: 
> 
>> I noticed that the Windows all-in-one installers are now signed (Open
>> Source Geospatial Foundation). Is 2.18.12 the first signed version or
>> were the previous versions also signed?
> 
> Yes, it's the first one.
> 
>> In any case - wanted to report back that our AV scanner did not complain
>> about 2.18.12, whereas it "swallowed" the QGIS 3 weekly without even
>> visibly notifying (only in the log file one could see that QGIS 3 was
>> sent to quarantine and the original installer file removed). Perhaps
>> signing installers builds trust with AV software? Installing over
>> OSGEO4W installer is always fine.
> 
> The weeklies apparently weren't built for a while.  Did anyone else notice?
> 
> I added signing for the weekly yesterday.  Requires wine and in turn xvfb -
> because we need to produce an extra installer that installs an uninstaller, so
> we can sign it and include it in the actual installer - runs fine locally (but
> w/o xvfb), but currently the final step crashes with a bus error on qgis2...
> 
> Jürgen 
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [QGIS-Developer] Question on signed windows installers

[Jürgen E . Fischer]

Hi Andreas,

On Tue, 22. Aug 2017 at 09:39:48 +0200, Neumann, Andreas wrote:
> I noticed that the Windows all-in-one installers are now signed (Open
> Source Geospatial Foundation). Is 2.18.12 the first signed version or
> were the previous versions also signed? 

Yes, it's the first one.


> In any case - wanted to report back that our AV scanner did not complain
> about 2.18.12, whereas it "swallowed" the QGIS 3 weekly without even
> visibly notifying (only in the log file one could see that QGIS 3 was
> sent to quarantine and the original installer file removed). Perhaps
> signing installers builds trust with AV software? Installing over
> OSGEO4W installer is always fine. 

The weeklies apparently weren't built for a while.  Did anyone else notice?

I added signing for the weekly yesterday.  Requires wine and in turn xvfb -
because we need to produce an extra installer that installs an uninstaller, so
we can sign it and include it in the actual installer - runs fine locally (but
w/o xvfb), but currently the final step crashes with a bus error on qgis2...


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Norden http://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1300] QEPANET approval notification.

[noreply]

Plugin QEPANET approval by pcav.
The plugin version "[1300] QEPANET 0.91" is now approved
Link: http://plugins.qgis.org/plugins/qepanet/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Plugin [1267] AreaPrinter approval notification.

[noreply]

Plugin AreaPrinter approval by pcav.
The plugin version "[1267] AreaPrinter 0.5 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/AreaPrinter-master/
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

[QGIS-Developer] Question on signed windows installers

[Neumann, Andreas]

Hi Jürgen, 

I noticed that the Windows all-in-one installers are now signed (Open
Source Geospatial Foundation). Is 2.18.12 the first signed version or
were the previous versions also signed? 

In any case - wanted to report back that our AV scanner did not complain
about 2.18.12, whereas it "swallowed" the QGIS 3 weekly without even
visibly notifying (only in the log file one could see that QGIS 3 was
sent to quarantine and the original installer file removed). Perhaps
signing installers builds trust with AV software? Installing over
OSGEO4W installer is always fine. 

Greetings, 

Andreas___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer