[Qgis-developer] Plugin [592] LOUIS Map Biographer approval notification.

[noreply]

Plugin LOUIS Map Biographer approval by pcav.
The plugin version "[592] LOUIS Map Biographer 1.3.3" is now approved
Link: http://plugins.qgis.org/plugins/mapBiographer/
___
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] Are there plans to create a unique "Add layer" tool?

[Stéphane Henriod]

Hi Anita

To go one step further :-) Any reason why it couldn't be polished and
directly integrated in the core? As a non-developer, I maybe underestimate
the workload here? Isn't it something that could "easily" be done by one of
the core developers without requiring substantial additional funding?

I think such unified button would be very helpful, especially for beginners
(who don't intuitively understand yet the difference between vector,
raster, etc.) and I would hate to start a GIS introduction by saying
"First, you'll have to download and install a plugin" :-)

It also would be a good way to catch former ArcGIS users, who grew up used
to such a unified approach.

All the best

Stéphane


Le lundi 3 avril 2017, Anita Graser  a écrit :

>
>
> On Mon, Apr 3, 2017 at 10:50 AM, DelazJ  > wrote:
>
>> Hi,
>> Thanks Anita for this work. I wasn't aware of your tool. Any reason to
>> not make it available in the Plugins repo? It might get more audience,
>> unless I overestimate our repo... Btw: I like the title of the blog post.
>> :-)
>>
>
> ​Thanks Harrissou! No good reason why it's not in the rep really. Mostly,
> because it's just 10 lines of code added to a plugin tempalte and requires
> manual GUI customization to remove all the redundant add layer icons.
>
> I'll put it on Github and publish it.
>
> Best wishes,
> Anita
>
>
>
> ​
>


-- 

“When you travel, remember that a foreign country is not designed to make
you comfortable. It is designed to make its own people comfortable." --
Clifton Fadiman
___
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] A couple of ideas for QGIS

[roy roy]

Dear QGIS Developers,

I think QGIS would benefit adding the following features;
if you find them interesting they may be added to QGIS 3.0:

1 - Better support for Spatialite tables:

it is now impossible to remove columns from a spatialite
table, i know it's not supported by SQLite but there is a
simple work around that consists in creating a new table
without the removed column/s

2 - Save project data into SQLite/Spatialite db:

this would grant users the choice to save all the work
in one unique file ( data, layer style ), very handy for
backups and sharing/shipping

i'm not a c++ developer but i can help with docs
and testing.
best regards,

Roy.


___
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] [Qgis-psc] bug tracker cleanup

[Borys Jurgiel]

Dnia poniedziałek, 3 kwietnia 2017 17:33:53 Paolo Cavallini pisze:
> once closed, nobody will see them. It is a reality that long standing
> issues are sometimes picked up by someone and fixed, even after years.
> To me closing a valid issue just because nobody is working on it is like
> hiding the dust under the carpet.
> IMHO thickets should be closed on their merit, i.e. if they are not
> valid, or not reproducible.

+1
There are some old enhancement tickets I still keep in mind. As long as they 
are there, not everything is lost :)

Best regards,
Borys 
___
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] Processing algorithms slower when using filters on vector layers

[G. Allegri]

I've noticed that when a (OGR) layer has a filter expression applied on it,
processing algorithms perform worse.
I have tested several polygon layers with some thousands of features. If I
do, e.g., an intersection, it takes a lot more if I apply a filter that
reduces the number of features to some dozens, then without filtering.

I guess it can be caused by the extra work that the feature irerator has to
do with the filter (request with expression) but it's an unexpected
behaviour, at least for many of my courses partecipants.

Tested on QGIS 2.14.10 and 2.18.4.

giovanni
___
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] [Qgis-psc] bug tracker cleanup

[Anita Graser]

On Mon, Apr 3, 2017 at 7:33 PM, Paolo Cavallini 
wrote:

> Hi Giovanni,
>
> Il 03/04/2017 15:08, Giovanni Manghi ha scritto:
>
> > see my previous email. If no one cares (not even the users), why keep
> > them open? they can serve well as reference even closed, and if they
> > are really important bugs they will be naturally reopened.
>
> once closed, nobody will see them. It is a reality that long standing
> issues are sometimes picked up by someone and fixed, even after years.
> To me closing a valid issue just because nobody is working on it is like
> hiding the dust under the carpet.
> IMHO thickets should be closed on their merit, i.e. if they are not
> valid, or not reproducible.
>

