So far KReport scripts are either:
- code snippets embeded in report elements (if their context are elements), such as event handlers or expressions such as "=x+y"
- definitions placed outside of the report and provided in an application-dependent way (Kexi) via a "map - (name, scriptText) pairs" API
We would like to design XML element(s) that list global (report-level) scripts by name and definition.
Outcome:
- report can be still a self-contained file, this way easier to import/export/transfer
- global script defined by the KREPORT format eventually - one app-defined thing less is good for the quality of the format
- from Kexi's perspective this change would probably mean less code in Kexi, more in KReport (not sure)