<div class="gmail_quote">On Mon, Mar 26, 2012 at 2:43 PM, Vincent Untz <span dir="ltr"><<a href="mailto:vuntz@gnome.org">vuntz@gnome.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Le lundi 26 mars 2012, à 13:36 +0100, Jerome Leclanche a écrit :<br> <div class="im">> On Mon, Mar 26, 2012 at 1:33 PM, Vincent Untz <<a href="mailto:vuntz@gnome.org">vuntz@gnome.org</a>> wrote:<br> ><br> > > Le dimanche 25 mars 2012, à 21:47 +0100, Jerome Leclanche a écrit :<br> > > > Hi lists<br> > > ><br> > > > Followup on my previous post, this is my submission for a spec that<br> > > stores<br> > > > default and fallback Icon, Cursor and Sound theme with the possibility of<br> > > > adding more themes or metadata to it.<br> > > ><br> > > ><br> > > <a href="https://docs.google.com/document/d/1Slqk1yTFsiTBS0P8EnDcqp5G7sGmJ8SW7iQTdw7NUTs/edit" target="_blank">https://docs.google.com/document/d/1Slqk1yTFsiTBS0P8EnDcqp5G7sGmJ8SW7iQTdw7NUTs/edit</a><br> > > ><br> > > > I'm looking for more comments and would like to eventually get the<br> > > process<br> > > > started on submitting it.<br> > ><br> > > It's unclear to me what's the exact goal of this spec: is it intended to<br> > > be used by theme authors as a hint for desktop environments? Or is it<br> > > intended to be used by desktop environments to store the theme<br> > > preferences of the user?<br> ><br> </div><div class="im">> The latter. It's currently impossible to get/set default themes (unless you<br> > do it on an environment-per-environment basis), the spec solves that.<br> <br> </div>I would think that the right way to get the themes would be through<br> xsettings:<br> <br> <a href="http://specifications.freedesktop.org/xsettings-spec/xsettings-latest.html" target="_blank">http://specifications.freedesktop.org/xsettings-spec/xsettings-latest.html</a><br> <a href="http://www.freedesktop.org/wiki/Specifications/XSettingsRegistry" target="_blank">http://www.freedesktop.org/wiki/Specifications/XSettingsRegistry</a><br> <br> (more settings could be added to the registry, if needed)<br> <br> As for setting the theme, don't all environments provide a tool to<br> change the theme? Is your proposed spec intented to allow creating<br> third-party tools, or to script changing the theme?<br> <div class="HOEnZb"><div class="h5"><br> Thanks,<br> <br> Vincent<br> <br> --<br> Les gens heureux ne sont pas pressés.<br> _______________________________________________<br> xdg mailing list<br> <a href="mailto:xdg@lists.freedesktop.org">xdg@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/xdg" target="_blank">http://lists.freedesktop.org/mailman/listinfo/xdg</a><br> </div></div></blockquote></div><br><div><br></div><div>The issue is not just changing the theme, it's also getting it. This is an issue for libraries that provide tools to get file paths for a theme action (in this case, Qt's QIcon.fromTheme: <a href="http://qt-project.org/doc/qt-4.8/qicon.html#fromTheme">http://qt-project.org/doc/qt-4.8/qicon.html#fromTheme</a>). And while it's true DEs provide custom ways to change the local theme, someone may wish to create a cross-platform cross-desktop one.</div> <div><br></div><div>J. Leclanche</div>