Hi all,
We are in the final stretch for the next version of LizMap, a plugin and
a web client to publish QGIS projects as web maps based on QGIS-Server.
In this new version, we added new features :
* Geolocation Control
* Measure tools
* OpenStreetMap search via Nominatim
* A simple print
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
HI
I am in the process of compiling Quantum GIS using mingw on win7.
I had a few hiccups, that i could overcome, but i am stuck with the
following error and dont know how to sort it out. I need some help please.
[ 46%] Building CXX object
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
On Fri, Mar 1, 2013 at 8:36 AM, Denis Rouzaud denis.rouz...@gmail.com wrote:
On 03/01/2013 08:29 AM, Martin Dobias wrote:
On Fri, Mar 1, 2013 at 7:50 AM, Denis Rouzaud denis.rouz...@gmail.com
wrote:
Hi Martin,
I got this error when I compile this morning.
http://pastebin.com/v0WPVbj7
Hi Martin,
Thanks for your reply, everything's fine now.
Greetings,
Denis
On 03/04/2013 01:24 PM, Martin Dobias wrote:
On Fri, Mar 1, 2013 at 8:36 AM, Denis Rouzaud denis.rouz...@gmail.com wrote:
On 03/01/2013 08:29 AM, Martin Dobias wrote:
On Fri, Mar 1, 2013 at 7:50 AM, Denis Rouzaud
On Mon, Mar 4, 2013 at 7:07 AM, Mathieu Pellerin nirvn.a...@gmail.com wrote:
Playing around with it, I was wondering whether - for the sake of offering a
better user experience - the import topology from XML and export topology to
spatialite should be merged into one action. Realistically, my
In qgsrasterpipe.h line 32 - 34 the code look tlike this.
/#ifdef _MSC_VER
#undef interface
#endif/
I have commented the #ifdef and #endif out so that #undef interface is
executed.
Now it compiles further.
--
View this message in context:
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
I am curious, why *#undef interface* ?
On Mon, Mar 4, 2013 at 3:33 PM, theunsgis theunsheydenr...@gmail.comwrote:
In qgsrasterpipe.h line 32 - 34 the code look tlike this.
/#ifdef _MSC_VER
#undef interface
#endif/
I have commented the #ifdef and #endif out so that #undef interface is
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
Andreas,
So I appreciate the parts you describe,
but maybe there is another pair of hands, who maybe able to complete a
component of some value. The contributor may be able to describe their own
milestone.
The offer stands in that case, albeit minor.
cheers
/
a development effort of approx.
Hi Benjamin,
Thank you for your interest in the project.
I was looking at a problem today and thought of your mail to the list.
In case you still would like to contribute to QGIS with a task
concerning parallelisation, I would have a place, where I can imagine a
true benefit of this.
QGIS
On Mar 4, 2013 11:38 PM, Matthias Kuhn matthias.k...@gmx.ch wrote:
Hi Benjamin,
Thank you for your interest in the project.
I was looking at a problem today and thought of your mail to the list.
In case you still would like to contribute to QGIS with a task concerning
parallelisation, I
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
27 matches
Mail list logo
