Re: [Qgis-developer] Changing behaviour of "show selected features" mode for attribute table

[Matthias Kuhn]

On 08/03/2017 18:45, Giovanni Manghi wrote:

> Hi all,
>
>> Hi I agree with Nathan, empty table by default will freak out users.
>> Could we imagine some heuristics that will let the whole table being seen
>> for reasonable sized tables, and only a subset for huge tables, advertised
>> by a warning bar ?
>>
>> I think of displaying visible items in mapcanvas if their number is not too
>> high, and if still too high, remember to show only selected items?
>> We need an exception of course for non geometric tables on that.
>>
>> I would not be shocked by such messages, huge tables should not be entirely
>> fetched, raising a security fence to the user sounds reasonable to me.
> +1
>
> but also... why not
>
> https://github.com/qgis/QGIS/pull/2518

Thanks Giovanni, same thoughts here.

>
> ?
>
> 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
>

___
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] is QGIS supposed to build with Qt 5.8?

[Larry Shaffer]

Hi,

On Tue, Mar 7, 2017 at 12:17 AM, G. Allegri  wrote:

> Thanks Nyall, I will abandon the struggle for now.
> I just wanted to try some new features from Qt3D that were added in the
> last release.
>

I just got QGIS 3 compiling against Qt 5.8, using some custom Homebrew
formulae on macOS 10.11.6. However, Homebrew is still a day or two off from
fully supporting Qt 5.8 in all the packages that QGIS uses.

I have not noticed any major runtime errors beyond this one, specific to
macOS:
https://bugreports.qt.io/browse/QTBUG-57706
That causes QGIS to stall upon loading the splash screen, requiring the
user to hit Return twice to proceed. Definite regression in Qt 5.7.x -->
5.8.0.

On the plus side, for macOS, all the icons now show up properly for actions
in the menus.


Larry Shaffer
Dakota Cartography
Black Hills, South Dakota
--
Boundless Desktop and QGIS Support/Development
Boundless Spatial - http://boundlessgeo.com
lshaf...@boundlessgeo.com



> giovanni
>
> Il 7 mar 2017 01:47, "Nyall Dawson"  ha scritto:
>
>> On 7 March 2017 at 10:41, G. Allegri  wrote:
>> > Hi Nyall,
>> > Ubuntu 16.04 + Qt Creator 5.8.0 (deb package).
>> > Qt 5.8 come from Qt Creator (under /opt path).
>> > Qt 5.5 from apt. Generating and building against these is ok.
>>
>> I'm not sure. I'm not aware of any platforms where QGIS is currently
>> built against 5.8 (since 5.8 on homebrew is broken, and all stable
>> distros are 5.7. Windows is 5.7 too), so there's possibly things we'll
>> need to change.
>>
>> But last time I tried to build against any non-repo packages on Ubuntu
>> I just couldn't get it to succeed either.
>>
>> Nyall
>>
>
> ___
> 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

[Qgis-developer] Plugin [420] Video Uav Tracker approval notification.

[noreply]

Plugin Video Uav Tracker approval by pcav.
The plugin version "[420] Video Uav Tracker 2.0" is now approved
Link: http://plugins.qgis.org/plugins/Video_UAV_Tracker/
___
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] Changing behaviour of "show selected features" mode for attribute table

[Giovanni Manghi]

Hi all,

> Hi I agree with Nathan, empty table by default will freak out users.
> Could we imagine some heuristics that will let the whole table being seen
> for reasonable sized tables, and only a subset for huge tables, advertised
> by a warning bar ?
>
> I think of displaying visible items in mapcanvas if their number is not too
> high, and if still too high, remember to show only selected items?
> We need an exception of course for non geometric tables on that.
>
> I would not be shocked by such messages, huge tables should not be entirely
> fetched, raising a security fence to the user sounds reasonable to me.

+1

but also... why not

https://github.com/qgis/QGIS/pull/2518

?

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

[Qgis-developer] Plugin [1187] Split Polygon Showing Areas approval notification.

[noreply]

Plugin Split Polygon Showing Areas approval by pcav.
The plugin version "[1187] Split Polygon Showing Areas 0.4" is now approved
Link: http://plugins.qgis.org/plugins/SplitPolygonShowingAreas/
___
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] Port Password Helper plugin into core

[Alessandro Pasotti]

Hi,

