On September 30th, 2010, 1:10 p.m., Marco Martin wrote:

still not completely happy having to keep a separate xml dom, however, there are probably not going to be other ways for a while and the implementation seems pretty good, so modulo those little things it could go in

If QXmlStreamReader::parse() would be virtual, we could create a stream reader, that replaces this on the fly. But for now I see no other way of doing this. The only idea that could work is: Create a QIODevice that reads from another QIODevice with help of QXmlStreamReader and writes the data again with QXmlStreamWriter... But this would be much more code and I don't think that this would be faster at all.

On September 30th, 2010, 1:10 p.m., Marco Martin wrote:

/trunk/KDE/kdelibs/plasma/svg.cpp (Diff revision 1)
		bool SharedSvgRenderer::load(const QByteArray &contents, const QString &styleSheet)
		103	QDomElement colorScheme = svg.createElement("style");

a check elements with the same id aren't existing should be done

You are right. But this would add more clutter. Maybe it is better to just leave the id as is. So no hint-uses-color-scheme but only current-color-scheme.

On September 30th, 2010, 1:10 p.m., Marco Martin wrote:

/trunk/KDE/kdelibs/plasma/svg.cpp (Diff revision 1)
class SvgPrivate
385	applyColors = elementRect("hint-apply-color-scheme").isValid();	437	if (elementRect("hint-apply-color-scheme").isValid()) {

so the coloring of the pixmap is still kept as retrocompatibility?

I don't want to break existing themes ;)

On September 30th, 2010, 1:10 p.m., Marco Martin wrote:

/trunk/KDE/kdelibs/plasma/theme.cpp (Diff revision 1)
void ThemePrivate::colorsChanged()
		320	if(stylesheet.isEmpty()) {

i wonder how much is the benefit vs cost of caching this?

Both is quite low. ;) But as this stylesheet has to be generated for every Plasma::Svg object, which is 259 times for a start of plasma with the default setup + analog clock + calculator, it feels wrong to regenerate it that often.

On September 30th, 2010, 1:10 p.m., Marco Martin wrote:

/trunk/KDE/kdelibs/plasma/theme.cpp (Diff revision 1)
KSharedConfigPtr Theme::colorScheme() const
		785	case ButtonHoverColor:

the button widget should be modified if this will start to be used

For what reason?

- Manuel

On September 30th, 2010, 11:41 a.m., Manuel Mommertz wrote:

With this patch applied SVGs can put a style-element with id 'current-system-colors' in it, which gets replaced by a style with the current systemcolors. This allows SVGs to use colors like background color and text color from the system palette. Giving themes much more possibilitys then just coloring the resulting pixmap.

Changing theme, changing colorscheme