Though posted on, XSettings is actually a Gnome/GTK+
standard without concensus.
Qt, KDE, and all the others to my best knowledge don't support this.
This is yet another example of Gnome pushes others to use its standard
and call their technology "cross-desktop" solution.
LXDE, which is based on gtk+, of course uses XSettings, but this only
works for gtk+ apps.
At least I solved the XCursor problem in a more desktop independent
way so I hope that we can solve the font one in the similar manner.
Actually, when I'm planning LXAppearance, I wanted to write some
config values to qtconfig to make it more cross-desktop but later I
found this very difficult. Any better idea?

On Sat, Mar 12, 2011 at 7:30 PM, Julien Lavergne <> wrote:
> Le samedi 12 mars 2011 à 16:35 +0800, PCMan a écrit :
>> I did a quick review and found a problem in lxappearance.
>> The Xft antialias stuff is not as easy as it looks like.
>> See this page:
>> There is no common standard for this and things are totally in a mess.
>> The most cross-toolkit and cross-desktop way seems to be using Xrm.
>> Since gtk+ uses cairo, it might support Xrm, too.
>> But using gtkrc and XSettings can get the config dynamically applied
>> in gtk+ applications.
>> I'm not sure if Xrm works for Qt4. IIRC Qt4 doesn't use Xft.
>> Anyway, if possible I don't want to do it in a gtk+ specific way.
>> Any thoughts or comments?
> Is XSettings not supposed to be a standard way to interact with this
> settings ? I think it will be easier (at least, for the short term) to
> stay with XSettings, as many parts of lxappearance use this.
> Regards,
> Julien Lavergne

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to