Boundless has developed a C++ plugin [1] to allow storage and
synchronization of the QGIS master password with the OS password manager.
The plugin has been tested on Windows, Mac and Linux.

The plugin is based on qtkeychain library [2], that would become a new
dependency, the library is available on major linux distributions, it is in
homebrew and can be easily build on Windows.

Any objection if I start the integration into core? It will not be a C++
plugin but part of the authentication manager.

The reasons for having it in core is that  the current implementation uses
a pure hack to capture the password from the credentials dialog (and it's
not completely secure), there are plans to tighten security of the
authentication manager and the password helper code will need to access to
the internals of the password manager in order to interact with the
credentials storage.


[1] https://github.com/boundlessgeo/qgis-master-pass-cxxplugin
[2] https://github.com/frankosterfeld/qtkeychain

-- 
Alessandro Pasotti
w3:   www.itopen.it
___
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] Fwd: [OSGeo-Discuss] GSoC Mentors - Action required!

[Werner Macho]

Hi Lists,

As of today there is still no mentor for any QGIS related project
entered on the according webpage [1].

[1] 
https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Administrative#Mentors

Please read the forwarded mail.

regards
Werner

-- Forwarded message --
From: Margherita Di Leo 
Date: Wed, Mar 8, 2017 at 2:33 PM
Subject: [OSGeo-Discuss] GSoC Mentors - Action required!
To: OSGeo Discussions , ICA OSGeo Labs list
, OSGeo-SoC ,
geofor...@lists.osgeo.org


Dear All,

at today, we have only 9 registered mentors, which I believe is not
the final number. If you are willing to mentor a student for Google
Summer of Code, here's what to do: add yourself here [1], clearly
indicating the *title* of the idea you are willing to mentor (no link
to ideas page, please). I will then send you an invite to join the
OSGeo organization on the GSoC website.
The Google Summer of Code program is a great way to attract new
developers and expand our software communities. Moreover, I would
really much like to see more of our former GSoC students engaging in
mentoring this year's fellows students.
Please, forward this email to your software communities!

Kind regards,


[1] 
https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2017_Administrative#Mentors

--
Margherita Di Leo

___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
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] New branch for 3.x documentation (master_3x)

[Alexandre Neto]

Hi all,

Following Mathias Kuhn suggestions we change strategy a bit:

1) "release_2.18" branch is now the default working branch;
2) all commits landing on "release_2.18" branch will be "immediately"
cherry-picked to "master";
2) 3.x features will documented directly on "master" branch.

If everything goes according to plan, by the time we release 2.18
documentation, the "master" branch will be fully updated and ready to
became the default branch again.

Thank you all for your help and input.

Alexandre Neto


Alexandre Neto  escreveu no dia quarta, 8/03/2017 às
10:37:

> Just an amend. The correct tag to inform that documentation is needed is
> [NEEDS-DOCS] (mind the S's).
>
> Thanks Harrisou for spotting the error
>
> Alexandre Neto
>
> Alexandre Neto  escreveu no dia quarta, 8/03/2017
> às 01:32:
>
> To help us document the all the new features, we kindly ask all developers
> to add the [FEATURE] and [NEED-DOCS] tags in their commits and provide some
> simple guidance on how to use the new features in the commit message.
>
>
>
>
>
>
>
>
> Thanks
>
> Alexandre Neto
>
> [0] -
> https://lists.osgeo.org/pipermail/qgis-developer/2017-March/047346.html
> [1] - https://github.com/qgis/QGIS-Documentation/tree/master_3x
> [2] -
> https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22QGIS+2.16%22
> [3] -
> https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22QGIS+2.18%22
> --
> Alexandre Neto
> -
> @AlexNetoGeo
> http://sigsemgrilhetas.wordpress.com
> http://gisunchained.wordpress.com
>
> --
> Alexandre Neto
> -
> @AlexNetoGeo
> http://sigsemgrilhetas.wordpress.com
> http://gisunchained.wordpress.com
>
-- 
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] Plugin [629] networks approval notification.

[noreply]

Plugin networks approval by pcav.
The plugin version "[629] networks 1.2.9" is now approved
Link: http://plugins.qgis.org/plugins/networks/
___
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] PyQgsServerTest :: test_wms_getprint_srs disabled

[Matthias Kuhn]

On 03/08/2017 11:28 AM, Alessandro Pasotti wrote:

