Date: Mon, 28 Feb 2005 11:06:31 +0300 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Jeremy Messenger <mezz7@cox.net> Cc: freebsd-gnome@freebsd.org Subject: Re: How does GNOME 2.9.x in MarcusCom treats you so far? Message-ID: <1109577991.7823.21.camel@localhost> In-Reply-To: <opsmvqogjk9aq2h7@mezz.mezzweb.com> References: <opsmr0hvtp9aq2h7@mezz.mezzweb.com> <opsmtidaa29aq2h7@mezz.mezzweb.com> <opsmtmltx19aq2h7@mezz.mezzweb.com> <opsmunkkey9aq2h7@mezz.mezzweb.com> <1109545591.1537.2.camel@localhost> <opsmvqogjk9aq2h7@mezz.mezzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=F7 =D7=D3, 27/02/2005 =D7 17:39 -0600, Jeremy Messenger =D0=C9=DB=C5=D4: ...cut... >>> After the more check up with marcus, we agree that there is no way for = =20 >>> us >>> can do with that. There are a lot of icons that aren't working, because= =20 >>> of >>> GNOME is not in KDE's theme. For example, kmail is in Locolor, =20 >>> crystalsvg, >>> kdeclassic and slick that GNOME doesn't have. Anything images that are = =20 >>> in >>> hicolor or the root of the icons directory will working fine. For =20 >>> example, >>> kturtle and quanta work fine because their images are in hicolor. >> >> Why hicolor ? > >Because, it's part of freedesktop standard. oops, things even worse in KDE, to get full set of icons, you need join hicolor and default.kde I've write simple script to populate hicolor directory from default.kde, but of course it is hack, and things should be cured at KDE side. >The fall back is to hicolor. > >Cheers, >Mezz --=20 Vladimir B. Grebenchikov vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1109577991.7823.21.camel>