Hi
On Wed, Mar 20, 2013 at 1:34 AM, Olivier Dalang
olivier.dal...@gmail.com wrote:
Hi !
Just for information :
- will QGis 2.0 have the PyQt API changed to version 2 ?
I don't understand?
- will it have a separate plugin folder than QGis 1.8 ?
It would probably make sense for it to have a
I was talking about that proposition:
http://osgeo-org.1560.n6.nabble.com/Merging-of-incompatible-changes-td5010325.html
( specifically the part about using the new api, as explained here :
http://pyqt.sourceforge.net/Docs/PyQt4/incompatible_apis.html )
2013/3/20 Tim Sutton li...@linfiniti.com
Hi !
Just for information :
- will QGis 2.0 have the PyQt API changed to version 2 ?
- will it have a separate plugin folder than QGis 1.8 ?
Thanks !
Olivier
2013/3/15 Tim Sutton li...@linfiniti.com
Hi All
Just to confirm on this thread that following the discussions here the
following
Pushed to master branch now.
On 13.03.2013 17:44, Marco Hugentobler wrote:
Hi devs
The first part of the symbology improvements is available in my github
fork:
https://github.com/mhugent/Quantum-GIS/tree/data_defined_symbology
Currently, one symbol is either in mm or in map units. The
Hi All
Just to confirm on this thread that following the discussions here the
following updated timeline to 2.0 will apply:
1 April 2013 - Feature freeze - no new features in master
1 May 2013 - GUI Freeze and String freeze - no changes to ui or
strings except where required for critical bug
Hi devs
The first part of the symbology improvements is available in my github fork:
https://github.com/mhugent/Quantum-GIS/tree/data_defined_symbology
Currently, one symbol is either in mm or in map units. The changeset in
the branch adds the possibility to mix different output units ( mm /
Hi
On 03/04/2013 08:17 PM, Larry Shaffer wrote:
Hi,
On Mon, Mar 4, 2013 at 6:40 AM, Tim Sutton li...@linfiniti.com
mailto:li...@linfiniti.com wrote:
Hi
On Mon, Mar 4, 2013 at 1:52 PM, Radim Blazek
radim.bla...@gmail.com mailto:radim.bla...@gmail.com wrote:
On Mon, Mar 4,
Hi Tim
The release plan sounds good to me (especially the longer bug fix
period). I don't know however if 15 March is a bit close for feature
freeze (at least for me, see below).
Things we planned to fix for 2.0 that still need love are, IMHO:
* general interface cleanup
* symbology
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 04/03/2013 11:37, Marco Hugentobler ha scritto:
For symbology migration from old to new one, I have good news: thanks to a
project
from Uster and Jena, I can implement data defined symbology settings for new
symbology. It is one of the few
Hi Marco,
On Mon, 04. Mar 2013 at 11:37:15 +0100, Marco Hugentobler wrote:
Disadvantage is that 15 March is too close for it to go into master. What
should we do (wait for 2.1 / shift feature freeze date / exception from
feature freeze) ?
How much time would you need? Moving the date to say
Hi,
I appreciate that a release plan is finally getting published and the
way for a shiny 2.0 is being paved.
I'm currently working on relation enhancements and nested forms for
related features. Unfortunately, this branch will not be ready by March
15, but I know, that there are some
On Mon, Mar 4, 2013 at 11:58 AM, Matthias Kuhn matthias.k...@gmx.ch wrote:
Hi,
I appreciate that a release plan is finally getting published and the way
for a shiny 2.0 is being paved.
I'm currently working on relation enhancements and nested forms for related
features. Unfortunately, this
I agree with Radim we need to start calling this much early then this. 2
or 3 months should be fine but I also think that we should have a more
planned out release time. This way people know it is coming +/- a month or
so.
- Nathan
On 4 Mar 2013 21:52, Radim Blazek radim.bla...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 04/03/2013 12:52, Radim Blazek ha scritto:
It seems that 2 weeks to finish all works won't be sufficient.
How about planning a 2.1 release shortly after June, where all this job could
fit in?
I know it's imposing an additional strain on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 04/03/2013 12:52, Radim Blazek ha scritto:
It seems that 2 weeks to finish all works won't be sufficient.
How about planning a 2.1 release shortly after June, where all this job could
fit in?
I know it's imposing an additional strain on the
Moving the date to say start of April wouldn't
hurt. Would that help?
Start of April would be ok for the data defined symbology.
Regards,
Marco
On 04.03.2013 11:44, Jürgen E. Fischer wrote:
Hi Marco,
On Mon, 04. Mar 2013 at 11:37:15 +0100, Marco Hugentobler wrote:
Disadvantage is that 15
Hi
On Mon, Mar 4, 2013 at 1:52 PM, Radim Blazek radim.bla...@gmail.com wrote:
On Mon, Mar 4, 2013 at 11:58 AM, Matthias Kuhn matthias.k...@gmx.ch wrote:
Hi,
I appreciate that a release plan is finally getting published and the way
for a shiny 2.0 is being paved.
I'm currently working on
Hi,
We have the (german speaking) FOSSGIS 2013 conference in Switzerland
from June 12 to 14 - would be kind of nice if we could announce QGIS 2.0
there (http://www.fossgis.de/konferenz/2013/).
I agree that data-defined symbology and raster improvements should be
finished. The relations
Hi,
On Mon, Mar 4, 2013 at 6:40 AM, Tim Sutton li...@linfiniti.com wrote:
Hi
On Mon, Mar 4, 2013 at 1:52 PM, Radim Blazek radim.bla...@gmail.com
wrote:
On Mon, Mar 4, 2013 at 11:58 AM, Matthias Kuhn matthias.k...@gmx.ch
wrote:
Hi,
I appreciate that a release plan is finally getting
On Mar 4, 2013 8:17 PM, Larry Shaffer lar...@dakotacarto.com wrote:
+1 for April 1 as a general feature freeze date, i.e. not for any
specific feature. I believe that's enough time to finish some of the
labeling features I've been wanting to focus on for 2.0. If someone could
help out with
On Tue, 5 Mar 2013 01:28:30 +0100
Martin Dobias wonder...@gmail.com wrote:
I would also like to finally remove old symbology - whether being fully
replaced by features in new symbology or not - otherwise we will need to
live the whole 2.x release cycle with old symbology.
But what about other
On 03/05/2013 08:06 AM, Alexander Bruy wrote:
On Tue, 5 Mar 2013 01:28:30 +0100
Martin Dobias wonder...@gmail.com wrote:
I would also like to finally remove old symbology - whether being fully
replaced by features in new symbology or not - otherwise we will need to
live the whole 2.x release
The new diagrams engine is solid, working better than the old one in all
the scenarios I've met. It's only weakness is that it doesn't play well
with the PAL engine.
M
On Tue, Mar 5, 2013 at 2:10 PM, Matthias Kuhn matthias.k...@gmx.ch wrote:
On 03/05/2013 08:06 AM, Alexander Bruy wrote:
On
2013/3/5 Matthias Kuhn matthias.k...@gmx.ch:
On 03/05/2013 08:06 AM, Alexander Bruy wrote:
Diagrams should be ready for 2.0. The code has been merged about half a year
ago.
Yes, I know. But old implementation also still available.
--
Alexander Bruy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 02/03/2013 22:15, Tim Sutton ha scritto:
I would like to get 2.0 release process rolling - I think all the key
features we were after have made their way into master and those that
haven't can probably wait for 2.1. Unless there is vigorous and
Dnia sobota, 2 marca 2013 o 22:15:41 Tim Sutton napisał(a):
Hi All
I would like to get 2.0 release process rolling - I think all the key
features we were after have made their way into master and those that
haven't can probably wait for 2.1. Unless there is vigorous and
widespread
Hi,
On Sun, Mar 3, 2013 at 2:58 AM, Borys Jurgiel li...@borysjurgiel.pl wrote:
Dnia sobota, 2 marca 2013 o 22:15:41 Tim Sutton napisał(a):
Hi All
I would like to get 2.0 release process rolling - I think all the key
features we were after have made their way into master and those that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 03/03/2013 11:33, Nathan Woodrow ha scritto:
add vector layer stuff is starting to really get out of hand. I would like
to use
the vertical tab idea and just have one dialog. I had bigger plans for the
dialog
but don't have time
* symbology migration to the new one
* labelling migration to the new one
related issues are here
http://hub.qgis.org/wiki/quantum-gis/Switching_from_Old_to_New_Symbology_and_Labeling
Would not be also great to fix issue that are known to cause crashes
or data corruption, but are not not
Paolo,
I had the idea of using the vertical list of icons on the left, one for
each provider, and having the current providers widget/dialog that opens
normally when you press the button docked on the right. This would mean
the UI is more consistent with the other dialog that follow this style
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 03/03/2013 13:58, Nathan Woodrow ha scritto:
Paolo,
I had the idea of using the vertical list of icons on the left, one for each
provider, and having the current providers widget/dialog that opens normally
when you
press the button docked
Hi All
I would like to get 2.0 release process rolling - I think all the key
features we were after have made their way into master and those that
haven't can probably wait for 2.1. Unless there is vigorous and
widespread objection, I propose that we embark on the following
release schedule:
15
32 matches
Mail list logo