​+1 Just because no user has added to an existing ticket for a while does
not mean that nobody cares or encounters it. It just means that they had
nothing new to add.

Best wishes,
Anita​
___
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] Plans for Processing algorithms documentation

[DelazJ]

Uhmmm, considering the different teasers I read about grant proposals, this
serie looks promising... and certainly selection hard to do, for voters...
Nice.
I stay tuned, then.

Thanks Matteo.

Le lundi 3 avril 2017, matteo  a écrit :
> Hi Harrissou,
>
> a grant proposal has been made to enhance this lack of Processing
> Documentation.
>
> Stay tuned ;)
>
> Matteo
> ___
> 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] [Qgis-psc] bug tracker cleanup

[Paolo Cavallini]

Hi Giovanni,

Il 03/04/2017 15:08, Giovanni Manghi ha scritto:

> see my previous email. If no one cares (not even the users), why keep
> them open? they can serve well as reference even closed, and if they
> are really important bugs they will be naturally reopened.

once closed, nobody will see them. It is a reality that long standing
issues are sometimes picked up by someone and fixed, even after years.
To me closing a valid issue just because nobody is working on it is like
hiding the dust under the carpet.
IMHO thickets should be closed on their merit, i.e. if they are not
valid, or not reproducible.
All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
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 [1212] Brasil IDF approval notification.

[noreply]

Plugin Brasil IDF approval by pcav.
The plugin version "[1212] Brasil IDF 0.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/Brasil-IDF/
___
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] Plans for Processing algorithms documentation

[matteo]

Hi Harrissou,

a grant proposal has been made to enhance this lack of Processing
Documentation.

Stay tuned ;)

Matteo
___
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] Plans for Processing algorithms documentation

[Paolo Cavallini]

Il 03/04/2017 16:23, DelazJ ha scritto:

> So, if some of you have any idea/plan on what processing algorithms
> documentation is supposed to evolve to, please share your knowledge...

agreed, this it a point of great importance, one of most common
complaints about QGIS. I'd be in favour of supporting this effort.
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
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 [1066] Isogeo approval notification.

[noreply]

Plugin Isogeo approval by pcav.
The plugin version "[1066] Isogeo 1.5.0-beta3 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/isogeo_search_engine/
___
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 [713] Indicatrix mapper approval notification.

[noreply]

Plugin Indicatrix mapper approval by pcav.
The plugin version "[713] Indicatrix mapper 1.3" is now approved
Link: http://plugins.qgis.org/plugins/tiss/
___
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] Are there plans to create a unique "Add layer" tool?

[Anita Graser]

On Mon, Apr 3, 2017 at 10:50 AM, DelazJ  wrote:

> Hi,
> Thanks Anita for this work. I wasn't aware of your tool. Any reason to not
> make it available in the Plugins repo? It might get more audience, unless I
> overestimate our repo... Btw: I like the title of the blog post. :-)
>

​Thanks Harrissou! No good reason why it's not in the rep really. Mostly,
because it's just 10 lines of code added to a plugin tempalte and requires
manual GUI customization to remove all the redundant add layer icons.

I'll put it on Github and publish it.

Best wishes,
Anita



​
___
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] Plans for Processing algorithms documentation

[DelazJ]

 Hi Devs,
(me looking again for plans...)

Currently, if you are looking for help for a Processing Tool, most of of
the tools will only display their description in QGIS application except if
they are from GRASS, GDAL/OGR (or any other provider I do not check).
Native QGIS tools show only their description, when it's filled, and this
is done only in english (see http://osgeo-org.1560.x6.
nabble.com/Are-Processing-algorithms-helps-not-translatable-td5309621.html).
The way to have a more complete decription (tool and parameters) is to look
into the Processing algorithms chapter (http://docs.qgis.org/2.14/en/
docs/user_manual/processing_algs/index.html) in User manual. But given that
this is a handmade update, it's far from completion, not all the tools are
available (focusing only QGIS native tools) and not all the parameters are
filled.

