On Thursday, March 21, 2013 00:00:52 you wrote: > PlasmaCore.SvgItem { > svg: Svg("nocover") > }
yes, or Svg { source: "nocover" } > This seems to work, in that it finds content/images/nocover.svgz as > expected. However, the effect is exactly the same as my original code, > which was > > PlasmaCore.SvgItem { > svg: plasmoid.file("images/nocover.svgz") > } not really the same; this will never fallback to the theme > In other words, it does not allow the theme to override it (instead, the > theme is the *fallback* for it). So it does not solve the problem of > how a plasmoid can provide a default image but allow it to be themed. that is quite true. *thinks* i have a solution for this, though it will require patching ThemeSvg (which is private, so no major problems there)... would it be acceptable to you if we had a images/themed/ directory where you could put such SVGs which would be the fallback to the theme? this would give us the following search path: $PLASMOID_PACKAGE/images/<name> $SYSTEM_SVG_THEME_PATH/<name> $PLASMOID_PACKAGE/images/themed<name> this could get tripped up if the file path is "themed/myimage.svg" but that seems like a stretch .. we could have a completely different directory, such as "theme/" .. hell, we could even go completely crazy and allow having per-theme SVGs in there even, e.g. a search path of: $PLASMOID_PACKAGE/images/<file> $SYSTEM_SVG_THEME_PATH/<file> $PLASMOID_PACKAGE/theme/$SYSTEM_SVG_THEME_NAME/<file> $PLASMOID_PACKAGE/theme/<file> thoughts? (this would all be very, very easy to add to ThemedSvg ..) p.s. re-adding the plasma-devel list .. apparently i didn't "reply all" at some point and this discussed veered off-list. -- Aaron J. Seigo
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel