Plugin AmigoCloud approval by pcav.
The plugin version "[849] AmigoCloud 0.2 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/qgis-amigocloud-plugin/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info:
On 8 February 2017 at 13:49, wrote:
> Due to previous error, mentioned in a early post, I installed `geos 3.6.1`
> and because build still failed, I place header file `geos_c.h` in
> src/core/geometry folder and replace `` with `"geos_c.h"` in
> `qgsgeometry.h`. This may
Due to previous error, mentioned in a early post, I installed `geos
3.6.1` and because build still failed, I place header file `geos_c.h` in
src/core/geometry folder and replace `` with `"geos_c.h"` in
`qgsgeometry.h`. This may not have been necessary but I wanted to make
it clear which
Ola Alexandre,
Il 07/02/2017 18:18, Alexandre Neto ha scritto:
> So, IMHO, after the release and branch a QGIS LTR version, we can delay
> the documentation branching for a while to give time for a good
> documentation release, but we can't do it for too long, to avoid the
> situation mentioned
In my opinion, we need to take action to make sure that a developer that is
working on a master version feature is not prevented from documenting it
because the documentation team is still working on the 2.16 version issues.
Example:
Plugin sipamsar approval by pcav.
The plugin version "[950] sipamsar 1.7 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/sipamsar/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info:
On Tue, Feb 7, 2017 at 10:43 AM, Jürgen E. Fischer wrote:
> Hi Nyall,
>
> On Tue, 07. Feb 2017 at 09:11:25 +1000, Nyall Dawson wrote:
>> > INSTALL says in requirements Qt >= 5.3.0, Debian stable has 5.3.2.
>
>> That's a mistake. AFAIK we are targeting 5.3 to cater for Debian.
>
>
I don't know what others think, but I think incorporating the new XYZ tile
layers support in the GUI by using WMS as a "parent" layer type is
incorrect:
1. they are a different kind of layer (and I presume not an OGC standard)
2. it hides the support for XYZ layers in QGIS from the user
What do
Definitely "stroke", both because it is the standard term in graphics
software, and also because neither "border" nor "outline" make any sense in
a line.
I agree that a dark grey would be a better choice of default stroke than
black:
I'm not sure we need to break the project here though right? The xml can
stay the same just the API and UI is different.
On Tue, Feb 7, 2017 at 8:01 PM, Paolo Cavallini
wrote:
> Il 07/02/2017 10:59, Nyall Dawson ha scritto:
>
> > Well, ideally not. Currently we only
As a user and not developer (again...), I could also live with my projects
being slightly broken (+1 for the short migration guide) if this is the
price to pay for a perfect consistency of the transparency / opacity
sliders.
In this case I would also favor "transparency" over "opacity"
And I
Il 07/02/2017 10:59, Nyall Dawson ha scritto:
> Well, ideally not. Currently we only break projects which rely on very
> old features (such as 1.x labeling, conversion from old symbology,
> some composer features from maybe 2.6 or earlier). None of these
> breaks are ever likely to be encountered
On 7 February 2017 at 19:54, Paolo Cavallini wrote:
> Il 07/02/2017 10:53, Nyall Dawson ha scritto:
>
>> The issue here is that we potentially break existing projects. While
>> updating the ui & api can be done, how can we handle user's data
>> defined opacity/transparency
Il 07/02/2017 10:53, Nyall Dawson ha scritto:
> The issue here is that we potentially break existing projects. While
> updating the ui & api can be done, how can we handle user's data
> defined opacity/transparency rules?
Aren't we breaking projects for q3 anyway?
Cheers.
--
Paolo Cavallini -
On 7 February 2017 at 19:47, Neumann, Andreas wrote:
> Hi,
>
> +1 for renaming to "stroke". "stroke" is also used as the term in SVG / PDF
> specifications - the two most important vector graphic standards.
>
> As a consequence, we would have related terms, such as
On 7 February 2017 at 19:43, Jürgen E. Fischer wrote:
> Hi Nyall,
>
> On Tue, 07. Feb 2017 at 09:11:25 +1000, Nyall Dawson wrote:
>> > INSTALL says in requirements Qt >= 5.3.0, Debian stable has 5.3.2.
>
>> That's a mistake. AFAIK we are targeting 5.3 to cater for Debian.
>
>
Il 07/02/2017 10:47, Neumann, Andreas ha scritto:
> +1 for renaming to "stroke". "stroke" is also used as the term in SVG /
> PDF specifications - the two most important vector graphic standards.
fine, thanks Andreas for the analysis.
> Another candidate would be renaming everything
Hi,
+1 for renaming to "stroke". "stroke" is also used as the term in SVG /
PDF specifications - the two most important vector graphic standards.
As a consequence, we would have related terms, such as "stroke-width",
"stroke-linecap", "stroke-dasharray", etc. See
Hi Nyall,
On Tue, 07. Feb 2017 at 09:11:25 +1000, Nyall Dawson wrote:
> > INSTALL says in requirements Qt >= 5.3.0, Debian stable has 5.3.2.
> That's a mistake. AFAIK we are targeting 5.3 to cater for Debian.
Debian jessie (stable) has GDAL 1.10.1 - too old for us.
Debian stretch (testing) has
As a non-Dev (only a user) and a non native English speaker:
- Yes to consistency!
- "Stroke" is also less clear to me than "Border" or "Outline". I would
prefer one of those 2 but I will not object if english-speakers think that
"stroke" is more correct
- Yes to keep the stroke /
Hi Gordon,
On Mon, 06. Feb 2017 at 11:48:53 -0500, gor...@shieldaig.com wrote:
> But doesn't build on Ubuntu 16.10 which uses Qt 5.6.
There are nightlies of master for yakkety (16.10) which build fine (see
https://dash.orfeo-toolbox.org/index.php?project=QGIS).
Jürgen
--
Jürgen E. Fischer
Hey Larry,
Thanks for your reply. It's sometimes tough to mention Esri on this list
without hackles getting raised, but it's out there. It's a fact. People use it.
Some HAVE to use it. I'm in that crowd. It would be wrong on your part to
assume that because I use it, I am unappreciative of the
Il 07/02/2017 10:09, Nyall Dawson ha scritto:
> I agree, and tried to do this change a while ago. Unfortunately it's
> not easy (possible?). Here's an example why:
Urhg, too bad - thanks for the analysis. Cleaning this up deeply would
require much work, right?
All the best.
--
Paolo Cavallini -
On 7 February 2017 at 19:05, Mathieu Pellerin wrote:
> I'm -1 on removing polygon outline by default. In many datasets (think
> administrative boundaries, cadastral polygons, etc.), polygons share
> boundaries and the outline is important.
>
> On the other hand, I'm not
I'm -1 on removing polygon outline by default. In many datasets (think
administrative boundaries, cadastral polygons, etc.), polygons share
boundaries and the outline is important.
On the other hand, I'm not against improving things by default :) IMHO, we
could greatly improve default coloring by
Il 07/02/2017 09:52, Nyall Dawson ha scritto:
> Following up on one of the points raised by John Hawkison (author of
> the famous "my first weekend with QGIS" email), I'd like to raise
> discussion about renaming all use of outline/border throughout QGIS to
> "stroke".
...
> Any opinions here?
+1 from me.
On Tue, Feb 7, 2017 at 3:52 PM, Nyall Dawson wrote:
> Hi all,
>
> Following up on one of the points raised by John Hawkison (author of
> the famous "my first weekend with QGIS" email), I'd like to raise
> discussion about renaming all use of outline/border
Hi all,
Following up on one of the points raised by John Hawkison (author of
the famous "my first weekend with QGIS" email), I'd like to raise
discussion about renaming all use of outline/border throughout QGIS to
"stroke".
I've been thinking about this and I'm personally in favour.
Why?
- the
28 matches
Mail list logo