> I tried to reproduce the issue locally without success.
> 
> I suggest for now to either split the printing tests into a separate
> file or better (if there is single test failing) just decorate the test
> as allowed to fail so that the whole suite does not fail.
> 
> When done, we can re-enable the server test in travis.

There is no `AllowFailure` available IIRC. There is only an
`ExpectedFailure` which will fail if the test succeeds.

Adding an infrastructure for something like this would be much
appreciated (similar to how ExpectedFailure is handled).
But splitting into a different file will be easier.

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

Re: [Qgis-developer] New branch for 3.x documentation (master_3x)

[Alexandre Neto]

Just an amend. The correct tag to inform that documentation is needed is
[NEEDS-DOCS] (mind the S's).

Thanks Harrisou for spotting the error

Alexandre Neto

Alexandre Neto  escreveu no dia quarta, 8/03/2017 às
01:32:

> To help us document the all the new features, we kindly ask all developers
> to add the [FEATURE] and [NEED-DOCS] tags in their commits and provide some
> simple guidance on how to use the new features in the commit message.
>
>






> Thanks
>
> Alexandre Neto
>
> [0] -
> https://lists.osgeo.org/pipermail/qgis-developer/2017-March/047346.html
> [1] - https://github.com/qgis/QGIS-Documentation/tree/master_3x
> [2] -
> https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22QGIS+2.16%22
> [3] -
> https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22QGIS+2.18%22
> --
> Alexandre Neto
> -
> @AlexNetoGeo
> http://sigsemgrilhetas.wordpress.com
> http://gisunchained.wordpress.com
>
-- 
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

Re: [Qgis-developer] PyQgsServerTest :: test_wms_getprint_srs disabled

[Alessandro Pasotti]

On Tue, Mar 7, 2017 at 9:12 AM, Paul Blottiere 
wrote:

>
> > It sounds strange to me that it was never observed in production, but I
> did not search the hub for an existing ticket, it might have been reported.
>
>
> The test seems to fail in very specific conditions (that I have not yet
> found). As Mathias suggested, I made a loop on the test. And even with 1000
> iterations, it's still not failing whatever the branch (master or 2.14)...
> Maybe it has never been observed.
>
>
> Paul
>
>
>
I tried to reproduce the issue locally without success.

I suggest for now to either split the printing tests into a separate file
or better (if there is single test failing) just decorate the test as
allowed to fail so that the whole suite does not fail.

When done, we can re-enable the server test in travis.



> On 03/07/2017 08:53 AM, Alessandro Pasotti wrote:
>
> On Tue, Mar 7, 2017 at 8:48 AM, Paul Blottiere <
> paul.blotti...@oslandia.com> wrote:
>
>> Alessandro,
>>
>>
>> > do you have clue if the multi-threading rendering could be the root
>> cause of this issue?
>>
>> The test is failing on travis for 2.14 too. However, PR about the
>> replacement of the QgsMapRenderer and the parallel rendering activation are
>> not backported in 2.14. So, as it happens both on master and 2.14, it seems
>> to be independent from the rendering step.
>>
>>
>> Only unit tests on the getprint service has been backported and before
>> that, there was none. So I think that the failing test is just underlying
>> an old issue which was there even before we started to refactor the server.
>>
>>
>> What do you think?
>>
>
> I'm afraid you are right ...
>
> It will be difficult to spot it out, by the way I think that the test did
> a good work to discover this issue.
>
> It sounds strange to me that it was never observed in production, but I
> did not search the hub for an existing ticket, it might have been reported.
>
>
>
>> Paul
>>
>>
>>
>> On 03/07/2017 08:16 AM, Alessandro Pasotti wrote:
>>
>> On Mon, Mar 6, 2017 at 5:30 PM, Paul Blottiere 
>> wrote:
>>
>>> Hi Alessandro,
>>>
>>>
>>> can you please have a look?
>>>
>>> I'm afraid this failure is not a problem in the test itself but a
>>> symptom of more serious issue: the map is completely missing from the
>>> generated print.
>>>
>>> FYI, the same test also fails on 2.14 as discussed on the following
>>> commit:
>>>
>>>
>>> I took a look but I cannot reproduce the failing test
>>> test_wms_getprint_srs.
>>>
>>> Actually, I have tested it within the next environment without issues:
>>> - master on Debian
>>> - release-2_14 on Ubuntu.
>>>
>>> Can anyone confirm?
>>>
>>> Paul
>>>
>>
>>
>> Paul,
>>
>> Thanks for looking into this, I'll do some local testing shortly, do you
>> have clue if the multi-threading rendering could be the root cause of this
>> issue?
>>
>> A s a side note, I would recommend to refactor the server test and split
>> it in smaller dedicated tests for the different services.
>>
>>
>>
>> --
>> Alessandro Pasotti
>> w3:   www.itopen.it
>>
>>
>> ___
>> Qgis-developer mailing listqgis-develo...@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
>> --
> Alessandro Pasotti w3:   www.itopen.it
>
>


-- 
Alessandro Pasotti
w3:   www.itopen.it
___
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] New branch for 3.x documentation (master_3x)

