Sharing my experiences with Jasper Reports and iReport

[david]

This gives understandable a lot of report power where we as Servoy developers are not involved

I'll give you this one for simple reports a user can do and I think this is where Patrick's report builder app would fill the gap nicely.

My perspective of reporting is that almost always a developer is involved. Casting rtf fields to embedding fonts for pdf output to pulling in that one piece of data that is three relations away—iReport doesn't magically make this stuff easy anymore than Velocity.

Again, agreeing with Patrick. Don't get used to it

[lwjwillemsen]

Hi David,

My perspective of reporting is that almost always a developer is involved.

This one is indeed critical for us. Over the years in our firm the large number of reports that were build for our end-users by non-developers have proved
in our case :

Almost never a developer is involved in report design !

[ptalbot]

My perspective of reporting is that almost always a developer is involved.

This one is indeed critical for us. Over the years in our firm the large number of reports that were build for our end-users by non-developers have proved
in our case :

Almost never a developer is involved in report design !

This mean that you have dedicated report designer(s)... Knowing that there are very little specialized resources around in this field I'd though this is worse.
Think also how easily you would find good HTML designers as opposed to report designers and do the math.

[lwjwillemsen]

This mean that you have dedicated report designer(s)...

No, we don't have... We gave colleagues (with no reporting experience other then our own legacy foxpro very limited text style reporting) a short course in jasper design, sql queries and our data model and off we went.
Some of those colleagues were also trained in writing xsl stylesheets for import and export data purposes.

Regards,