Alister,

I just wanted to stress the point that I think a report could be any printable presentation of data (dynamical data e.g. from a layer and "fixed" data e.g. a legal statement or a company's logo). Thus every report will probably be unique and specially made for certain data in a certain use case. Having said that a reporting software that can be used by many users has some kind of a WYSIWYG report designer.

If we want to stay within QGIS the composer would be the tool where I would see the report; one can accomodate images, texts, maps, graphical elements etc. in there. What the composer lacks is a multipage layout and a way of replacing placeholders in a template with real data during run time (that is not to say the composer is bad as it is now, just stating what IMHO it is missing to make it a reporting utility). So a report would not be an element that one can add to a composer layout but the composer layout itself would be the report and created combining data and a template during run time.

You are right, JasperReports is Java based. I am not a programmer and I do not have any clue about the pros and cons of Java except from a user's perspective. I am only interested in having working tools for my users and JasperReports together with PyJasper [1] was working for me. In our setting the report generator itself is not running on the client but on a server, a QGIS python plugin is sending the data together with a report template to the server.

[1] https://github.com/hudora/pyJasper

all the best

Bernhard

Am 03.12.2011 01:06, schrieb Alister Hood:
Yes, I didn't mean that the report should _be_ data in a table.  Just that it should be 
put in the "Layers" list, and it should be possible to add it to a composer 
layout.

But I now realise if a report only applies to one layer it doesn't make sense 
to put it in the Layers list.  The report would be another way of displaying 
information about the layer (just like you can display the layer features on 
the map, or view the attribute table).  It should therefore be accessible in a 
similar way to the attribute table.  And it should be possible to add it to a 
composer layout.

N.B. JasperReports is Java based.  QGIS is very unlikely to add Java as a 
dependency (at least I hope so ;))
If I remember correctly, people were having difficulty finding a report 
generator suitable to use in QGIS.  I wonder if there are any that are 
javascript based.  Perhaps that might be an option - Tim is doing some work 
with Javascript in QGIS.

Date: Fri, 02 Dec 2011 10:19:27 +0100
From: Bernhard Str?bl<[email protected]>
Subject: Re: [Qgis-developer] Re: Excel Export from QGIS
To: [email protected]
Message-ID:<[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

IMHO a report should be more than presenting data in a table. A report
presents features' data in a readable way e.g. in a table but also in
some kind of text and could include a map or an image of the feature.

A free report generator is JasperReports http://jasperforge.org/

Bernhard

Am 02.12.2011 09:52, schrieb Alister Hood:
I seem to remember some previous discussions about a report generator.

I don't think it would replace the improvements I mentioned, if that's what you 
mean.
Also, note that the need to print attribute tables across multiple pages is 
very similar to the need to produce maps spread across multiple pages, so it 
might be good to implement it along with the long-desired mapbook generator.

Alister

-----Original Message-----
From: Alexander Bruy [mailto:[email protected]]
Sent: Friday, 2 December 2011 9:27 p.m.
To: Alister Hood
Cc: Bob and Deb; [email protected]
Subject: Re: [Qgis-developer] Re: Excel Export from QGIS

Hi all,

maybe it's better to integrate into QGIS report generator? Composer
is a nice feature but it don't allow to create advanced reports.
Something like FastReports [0], NCReport [1] or CrystalReports
will be great adition (I know, this solutions are commercial but this
is just example).

[0] http://www.fast-report.com
[1] http://www.nocisoft.com/

--
Alexander Bruy


________ Information from NOD32 ________
This message was checked by NOD32 Antivirus System for Linux Mail Server.
http://www.nod32.com





________ Information from NOD32 ________
This message was checked by NOD32 Antivirus System for Linux Mail Server.
http://www.nod32.com
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to