[Alexandre Neto]

Hi Mathias,
Having two babies in the house, I'm all for avoiding sleepless nights!

Not sure I followed your suggestion. AFAIK, The "master" branch (future
release-2_18) is already the default branch. And our plan was to keep a
close eye on that branch and continuously forward port everything from
master to master_3x, to avoid that single "big bang".

Maybe I'm not understanding your suggestion. If you don't mind, I will ping
you on gitter.

Alexandre Neto

A qua, 8/03/2017, 07:30, Matthias Kuhn  escreveu:

Hi all,

Nice move!

I have a minor note on the setup.

"master_3x" will be merged into "master"* sounds like a plan, but I guess
in reality someone will spend days trying to figure out how to solve those
damned conflicts. I would strongly suggest against merging production
branches as this leads to a single "big bang" with interleaved effects of
documentation commits that have already been forward ported and missing
ones.
Instead I would propose to follow the branching schema of QGIS. On github
you can define the "default branch" in the repository settings to
release-2_18, so pull requests will be opened against this branch by
default at the moment.

Just my 2c, maybe it helps to avoid some sleepless nights if this adjusted
right now ;)

Matthias


On 08/03/2017 02:32, Alexandre Neto wrote:

Hello All,

As a result of a long discussion around how to contribute with
documentation for 3.x new features [0]
,
we decided to create a master_3x branch [1]
.

>From now on, all new features landing on QGIS 2.99 should be documented in
the "master_3x" branch.

All new documentation and improvements as we go through the latest releases
issues (2.16 [2]

and 2.18 [3]) should still be worked on the master branch. When it makes
sense, the documentation team will do his best to "forward port" them to
master_3x branch.

After 2.18 release as LTR (June?) and consequent release of 2.18
documentation, "master_3x" will be merged into "master" and all should go
back to normal. That is, all contributions can be done in the "master"
branch.

To help us document the all the new features, we kindly ask all developers
to add the [FEATURE] and [NEED-DOCS] tags in their commits and provide some
simple guidance on how to use the new features in the commit message.

Thanks

Alexandre Neto

[0] -
https://lists.osgeo.org/pipermail/qgis-developer/2017-March/047346.html
[1] - https://github.com/qgis/QGIS-Documentation/tree/master_3x
[2] -
https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22QGIS+2.16%22
[3] -
https://github.com/qgis/QGIS-Documentation/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22QGIS+2.18%22
-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com


___
Qgis-developer mailing listqgis-develo...@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

-- 
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] Plugin [557] autoSaver approval notification.

[noreply]

Plugin autoSaver approval by pcav.
The plugin version "[557] autoSaver 2.3" is now approved
Link: http://plugins.qgis.org/plugins/autoSaver/
___
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] PyQGIS documentation (and SIP files)

[Alessandro Pasotti]

On Wed, Mar 8, 2017 at 9:34 AM, Nathan Woodrow  wrote:

> I'm not sure we need the headers in the sip files to make a python docs
> API do we. That is the first thing to work out.
>

I don't know, all I know is that you can build API docs with doxygen using
sip files as a source: this is an ancient try that I did a few years ago
http://www.itopen.it/qgis/serverplugins/api/classQgsServerInterface.html

The result is far from ideal though, but maybe it could be refined.
There might be other ways to build the Python API docs, like using
introspection, but I'm not sure about how can we grab the documentation
from the C++ headers if we go that route.




