Re: [QGIS-Developer] New MapTools for Circle, ellipse, regular polygon

[L.Bartoletti]

On 20 May 2017 at 04:16, L.Bartoletti  wrote:

Hello,

I would like, if I have time, to add the GUI for the classes I recently
added (Circle, ellipse, regular polygon).

Great news - I've long wanted a simple way to draw circles (and if I
can add a feature request - rectangles too!). Thanks for all your
recent work implementing the base components of this in the c++
classes.

Thank you!
You can already do this via my plugin CADDigitize (rectangle too) or QAD 
(expect rectangle). Obviously, I can also add the rectangles. It will 
certainly be necessary to create a new class or modify QgsRectangle 
which today has no possibility of rotation (azimuth, inclination).

Here's what I'd suggest:

1. QgsMapToolCapture needs refactoring. It's become quite messy and
the interface is tied too heavily to the existing subclasses, making
it difficult to add new capture tools. I think this should be
refactored so that subclasses implement two virtual methods - one for
returning the geometry for the temporary rubber band which is shown
while moving the mouse during digitizing, and one for returning the
actual created QgsGeometry corresponding to the current clicked
points.

2. Create QgsMapToolAddFeature subclasses for each of the new "add
shape" actions. Assuming that the QgsMapToolCapture API is cleaned,
this should be quite simple to do for each shape type. I'd actually go
crazy here - and add multiple tools for each shape type, so you could
have tools for "add ellipse by center and radius", "add ellipse by
bounding box", etc. Same for rectangles - we could have a "add
rectangle by clicking two opposite corners tools", and an ArcGIS style
"add rectangle by clicking one corner, clicking the other end of this
side, and then clicking the opposite side tool" (see
https://www.youtube.com/watch?v=YdeRhpDmf2s). This approach would
automatically play very nicely with the existing advanced digitizing
dock constraints + inbuilt snapping tools.

3. Expose these construction tools via a new toolbar. Group the
similar tools together with the little down arrows to select between
them + remember which was the last tool used and show that one by
default (just like how the select tools are grouped and operate). So
there'd be a group for rectangle construction, ellipse construction,
regular polygon construction.

OK. I think it sounds like what I did with CADDigitize (for GUI part).
I think that it will also be necessary to modify classes for the snap if 
later we wish to realize ("CAD") modifications of entities (trim, 
extend, chamfer, bevel ...)

(Incidentally - I really want to see this happen, and I'm happy to
provide mentorship for these changes if you require.)

(Oh yeah, that would be great!)

Loïc.

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

Re: [QGIS-Developer] Python 3 compatibility

[Nyall Dawson]

On 25 May 2017 at 00:52, Andreas Plesch  wrote:
> On my linux system (gentoo) QGis 2.18 is using the system python which is
> set to Python 3 whereas on my windows system QGis 2.18 is using the bundled
> Python 2.
>
> This lead to me to start to look for which Python is used in processing
> scripts leading to lines such as:
>
> http_server = ('SimpleHTTPServer', 'http.server')[sys.version_info.major ==
> 2]
>
> With QGis 3 using Python 3 (I believe), there be will be a desire to write
> scripts and plugins which are compatible with both Python 2 and Python 3.
>
> Is there a recommendation of how to accomplish this compatibility ?
>
> Or is the general recommendation to have and maintain separate programs for
> each version ? I suspect the answer is yes here but perhaps there are other
> approaches.

That's what I'd strongly suggest. Otherwise you'll end up with a ton
of branching code trying to maintain compatibility with the older
libraries.

You could put the existing plugin version into some type of
"maintenance" only mode for 2.x and move all feature development into
a new, clean 3.0 branch.

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] Plugin [1240] Geo Picker approval notification.

[noreply]

Plugin Geo Picker approval by pcav.
The plugin version "[1240] Geo Picker 0.1.1 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/GeoPicker/
___
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-developer] Status of QGIS3

[Richard Duivenvoorde]

On 24-05-17 20:05, Radim Blazek wrote:
> Hi.
> 
> On Thu, Jan 26, 2017 at 9:04 PM, Andreas Neumann  wrote:
> 
>> What is already done:
>> Python plugin update helper 2 to 3
> 
> Does it mean a doc? Can you point me to the website? I am looking for
> a python plugin upgrade guide.

Not a guide, but a script you can use:

https://github.com/qgis/QGIS/blob/master/scripts/2to3

it uses all stuff from

https://github.com/qgis/QGIS/tree/master/scripts/qgis_fixes

You could run the script and see what is changed?

Regards,

Richard
___
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-developer] Status of QGIS3

[Radim Blazek]

Hi.

On Thu, Jan 26, 2017 at 9:04 PM, Andreas Neumann  wrote:

> What is already done:
> Python plugin update helper 2 to 3

Does it mean a doc? Can you point me to the website? I am looking for
a python plugin upgrade guide.

Radim
___
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 3D Grant

[Syd Visser]

Martin


Thanks for the clarification. We look forward to seeing better 3D 
support more integrated into Qgis. Without good 3D support people here 
keep moving back to commercial software.


Unfortunately as far as i can see PostGIS supports 3D vector and 3D 
point clouds 2D raster but not 3D raster. The only opensource database 
program that I know of that supports 3D raster is Grass which we use for 
that purpose. But we usually do our viewing in Paraview or Mayavi 
therefore to be able to view in QGIS would be a read advantage.


