Sorry for rewinding the thread to where it started.
Provided that users can benefit from keeping the last stable release and an
LTR both installed, do you think that this is up to the specific platform
to handle this (OsGeo4W does it already) or a more general solution can be
provided?
The LTR will
Hey Carlo,
I guess we are a bit confused at the moment because the goal of QGIS has
never really been that at all, at least not post v1. We have always aimed
to make it the best it can be for a lot of different workflows.
I'm not sure I would consider anything in QGIS a step backwords at all,
Th
No pun intended, when you announced what you were going to do, I used
MapInfo as my main GIS and Thuban as a viewer and I hoped very much you
were starting something that was went further.
Since version 0.11 I was using QGIS as my "main" GIS. What I was saying is
that the continuous improvement mad
Hi
> On 03 Mar 2018, at 20:43, Jürgen E. Fischer wrote:
>
> Hi,
>
> On Sat, 03. Mar 2018 at 12:43:00 +0100, Carlo A. Bertelli (Charta s.r.l.)
> wrote:
>> but also abandoned the idea of QGIS as a simple viewer that acquires editing
>> abilities by plugins.
>
> Was that ever a goal? If so, I d
Hi,
On Sat, 03. Mar 2018 at 12:43:00 +0100, Carlo A. Bertelli (Charta s.r.l.) wrote:
> but also abandoned the idea of QGIS as a simple viewer that acquires editing
> abilities by plugins.
Was that ever a goal? If so, I didn't know - but I have been around only for a
bit more than 10 years ;)
J
> If you use
> qgisMinimumVersion=3.0
> qgisMaximumVersion=3.99
> your plugin will only be visible in 3.x
Hi Richard,
Let me clarify: Usually you should only set the qgisMinimumVersion. If it is
set to 3.0, it is
assumed the plugin is compatible with any QGIS 3, thus from *2.99* up to *3.98*
Hey Carlo,
Right I guess the first one is a package issue for unix type installs. On
Windows this is fine as we can run different versions all the time but is a
good point for Linux, etc.
Regarding .qgis2 and .qgis3 This is already isolated in QGIS 3 as the
settings and plugins are now all stored
@Nathan: Yes, to be precise, I mean calling using a different name, say
qgis2 or qgis_ltr and using /usr/lib/libqgis2* instead
of /usr/lib/libqgis*, /usr/lib/qgis2 or /usr/lib/qgis-ltr,
/usr/share/qgis2, /usr/include/qgis2 instead of /usr/include/qgis,
@Richard: That's very good, I overlooked this
On 03-03-18 12:43, Carlo A. Bertelli (Charta s.r.l.) wrote:
> From a user's point of view, having a tried and dependable LTR is an
> important feature.
> The new main version has finally addressed the needed upgrade of python
> (2->3) and Qt (4->5) but also abandoned the idea of QGIS as a simple
>
Hi,
I'm not sure what you mean. Could you explain with an example.
Regards,
Nathan
On 3 Mar. 2018 9:43 pm, "Carlo A. Bertelli (Charta s.r.l.)" <
carlo.berte...@gmail.com> wrote:
> From a user's point of view, having a tried and dependable LTR is an
> important feature.
> The new main version ha
>From a user's point of view, having a tried and dependable LTR is an
important feature.
The new main version has finally addressed the needed upgrade of python
(2->3) and Qt (4->5) but also abandoned the idea of QGIS as a simple viewer
that acquires editing abilities by plugins. Plugins are not an
11 matches
Mail list logo