So, given QEP51 (https://github.com/qgis/QGIS-Enhancement-Proposals/issues/5
1) and https://github.com/qgis/qgis3.0_api/issues/62 which made some great
improvements on linking user manual and application context help, are there
some improvements planned on processing? What I'd need to know is:
- whether algorithms documentation will be done in application repo or doc
repo?
- What would algorithms documentation look like? i.e do we keep the same
structure/template?
- what's the status of the external resources (I'm not sure they are kept
updated) as discussed in the qep? Do we keep their help file in
application? in doc repo? (seems there's a mix currently)

Why these questions?:
- Doc repo is full of Processing tagged issues (
https://github.com/qgis/QGIS-Documentation/issues?utf8=%E2%
9C%93=is%3Aissue%20is%3Aopen%20processing - not exhaustive) and we need
to know what are the plans to avoid wasting our energy
- From QGIS2.16 we have moved many C++ Core plugins (fTools, GdalTools,
Heatmap, geometry snapper, interpolation...) to Processing so description
of these plugins (http://docs.qgis.org/2.14/en/
docs/user_manual/plugins/plugins_index.html) must somehow be removed from
the plugins chapter in user manual (a pending PR at
https://github.com/qgis/QGIS-Documentation/pull/1806 which actually made me
write this message) and reorganized in processing section. Some plugins
were briefly described while others were really detailed:
  *  What are the information to keep for Processing?
  *  In which form, given that the way their description is written doesn't
match processing algorithms doc template?
- last but not least, I recently read a thread  in which someone was
looking for ways to help documenting algorithms (very precise offer but why
not, any help is welcome!!) and I fail to find a proper answer to give him
other than his help is welcome.

So, if some of you have any idea/plan on what processing algorithms
documentation is supposed to evolve to, please share your knowledge...

Regards,
Harrissou
___
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] [Qgis-psc] bug tracker cleanup

[Giovanni Manghi]

Hi Tim,


> Do you mean like a monthly effort to dedicate some funds for bug fixing? I'd 
> certainly like to see us heading that way, and even better where QGIS.org 
> hires full time bug fixers / developers to work only for the good of the 
> general project and not to serve a specific client. Andreas can speak better 
> to the ability to do anything right now - but I suspect we might need to wait 
> till next year if we want to budget for more substantial (e.g. monthly) paid 
> bug fixing rounds.

regressions in 2.18 (since 2.14) are piling up. I'm sure that working
3/4 days on testing tracker triage in Essen I will find more.

cheers!

-- G --
___
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] [Qgis-psc] bug tracker cleanup

[Giovanni Manghi]

Hi Matthias,

> Do we have a plan for the signup process for redmine?
> I think the decision to stick to redmine was made under the assumption
> that one no longer needs to obtain a shared secret during this process.


hopefully we can get rid of the mantra thing


> What about all that have been in "feedback" state for more than 1 year?
> That should filter out issues like 167.

I already use the "feedback" label to close tickets that do not
receive an update in more than 15 days. As any others my time is
scarce, so those 15 days frequently become weeks, and my focus is on
high priority tickets and regressions because the "normal" bug queue
is too large to be able to be managed only in spare time (this is the
main reason to close all the tickets that didn't received *any*
attention in years).

-- G --
___
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] [Qgis-psc] bug tracker cleanup

[Giovanni Manghi]

> Il 27/03/2017 12:02, Giovanni Manghi ha scritto:
>
>> this thread didn't get the traction I was hooping for, is this a
>> indication that is a general opinion that all the fixing effort should
>> be focused on qgis3 and not also on the next LTR?
>
> agreed, I'm also surprised (the list seems less reactive on several
> subjects lately), and thanks for your perseverance in tracking this
> important issue.


...
...
...



> bad stuff indeed. so the above does not hit Q3, right?
> a bit of a pity investing on a dead branch rather than on main trunk,
> but I think it is a necessity, now that we want 2.18 as LTR.



since this email two more important regressions (in 2.18 since 2.14)
have been found and reported:

* "hidden" widget is broken
* maptips with expression to show local images is broken





> it makes sense, but in spipte of our efforts, many plugins still rely on
> this, and I do not think it's a good move just to shut them down


