Hi All,

Earlier I think will use LazReport for my new project. Implemented Child feature for my needs but now see many other lack of features, problems, reported bugs.

Features for example...
- Page, Band not have Frames and FillColor properties
- FillColor not have (Brush.Style) property
- Stretched not working with Line
- Frames not have Color, Style, Width properties/side
- Keep together feature for Band (e.g. Parent and Child(s))
- In Designer Text object not resized when Font changed
- On Preview can scroll below the page
- On Preview Find highlight the whole text of view and only the first occurence
- Barcode not have Font property

Reported bugs for example...
http://bugs.freepascal.org/view.php?id=19996
http://bugs.freepascal.org/view.php?id=26263

How easy or hard or impossible to implement the above features into LazReport? In the main source not in a fork. Seeing the above features from LazReport POV better for me if create a report engine from scratch which fit my needs? Opinions?

Gabor

Just an opinion:
I am working with Graeme Geldenhuys to create a reporting engine from scratch. I think Lazreport's design contains some fundamental flaws, which can only be remedied by re-implementing a reporting engine from scratch.

Michael.

On Thu, Jul 9, 2015 at 4:45 PM, Michael Van Canneyt wrote:
[...]

I think Lazreport's design contains some fundamental flaws, which can only be remedied by re-implementing a reporting engine from scratch.

This is a very good new! I smell TFPReport in the air... =)

Right on :-)

Michael.

Il 09.07.2015 21:45, Michael Van Canneyt ha scritto:

That's great :)

I hope that direct exports to PDF and LibreOffice (.odt and .ods) or eventually M$ Office (.docx and .xlsx) will be available on all platforms... :)

The primary save format will be JSON, which can be converted to anything you want. We're not making any assumptions about the final output. The structure will be such that adding exports should not be a problem. We have at least PDF planned, for use in Web applications.

In fact, FPC's TTF/PDF support is being worked on as I write this.

Michael.

Op 10-07-15 om 09:36 schreef Michael Van Canneyt:

The primary save format will be JSON, which can be converted to anything you want.

I don't know much about JSON, but I'm about to start an application that writes to a label-printer (= small paper-sizes). Would it be possible to generate output for that, without manual intermediate steps ?

Koenraad.

Well - good luck - Lazreport took a long time to get stable and certainly contains many idiosyncrasies that could benefit from a redesign. But please ensure that there is a clear migration path to any new reporting engine.

Tony Whyman
MWA

Tony Whyman wrote

Well - good luck - Lazreport took a long time to get stable and certainly contains many idiosyncrasies that could benefit from a redesign. But please ensure that there is a clear migration path to any new reporting engine.

Well. The reporting engine is developed using test-driven development, so it should hopefully not take so long to be stable. This is possible because all GUI dependencies have been removed from the core engine.

Concerning migration path: It will surely be possible to write some form of .lrf file converter, but I will not compromise on design to make this possible.

Michael.

I don't see why not.

Michael.

The primary save format will be JSON, which can be converted to anything > you want.

How?? Is there some utility that does that?? Or do I misunderstand what you meant? Also, will users still be able to design their own reports like they can with LazReport? Thanks.
Bob B.

On Friday, July 10, 2015 1:20 AM, Michael Van Canneyt wrote:

I don't see why not.

Michael.

Bob B. wrote

> The primary save format will be JSON, which can be converted to anything > you want. How?? Is there some utility that does that?? Or do I misunderstand what you meant?

The finished report can be saved to JSON file.
It can be rendered to a printer canvas.
But you can also make a utility that prints this file to a label-printer.

Also, will users still be able to design their own reports like they can with LazReport?

Yes, obviously.

Michael.

Hi All,

2015. 07. 09. 21:45 keltezéssel, Michael Van Canneyt írta:

Two years gone. Any news? I see "In progress" on the Foundation's page, but want to know more detailed informations.

https://foundation.freepascal.org/projects/reporting-engine

Gabor

It's ready and waiting for release. I'm waiting for 2 small fixes still:
- Some strange error when exporting a custom element to PDF
- Removing a dependency on freetype.dll on windows.

Michael.

Hi,

pls, where can the actual 'unstable ?' Code found ? fpc trunk, where ?

Thanks
Andreas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20170811/3adcec64/attachment.html>

Hi,

I will commit the code to FPC svn the coming week.

Michael.

.... and the week goes by :-)

Any news about the report-engine ? Or had i miss this in the (fpc) trunk ?

Andreas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20170819/15444a7f/attachment.html>

Andreas Frieß wrote

.... and the week goes by :-)

It's not yet over.

Any news about the report-engine ? Or had i miss this in the (fpc) trunk ?

No, it is planned for tomorrow. I have other things on my plate as well :)

Michael.

hi,
maybe the code could be released with these two bugs? at least the community could see the code and start assessing the scenarios in which the code could be used.
and also given the code maybe somebody can help with the fixes.

thank you,
tudor hulban

Tudor Hulban wrote

and also given the code maybe somebody can help with the fixes.

I've already found the cause of the problem exporting custom elements to PDF. Not many will hit the error anyway, either way I'll correctly implement a fix tomorrow and post a patch to Mantis.

Regards,
Graeme

Tudor Hulban wrote

maybe the code could be released with these two bugs?

ps:
In case you didn't see the announcement, the fpReport code was released today.

Regards,
Graeme