>
> On Wed, 8 Mar 2017 6:23 pm Alessandro Pasotti  wrote:
>
>> Hi,
>>
>> I think we still lack a up-to-date comprehensive documentation targeted
>> to Python QGIS developers and I would like to discuss the options that we
>> have to improve the current situation.
>>
>> As a Python QGIS developer, what I probably need is:
>> 1. Python API docs, possibly with examples
>> 2. Developer documentation about how to write PyQGIS plugins and
>> standalone applications
>> 3. Tutorials and examples
>> 4. Scaffolding
>>
>>
>> 2 and 3. the cookbook is doing a very good job, but it could probably be
>> improved and kept in sync with the API changes
>> 4. is perfectly covered by plugin builders
>> 1. this is were IMO we should do better: for most experienced QGIS
>> developers it's perfectly fine to look at the C++ API docs, but I think
>> that for Python developers that is not ideal
>>
>> There have been some efforts to build PyQGIS API documentation:
>> http://geoapis.sourcepole.com/qgispyapi/qgisinterface , maybe Sourcepole
>> colleagues could share their experience in building that pages.
>>
>> My main concern here is that we are slowly moving away from documenting
>> SIP files, I don't know if we can still build PyQGIS documentation without
>> documenting the SIP files but we should think carefully before taking a
>> move that will block us from using SIP files as a source for building the
>> docs.
>>
>>
>> What do you think about this?
>>
>>
>> --
>> Alessandro Pasotti
>> w3:   www.itopen.it
>> ___
>> 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
>
>


-- 
Alessandro Pasotti
w3:   www.itopen.it
___
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 [1187] Split Polygon Showing Areas approval notification.

[noreply]

Plugin Split Polygon Showing Areas approval by pcav.
The plugin version "[1187] Split Polygon Showing Areas 0.3" is now approved
Link: http://plugins.qgis.org/plugins/SplitPolygonShowingAreas/
___
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] PyQGIS documentation (and SIP files)

[Nathan Woodrow]

I'm not sure we need the headers in the sip files to make a python docs API
do we. That is the first thing to work out.

On Wed, 8 Mar 2017 6:23 pm Alessandro Pasotti  wrote:

> Hi,
>
> I think we still lack a up-to-date comprehensive documentation targeted to
> Python QGIS developers and I would like to discuss the options that we have
> to improve the current situation.
>
> As a Python QGIS developer, what I probably need is:
> 1. Python API docs, possibly with examples
> 2. Developer documentation about how to write PyQGIS plugins and
> standalone applications
> 3. Tutorials and examples
> 4. Scaffolding
>
>
> 2 and 3. the cookbook is doing a very good job, but it could probably be
> improved and kept in sync with the API changes
> 4. is perfectly covered by plugin builders
> 1. this is were IMO we should do better: for most experienced QGIS
> developers it's perfectly fine to look at the C++ API docs, but I think
> that for Python developers that is not ideal
>
> There have been some efforts to build PyQGIS API documentation:
> http://geoapis.sourcepole.com/qgispyapi/qgisinterface , maybe Sourcepole
> colleagues could share their experience in building that pages.
>
> My main concern here is that we are slowly moving away from documenting
> SIP files, I don't know if we can still build PyQGIS documentation without
> documenting the SIP files but we should think carefully before taking a
> move that will block us from using SIP files as a source for building the
> docs.
>
>
> What do you think about this?
>
>
> --
> Alessandro Pasotti
> w3:   www.itopen.it
> ___
> 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

[Qgis-developer] PyQGIS documentation (and SIP files)

[Alessandro Pasotti]

Hi,

I think we still lack a up-to-date comprehensive documentation targeted to
Python QGIS developers and I would like to discuss the options that we have
to improve the current situation.

As a Python QGIS developer, what I probably need is:
1. Python API docs, possibly with examples
2. Developer documentation about how to write PyQGIS plugins and standalone
applications
3. Tutorials and examples
4. Scaffolding


2 and 3. the cookbook is doing a very good job, but it could probably be
improved and kept in sync with the API changes
4. is perfectly covered by plugin builders
1. this is were IMO we should do better: for most experienced QGIS
developers it's perfectly fine to look at the C++ API docs, but I think
that for Python developers that is not ideal

There have been some efforts to build PyQGIS API documentation:
http://geoapis.sourcepole.com/qgispyapi/qgisinterface , maybe Sourcepole
colleagues could share their experience in building that pages.

My main concern here is that we are slowly moving away from documenting SIP
files, I don't know if we can still build PyQGIS documentation without
documenting the SIP files but we should think carefully before taking a
move that will block us from using SIP files as a source for building the
docs.


What do you think about this?


-- 
Alessandro Pasotti
w3:   www.itopen.it
___
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