"just" shut them down no, we can send a mail and say that they will be
shut down. Moving is something that many have already done (for
instance I was forced because someone had deleted a repo of mine on
Redmine, but I dind't made any fuss about it). Making the
platform/redmine update/upgrade and leaving the mess that there is now
it would be really a pity.




> not sure about this: if they still make sense, I'd prefer to keep them.
> e.g. the second oldest is still valid, and helps us remembering about a
> real issue:
> http://hub.qgis.org/issues/167
> I understand keeping the list short is a major advantage, but removing
> issues like this is not an advantage for the project IMHO.


see my previous email. If no one cares (not even the users), why keep
them open? they can serve well as reference even closed, and if they
are really important bugs they will be naturally reopened.

One way or the other a decision must be taken.



-- G --
___
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] [Qgis-psc] bug tracker cleanup

[Giovanni Manghi]

Hi Richard!


> Hi G,
>
> thanks for this update and your work in this!
>
> in Bonn, I assisted Juergen when we tried to handle a backup of the old
> db to read into a new Hetzner server (we actually already have one since
> then...). Point at that moment was that we were waiting for people to
> cleanup the wiki and plugin pages


As we have to(?) stick with Redmine (rather then moving to github) and
try update/upgrade
the platform I strongly believe that we should do a deep cleanup of
our Redmine instance *before* upgrading. This would include close all
subprojects (asking kindly to plugin authors to move on to github, as
many have already done)

and -in my opinion-

all the tickets (at least the bug ones) that are years that are
untouched/not updated: I really can't see any advantage in keeping
open tickets that is clear now that no one will ever look at, and no
one (even the users) seems to be bothered by. If some of them is
really important this will naturally be reopened. If they are not they
can serve as reference, but closed, eventually with a specific text
stating the reason why it was closed.




> I think (Juergen?) that we actually were confident enough that with some
> hours of work (and Juergens Perl-magic) we were able to move the old db
> to a new RedMine instance.
>
> I cannot do this alone, but if Juergen is in Essen and free for half a
> day I think we should bite the bullet.


sounds like a plan? not sure if I can help with the above process, but
I could certainly with the cleaning before the update/upgrade.

looking for some consensus here, hopefully before Essen.

thanks

-- G --
___
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] QGIS API Distance, Azimuth/Bearing - API Documentation

[C Hamilton]

I had been wondering what algorithm is being used for the methods azimuth,
distance, and  project in the QgsPoint class, but in looking at the code it
is simply cartesian plane math. It looks like the qgsdistancearea class is
using vincinty math if I am examining the code correctly.

Vincinty is more accurate than the great circle, but fails in some cases
and there are more accurate methods. I apologize if I have failed to find
the right classes and methods in the API, but why doesn't the API provide
the more accurate geodesic calculations that are in geographiclib. It also
seems like it would be good to also provide great circle math as an option.
Am I missing it in the API or is it simply not there? If it is not there is
anyone working on adding it?

Are there any efforts going on to flesh out the QGIS API a little more.
Generally, the methods and parameters are not well documented if it is not
obvious from the name.

Thanks,

Calvin
___
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] Spatialite KyngChaos packaging on OSX not loading spatialite extension

[David Marteau]

Hi,


For some times some people are reporting that plugins using pyspatialite are 
not working anymore  with the KyngChaos packaging for OSX (2.14 or 2.18)

The error is usually:

OperationalError('no such module: VirtualSpatialIndex',)

when trying to référence SpatialIndex in spatial requests.
After investigation it appears that errors occurs when trying to use spatialite 
functions…

The fact is, when using pyspatialite directly from python: the spatialite 
extension is not loaded.

cur.execute('SELECT spatialite_version()')
> OperationalError: no such function: spatialite_version

and so on for any SELECT involving spatialite functions.

This can be explained easily has the pyspatialite python package is only a link 
to the pysqlite2 python package, and thus, do not load the the spatialite 
module. 

Furthemore loading extension is disabled in the KyngChaos sqlite3 package, so 
we are stuck in that the pyspatialite provided by KyngChaos is useless as 
standalone library and do not enable plugins to make direct calls to  
spatialite.


Is there any reason for this situation or this should be considered as a bug ?? 

Actually, the native OSX sqlite3 python binding do not enable leading 
extensions, this was preventing using spatialite from python. This constraint 
has been removed recently in Macport, which now enables to use spatialite with 
python without relying on pyspatialite.



David.

___
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] Processing GUI integration

[Matthias Kuhn]

On 3/31/17 8:15 AM, Paolo Cavallini wrote:

>> I'd like to see a toolbar icon added for opening/closing this panel.
> ì1

