GSOC ReportBuilder Weekly Update

[Adam Seskunas]

Hello all,

Just a quick weekly update on implementing ReportBuilder in C++.

Last week I set out to write a very basic xslt filter that could handle
some straight lines in a report. As this was the first time I had written
an xslt filter and there was some work needed to get everything set up(file
locations, python scripts to get input/output, python scripts to automate
zipping/unzipping odt files, etc.) it took most of the week. The filter
works and it was a good exercise as some of the work will be used later.

During my weekly meeting with my mentors, there was much discussion about
what exactly is the input for the xslt filter is and what is the output.
The goal of the project is to remove the Pentaho Report Engine and the
companion Java code from the LibreOffice codebase and we wanted to make
sure that the Pentaho engine was not touching the input for the would be
xslt filter. It was decided that I should take some time to make sure and
to really nail down the what the input and output would be.

Which led to my realization, while debugging the ReportBuilder that I have
had the input and output reversed. In some ways, this makes things
potentially easier, but also adds some new challenges. It also solves some
lingering questions I had about how the ReportBuilder functions, which is a
positive development.

So now my next steps have changed from working on the xslt filter, to
adapting the existing C++ to place the database data into the input xml. I
will start to look at how this will be done in detail the rest of the week
with the hope that it can be implemented in the next two weeks.

That's it for now, thanks for reading,
Adam  Seskunas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice/attachments/20250520/847289c1/attachment.htm>