https://bugs.kde.org/show_bug.cgi?id=420774
Jarosław Staniek <stan...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from Jarosław Staniek <stan...@kde.org> ---
Yes I agree. I see a few things:
1. KReport can be used without QWidgets, in this case we may need to split to
the core and the QWidget-based (like I did in KProperty). In this case any
error message would be abstracted to allow passing it to a non-QWidget APIs.
2. KReport can be used without designing - just the renderer, in this case we
may need to split to the rendering core and the rest. In this case any error
message would be abstracted to allow passing it to a non-QWidget APIs or
suppressing.
3. In the case 1 the icon resource would be needed if any icon from there is
used by the non-QWidget app for any needs.
If you ask for abstraction of messages, there is
https://api.kde.org/frameworks/kcoreaddons/html/namespaceKMessage.html in KF5
but it's up to maintainers to use it or offer any abstraction.
--
You are receiving this mail because:
You are watching all bug changes.