And a Fn shortcut, I really appreciate F7 for symbology.
Next on the list are
 * processing
 * the browser to give it a bigger exposure (see also discussion about
unified add layer)
 * the attribute table (F6 shortcut should be in the toolbar icon tooltip)
 * More?

Matthias
___
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 [1209] Batch GPS Importer approval notification.

[noreply]

Plugin Batch GPS Importer approval by pcav.
The plugin version "[1209] Batch GPS Importer 0.1.1" is now approved
Link: http://plugins.qgis.org/plugins/batch_gps_importer/
___
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 [241] Crayfish approval notification.

[noreply]

Plugin Crayfish approval by pcav.
The plugin version "[241] Crayfish 2.5.1" is now approved
Link: http://plugins.qgis.org/plugins/crayfish/
___
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] Are there plans to create a unique "Add layer" tool?

[DelazJ]

Hi,
Thanks Anita for this work. I wasn't aware of your tool. Any reason to not
make it available in the Plugins repo? It might get more audience, unless I
overestimate our repo... Btw: I like the title of the blog post. :-)

So other than Anita's plugin, there's currently no ongoing work to unify
the tools.
>From a doc writer's perspective, it's ok; we'll see how we structure the
chapter.
>From a user's one, would be nice to have things moved in the way of a
unified tool in the next releases. Landing in 3.0 could even sound like a
big change between 2.x series and 3.0. Maybe, taking Anita's work as a
first step and 

Regards,
Harrissou


2017-04-03 6:05 GMT+02:00 Stéphane Henriod :

> Hi all
>
> I must say that Anita's hack seems quite handy and straight forward from a
> user's perspective. Would it be heavy to "just" integrate into the Master
> QGIS? I would be happy to help with testing. More, I unfortunately cannot
> do :-)
>
> Cheers
>
> Stéphane
>
>
>
> Le lundi 3 avril 2017, Tim Sutton  a écrit :
>
>> Hi Anita
>>
>> On 02 Apr 2017, at 10:21 PM, Anita Graser  wrote:
>>
>>
>>
>> On Sun, Apr 2, 2017 at 9:32 PM, Tim Sutton  wrote:
>>
>>> Hi Harrisou
>>>
>>> On 02 Apr 2017, at 4:57 PM, DelazJ  wrote:
>>>
>>> Hi devs,
>>>
>>> In the documentation team, we plan to rewrite the "Supported data
>>> formats" chapter (http://docs.qgis.org/2.14/en/
>>> docs/user_manual/working_with_vector/supported_data.html) which
>>> actually explores many of the different ways to add (vector) layers to
>>> QGIS. It's full of redundant information, not easy to maintain and doesn't
>>> expose tools like the browser panel. Discussion at
>>> https://github.com/qgis/QGIS-Documentation/issues/1088
>>>  if you want
>>> to help.
>>> Before we engage any time on this restructuring and to avoid doing
>>> things twice and because I read some related assertions in the past, I'd
>>> like to ask if there's any plan to merge some of these tools for 3.0... And
>>> if ever, what's the state of the work ?
>>>
>>>
>>> This has been discussed a number of times, and Nathan made some initial
>>> mockups once. But as far as I know, nobody is actively working on this so I
>>> don't know if anything will land in 3.0.
>>>
>>
>> ​I've been working with my "unified add layer button" modification for a
>> few months now: https://anitagraser.com/2016/07/20/one-add-button-to-ru
>> le-them-all/​
>>
>> Wouldn't want to go back. I still sometimes use the Add PostGIS layer
>> dialog from the menus though.
>>
>>
>> Ah thanks I forgot about your post Anita!
>>
>> Regards
>>
>> Tim
>>
>>
>> Best wishes,
>> Anita
>>
>>
>> —
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Tim Sutton*
>>
>> *Co-founder:* Kartoza
>> *Project chair:* QGIS.org
>>
>> Visit http://kartoza.com to find out about open source:
>>
>> Desktop GIS programming services
>> Geospatial web development
>> GIS Training
>> Consulting Services
>>
>> *Skype*: timlinux
>> *IRC:* timlinux on #qgis at freenode.net
>>
>> Kartoza is a merger between Linfiniti and Afrispatial
>>
>>
>
> --
>
> “When you travel, remember that a foreign country is not designed to make
> you comfortable. It is designed to make its own people comfortable." --
> Clifton Fadiman
>
>
> ___
> 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