On 08/12/2014 11:34 PM, Àlex Fiestas wrote:
On Monday 11 August 2014 12:51:21 Milian Wolff wrote:
a) what's the advantage of having a native widget style, compared to using
QtCurve settings? Are there things missing / not implementable in QtCurve?
We did some rought tests and QtCurve was waaaay slower than Oxygen (that at
the same time was slower than Fusion).
The test we did was re-painting widgets over and over with different styles and
then measuring instructions and time iirc.
Cheerz.
Hi Alex,
many thanks for doing this test (glad to hear that oxygen is not the
biggest beast around :))
Now, to be honest, I'm not sure how 'relevant' the test is, and the
outcome might well be very GPU related.
Oxygen, unlike QtCurve, uses a lot of QPixmap all over the place for
rendering and caching, which is known to be quite expensive on some
GPUs, and not at all on others.
Also, for the comparison to fusion, oxygen has tons of animations, which
causes several (as opposed to one) localized repaints for basically each
user interaction, and this will cost, naturally. (not sure what's the
status of QtCurve with that respect).
In any case, I'd also be curious to see the outcome for the current
breeze code (kde:scratch/hpereiradacosta/breeze), for which the
rendering is supposedly much simpler than oxygen, and no caching is
used. (but animations are there)
Best,
Hugo
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
