https://invent.kde.org/libraries/kreport/-/issues/19

https://invent.kde.org/libraries/kreport/-/issues/17

https://invent.kde.org/libraries/kreport/-/issues/16

https://invent.kde.org/libraries/kreport/-/issues/13

https://invent.kde.org/libraries/kreport/-/issues/12

https://invent.kde.org/libraries/kreport/-/issues/11

https://invent.kde.org/office/kexi/-/issues/80

The JS engine isn't suitable; instead develop powerful Python bindings like Krita or Blender.

https://invent.kde.org/office/kexi/-/issues/79

https://invent.kde.org/libraries/kreport/-/issues/2

https://invent.kde.org/office/kexi/-/issues/78

https://invent.kde.org/office/kexi/-/issues/42

README is there already

https://invent.kde.org/office/kexi/-/issues/72

Extended to cmake as well
https://invent.kde.org/libraries/kproperty/-/issues/1
https://invent.kde.org/libraries/kreport/-/issues/1

Probably will be invalid once we deprecate JS scripts. But the concept will be useful for Python scripts at some point.

Fixed already probably

Once we have stable Python support JS shall be obsolete in favor of Python.

Done in the Invent

Respective merge requests are created now here:
https://invent.kde.org/libraries/kdb/-/merge_requests/1
https://invent.kde.org/libraries/kproperty/-/merge_requests/1
https://invent.kde.org/libraries/kreport/-/merge_requests/1

Great, thanks Friedrich.

@staniek Ah, missed your reply, somehow phabricator did not send me a noticiation.

Hi Freidrich. That's a good news to me!

Hi @staniek . While I am currently doing some work to keep api.kde.org alive and cleaning up legacy docs where possible, I remembered this task and would be available to complete it these days :)

In D28809#655086, @piggz wrote:

Amazing to have someone using my work, can I ask what app you are using it in?

Updated required version of ECM to use ECMSetupQtPluginMacroNames. It is now
based on master (3.3) instead of the 3.2 branch

Nice, but question, would it be possible to use ecm_setup_qtplugin_macro_names() ? https://api.kde.org/ecm/module/ECMSetupQtPluginMacroNames.html

Amazing to have someone using my work, can I ask what app you are using it in?

In D28809#652567, @jfita wrote:

In D28809#652442, @staniek wrote:

BTW, while creating reviews please add at least me and KReport maintainer Adam as reviewers. Thanks!

Sorry about that. I misunderstood the instructions at the community wiki to mean that it would be done automatically.

I will keep it in mind next time.

In D28809#652442, @staniek wrote:

BTW, while creating reviews please add at least me and KReport maintainer Adam as reviewers. Thanks!

Improve wording, remove use of QLatinString/QStringLiteral, and make code follow conventions better

BTW, while creating reviews please add at least me and KReport maintainer Adam as reviewers. Thanks!

Good job, some notes added.

Fix wording, and remove improper use of auto and pointer validity according to coding style

Reviewed until line 475.

In D28809#649963, @jfita wrote:

Updated text according to Jarosław’s notes

Thanks, reviewed first 200 lines. Good job!

Very nice, I will review this.

BTW @jfita, I propose adding the following line to the description, to help us creating change logs:

Good job!

Good job, thanks!

Landed in 3.2.

In D28736#645582, @staniek wrote:

If we want it in the stable 3.2 release, it needs to land in the 3.2 branch.

If we want it in the stable 3.2 release, it needs to land in the 3.2 branch.

Thanks!

LGTM

note that I can already push patches on my own

Thanks for the approval -- note that I can already push patches on my own ;-)

You can apply it also to a stable branch, because, if I'm not mistaken, the change only removes translations. Removing translated strings is not a problem.

(landed to master (3.2) as translations are affected)

Thanks a lot @pino. Looks nice, in some regards even more in line with LibreOffice (US Letter -> Letter).

Note to ourselves: forgot to include it in 3.1 beta so it goes to the next minor version.

In D9941#193148, @staniek wrote:

• GIT_SILENT dataSourceProperty()->setValue -> setItemDataSource
• Remove unnecessary and unused support of static text with $ prefix
• GIT_SILENT Update API for source and format
• GIT_SILENT For docs for loadFromFile

• GIT_SILENT dataSourceProperty()->setValue -> setItemDataSource
• Remove unnecessary and unused support of static text with $ prefix
• GIT_SILENT Update API for source and format
• GIT_SILENT For docs for loadFromFile

Regarding lat/long/zoom, does the map element show you the map for statically provided values (i.e. when is data source is empty)?

Thanks for the reminder Adam.

eg, field datasource can contain =<Complex js > or $<literal string>

I see, do you remember what was the actual rule?