Keep up the good work on QGIS it is really getting very good.


thanks

Syd


*Syd (Sipke) Visser, P.Geo.*
President, Snr. Geophysicist/Geologist

Tel: 1 (604) 582-1100
Cell: 1 (604) 813-1440
s...@sjgeophysics.com
www.sjgeophysics.com 



On 2017-05-23 08:40 PM, Martin Dobias wrote:

Hi Syd

The idea is to have support for proper 3D meshes/volumes, not just
2.5D geometries. The initial work should introduce interface for 3D
renderers (somehow similar to 2D renderers we have now) allowing
generation of arbitrary meshes and associated materials from input
data (which could be 2D geometries, 2.5D geometries or 3D geometries)
- to create e.g. buildings extruded from their footprint, tree objects
from points or underground pipes from linestring geometries. In the
initial work we may not have support for reading true 3D geometries
from data sources like PostGIS, but that should not be a problem to
add at some point later when the 3D rendering framework is in place.

Regards
Martin


On Tue, May 23, 2017 at 10:41 PM, Syd Visser  wrote:

I have a question on the 3D that was proposed in the grant for the use with
QT 3D. Am i wrong to think this is really oriented towards what some people
call 2.5D (terrain model as shown in the proposal example) or will there be
support for 3D that will be able to display 3D meshes or volumes like those
available in Grass and display in programs such as NVIZ and Paraview or more
advanced commercial software. As geophysicists we are always trying to look
at things under the ground not on top.

thanks

Syd

--

Syd (Sipke) Visser, P.Geo.
President, Snr. Geophysicist/Geologist

Tel: 1 (604) 582-1100
Cell: 1 (604) 813-1440
s...@sjgeophysics.com
www.sjgeophysics.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 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] Python 3 compatibility

[Andreas Plesch]

On my linux system (gentoo) QGis 2.18 is using the system python which is
set to Python 3 whereas on my windows system QGis 2.18 is using the bundled
Python 2.

This lead to me to start to look for which Python is used in processing
scripts leading to lines such as:

http_server = ('SimpleHTTPServer', 'http.server')[sys.version_info.major ==
2]

With QGis 3 using Python 3 (I believe), there be will be a desire to write
scripts and plugins which are compatible with both Python 2 and Python 3.

Is there a recommendation of how to accomplish this compatibility ?

Or is the general recommendation to have and maintain separate programs for
each version ? I suspect the answer is yes here but perhaps there are other
approaches.

Any insight or comment much appreciated,

-Andreas


-- 
Andreas Plesch
39 Barbara Rd.
Waltham, MA 02453
___
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] [Qgis-developer] Are there plans to create a unique "Add layer" tool?

[Alessandro Pasotti]

Hi,

a quick update:

I've prepared a PR with a working prototype in
https://github.com/qgis/QGIS/pull/4629, I need some feed-back and some
help, expecially UX/UI about if we want it as a dockable dialog too (and
how to make it user-configurable).

Feed-back welcome (but please keep it limited in scope to phase 1).

Cheers



On Fri, May 19, 2017 at 9:45 AM, Richard Duivenvoorde 
wrote:

> On 19-05-17 01:23, Nyall Dawson wrote:
>
> > On this note - I've recently discovered the need for some type of
> > reusable layer selection widget which allows choice of existing
> > layers/loading new layers from the file system/loading new layers from
> > available db/online connections. This would be extremely valuable for
> > processing too!
> >
> > So I'm really glad to hear that you'll be pushing ahead with this work
> > - thanks Boundless!
>
> Yep, and thanks Alessandro for the screenie. Makes me want more!
>
> @Nyall in Essen the talk was to start with what Alessandro wrote in his
> email, so 1 dialog 'merging' all buttons/widgets/dialogs into one, reuse
> as much as possible. So it was possible to get it into 3.0
>
> Off course people (.../me) started brainstorming about features which
> w/could be added too :-)
>
> Your idea adds (I think) to the idea to make some kind of
> 'datamanagement-console' in near future, where you can create/copy
> data(!), move data around (browser part) or delete it.
> Your note fits in this isn't it?
>
> Regards,
>
> Richard
>
>
> ___
> 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

Re: [QGIS-Developer] Qt Designer Cannot Drop Widgets onto QgsDockWidget

[Denis Rouzaud]

Hi Calvin,

I can reproduce.
This is very strange as the custom widget is indeed defined as a container,
so it should be able to receive widgets.
I tried on fedora + master, you tried on windows + 2.18, so it doesn't seem
to be OS or Qt version dependant.

Anyone else can confirm?

Cheers,
Denis

Le mar. 23 mai 2017 à 17:01, C Hamilton  a écrit :

> If I start with a QgsDockWidget in Qt Designer rather than a QDockWidget,
> I cannot add another widget to it. With QDockWidget I have a QWidget inside
> and then all of the other components. I simply cannot add anything to
> QgsDockWidget. Is anyone else having the same problem?
>
> I am using the latest version (2.18.8) shipped with the OSGeo4W installer
> on Windows 7.
>
> 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 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 [1244] Mapzen Isochrones approval notification.

[noreply]

Plugin Mapzen Isochrones approval by pcav.
The plugin version "[1244] Mapzen Isochrones 0.1" is now approved
Link: http://plugins.qgis.org/plugins/qgsMapzenIsochrones-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