https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #17 from Jarosław Staniek ---
Yes, once we have the option you can depend on either breeze5-icons or
breeze5-icons-rcc. I guess for Linux you'll pick the former.
I would add these notes to the option's docs.
Thanks for the good chat, Wolfga
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #16 from Wolfgang Bauer ---
(In reply to Jarosław Staniek from comment #15)
> At run time, as I suggested the
> QIcon::setThemeName(QStringLiteral("breeze")) only declares a desire to use
> breeze, the only currently consistent theme. No way
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #15 from Jarosław Staniek ---
Yes for build time. So such option marked "for those who know what they are
doing" would be a good help indeed.
At run time, as I suggested the QIcon::setThemeName(QStringLiteral("breeze"))
only declares a des
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #14 from Wolfgang Bauer ---
(In reply to Fabian Vogt from comment #12)
> (In reply to Wolfgang Bauer from comment #8)
> > But of course that would also mean that kexi would then use the system's
> > icon theme. (via KIconTheme or QIcon, I su
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #13 from Jarosław Staniek ---
Yes, IIRC e.g. "table" icon was hi-color or gnome-like when some esoteric icon
theme is set.
For the record, while I remember now: major reason towards using the rcc system
came from the fact that it's resource
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #12 from Fabian Vogt ---
(In reply to Wolfgang Bauer from comment #8)
> But of course that would also mean that kexi would then use the system's
> icon theme. (via KIconTheme or QIcon, I suppose)
>
> TBH, I'm not sure how this is currently
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #11 from Jarosław Staniek ---
Currently we 're 100% sure that KEXI runs when we have access to
breeze-icons.rcc. So we do not have a situation when we mix e.g. GNOME and
Breeze icons in one GUI. In the future when we have more KEXI-compatibl
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #10 from Fabian Vogt ---
FWICT there's no effective difference between opening a breeze-icons.rcc from
the system during runtime vs. using the "breeze" icon theme if installed. So
using the Breeze system theme as fallback if the rcc file doe
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #9 from Jarosław Staniek ---
I've observed ugly fall back to hi color icons on XFCE for example :( So
depending on fall back will leave us with bug reports like "Apps look ugly, how
to bring consistent icons back" - something that is of wors
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #8 from Wolfgang Bauer ---
But of course that would also mean that kexi would then use the system's icon
theme. (via KIconTheme or QIcon, I suppose)
TBH, I'm not sure how this is currently handled...
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #7 from Wolfgang Bauer ---
(In reply to Jarosław Staniek from comment #6)
> > So maybe add a cmake option to build without the .rcc dependency
>
> Do you mean build-time dependency only? That would be possible to add
> because *you* on open
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #6 from Jarosław Staniek ---
> Well, it is not a warning, but an error.
Yes, the intent was such a verbose exit, which, for the branding reason at
least, we see as better choice.
> Currently, Kexi just quits if the .rcc is not installed, e
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #5 from Wolfgang Bauer ---
(In reply to Jarosław Staniek from comment #4)
> Thanks for the bigger picture Wolfgang. IIRC back when we lacked the
> build-time check we had situations when KEXI was distributed without the
> dependency. Would y
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #4 from Jarosław Staniek ---
Thanks for the bigger picture Wolfgang. IIRC back when we lacked the build-time
check we had situations when KEXI was distributed without the dependency. Would
you see a universal replacement technique to ensure
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #3 from Wolfgang Bauer ---
(In reply to Wolfgang Bauer from comment #2)
> Maybe it would be possible at least to have a way to build it without that
> dependency, perhaps by a cmake option?
Although, on second thought a cmake option might no
https://bugs.kde.org/show_bug.cgi?id=446731
--- Comment #2 from Wolfgang Bauer ---
That's all good and nice, but the problem still is that kexi depends on the
.rcc on buildtime and on runtime even on Linux/KDE where the icons should be
available by the breeze icon theme anyway.
Currently kexi ju
https://bugs.kde.org/show_bug.cgi?id=446731
Jarosław Staniek changed:
What|Removed |Added
CC||stan...@kde.org
--- Comment #1 from Jarosław
https://bugs.kde.org/show_bug.cgi?id=446731
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de
--
You are receiving this
18 matches
Mail list logo
