On 19.02.2014 15:46, Carsten Haitzler (The Rasterman) wrote:
> On Wed, 19 Feb 2014 12:38:53 +0900 Florian Schaefer <list...@netego.de> said:
>
>> OK, I think I figured out part of the mystery: My E is installed to
>> /opt/e. Hence also the efreet dbus service files finished up in this
>> location and my dbus was, of course, not picking up those files. Now
>> I've symlinked them to a proper location, E can talk with Efreet, icon
>> themes show up and most of my icons are back.
>
> OOOOOOOOOOOOOOOOOOOOOOOOOOOOOH! aha!
I felt something similar. :-)
>> If we are already given big big warnings about disabling stuff like
>> physics during configuration time, how about adding a warning when
>> putting custom installation prefixes that it is essential that those
>> dbus service files need to be taken care of?
>
> yes. good point. i'll stuff a warning bonanza in about this.
Thanks.
>> Still, for programs like firefox, thunderwirds, wicd, my icons are
>> missing. Can it be that E is giving precedence to SVG files even though
>> I do not have svg support in E?
>
> wtf? no svg support! fredesktop.org icon specs make that a requirement... from
> memory
Well, the FDO spec says, quote, "Support for SVGs is optional.". Anyway,
if for E the handling is like this then support for SVG should not be in
an optional evas_generic_loaders package, but in a mandatory
requirement. Better yet, make it a part of Evas or E, as without it the
WM is pretty much useless ... in contrast to having a physics engine
installed ... sorry, I have to dwell on that point a bit more. ;-)
Florian
>> On 19.02.2014 09:07, Florian Schaefer wrote:
>>> Hello David!
>>>
>>> On 18.02.2014 21:15, David Seikel wrote:
>>> [...]
>>>>> I agree, that could be at it's heart. So now the question is how to
>>>>> make E recognize my icon theme. Is there some file in which the
>>>>> available themes are listed? Or according to which kind of black
>>>>> magic is that determined?
>>>>
>>>> The FreeDestop.Org specification that most Linux distros follow to get
>>>> this to all work is kinda black magic. I suspect in your efforts to
>>>> trim down your OS you forgot to dance Gangnam style widershins around
>>>> the pile of fresh three headed chicken wings. Or something. Maybe add
>>>> BBQ sauce?
>>>>
>>>> I think these are the most relevant mystical tomes -
>>>>
>>>> http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
>>>>
>>>> http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.1.html
>>>>
>>>> http://standards.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html
>>>>
>>>> But it probably boils down to - you shaved a bit too much off to save
>>>> space, and some crucial bit is missing. The problem is identifying
>>>> that missing bit.
>>> [...]
>>>
>>> I dunno whether I shaved off too much. Probably I just didn't install
>>> everything. I think I installed this system about 10 years ago. Ever
>>> since being on Debian/sid, copying it from one computer to the next and
>>> doing the daily updates in order to keep the edge (or at least trying
>>> to). But as in those years the Linux experience evolved from something I
>>> can understand as everything is in plain text config files, to something
>>> very difficult to disentangle as most stuff is handled by strange
>>> daemons, buses and IPCs, it might be I missed something. ;-)
>>>
>>> Anyway, thank you for those helpful FDO links. Tried to do my homework
>>> here, matching with what is written there to my system:
>>>
>>> Quote: "By default, apps should look in $HOME/.icons (for backwards
>>> compatibility), in $XDG_DATA_DIRS/icons and in /usr/share/pixmaps"
>>>
>>> My $XDG_DATA_DIRS is
>>> /opt/e/share/enlightenment:/opt/e/share:/usr/local/share:/usr/share.
>>> That's already interesting. As the folder [...]/enlightenment/icons is
>>> empty. Instead my E icons are in [...]/enlightenment/data/icons. Who
>>> adds this entry to my XDG_DATA_DIRS? Anyway, most of my stock icons are
>>> in /usr/share/icons, so this dir is also covered.
>>>
>>> Quote: "Implementations are required to look in the "hicolor" theme if
>>> an icon was not found in the current theme."
>>>
>>> I have a "hicolor" subdirectory in the icons folder, and it is populated
>>> with all the icons I'd every need for my humble set of applications.
>>>
>>> Quote: "In at least one of the theme directories there must be a file
>>> called index.theme that describes the theme."
>>>
>>> My hicolor directory contains an index.theme file, giving the theme the
>>> name "Hicolor". However, it contains "Hidden=true". So I set this to
>>> false, just in case. Still, it doesn't show up. Anyway, an application
>>> is required to use this theme in case should an icon not be found
>>> anywhere else. Therefore, I'd expect my icons to show up.
>>>
>>> So in this respect it themes my system is not so completely badly set
>>> up. Any more ideas?
>>>
>>> Thanks for you help/patience,
>>> Florian
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Managing the Performance of Cloud-Based Applications
>>> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
>>> Read the Whitepaper.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
>>>
>>>
>>>
>>> _______________________________________________
>>> enlightenment-users mailing list
>>> enlightenment-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
>>>
>>
>
>
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
