[Qgis-developer] Reporting engine

2014-01-07 Thread Andreas Neumann
Hi,

I am starting a new thread on the reporting engine. As it generates a
lot of interest and the content is not related to attribute tables
anymore ...

I think it would be good to schedule a meeting at the next Hackfest in
Vienna.

Meanwhile it would be good to find out if the existing C++/QT based
solutions could be used from a licensing and from a technical point of
view. We could also start collecting requirements in a wiki. Or if it
may be wiser to write something from scratch based on our existing API
and the current Atlas functionality.

The question with the separate tools and libraries is if they could be
well integarted. Ideally the GUI would be in separate panels and
toolbars inside the QGIS print composer and not with a separate tool or
window.

Could someone open a wiki page for collecting the requirements and facts
about existing reporting tools? I am not too familiar with the new QGIS
infrastructure yet - just read you are migrating the content currently.

Thanks, Alex, for listing the C++ based options! Its a good start.

I had a very quick look on some of them. OpenRPT is GPL, which is nice,
but last update at Sourceforge from 2011 - not so nice. Or is QtRPT the
followup project?

Exaro does not show a lot of activity - last update 2009? Same for
FreeReport (last update 2002). I have severe doubts if a project hadn't
been updated for more thant tow years

NCReports seems to be quite powerful and advanced but I have doubts
about the license. Something to find out/negotiate.

Thanks,
Andreas






___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] Reporting engine

2014-01-07 Thread Paolo Cavallini
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Il 07/01/2014 13:44, Andreas Neumann ha scritto:

 Could someone open a wiki page for collecting the requirements and facts
 about existing reporting tools? I am not too familiar with the new QGIS
 infrastructure yet - just read you are migrating the content currently.
 
 Thanks, Alex, for listing the C++ based options! Its a good start.


What about python-reportlab? A C++ implementation is not an absolute necessity.
All the best.

- -- 
Paolo Cavallini - www.faunalia.eu
Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlLMAiYACgkQ/NedwLUzIr4iDQCdEzrbjTRIwbSrqLlx/psvCEia
T+MAn33PkeawiKaNArMyjXmzVTTkU/ir
=9xHQ
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] Reporting engine

2014-01-07 Thread Andreas Neumann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


 What about python-reportlab? A C++ implementation is not an
 absolute necessity.

Yes - this looks interesting. More active, more features and BSD
license. Part of the libraries (e.g. XML parser) is GPL.

Something we should examine more closely.

Andreas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSzAzwAAoJELiCsGDopvBCiZ8H/1ACdgHMnHdQ++7ZLhhwNwsw
w4BpmtL3xe3EOjuZpfr9r/f6xtFymFqn7/Vjpqlpa7bEgiFDmF4YyoMmUnfTnsm2
jDDZRJnl7VMxv2/B9hvcwTZ+jYiOsJVQBqwKF5RPXQcvq8R7F8epg2neKi2FbIXo
l+SnRU1owZqyWZ8LfVuIi9TBKHEqt+OpbF4/bTCwQ8k0SE13WJW8HRsRiHZlOe7Q
eZi8iK4kZRmP5mJ41vy28rXwDbDfRV50vXslXdneRbRvWP6UMx4Ae1pYeaF7kJyX
1a10t3htFaSbn/U65aUkgW/Lw+eTSSL2TQ12PKFo7P/R91xVS10qe5FTaf3xNeA=
=W5EL
-END PGP SIGNATURE-
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer