[enlightenment] wbar doesn't get populated during boot if desktop=enlightenment for example

[jls]

I only see the 3 icons from the base even I have extensions  in onboot.lst that normally creates icons in wbar .

[roberts]

Read the .info file. The extension maker did not create the necessary interface files for Tiny Core. It is the first line of the comments.

[althalus]

Read the .info file. The extension maker did not create the necessary interface files for Tiny Core. It is the first line of the comments.

That being said, there is nothing in e17 that should affect wbar's ability to function correctly, and indeed on (all three) of my test systems, appropriate wbar icons are visible for onboot applications when I let wbar start. I tend to find wbar is not necessary for enlightenment however, as there is a gadget on the shelf which serves the same purpose.

[jls]

but wbar works also using other wm, if I load an xtension having an icon entry when the system is running, wbar gets updated, the only problem, I'm repeeting, is for tcz loaded during boot.
I understand u like flwm as I do I, but since (rarely) happens that I install tc/mc to friends' computer, flwm is not always well seen.

I agree wbar isn't needed in E(nlightenment) but wbar is auto populated by this distro despite the one in E

[roberts]

So it works with all other window managers, except enlightenment.
I guess I will have to get involved with this extension then,

[jls]

I only tred enlightenment, using the boot code

Code: [Select]

desktop=enghlitenment_startor something like that, but I feel the problem occours with any other wm

[roberts]

jwm OK, icewm OK, hackedbox OK.

the desktop= is really not very useful anymore, unless you have multiple window managers listed onboot, and then wish to specify which one to actually use via the bootcode.

desktop=icewm

BTW, enlightenment errors out for me with
ERROR: UNABLE TO ASSUME ROOT PRIVILIDEGES.

So unable to test it.

[althalus]

BTW, enlightenment errors out for me with
ERROR: UNABLE TO ASSUME ROOT PRIVILIDEGES.

So unable to test it.

Hmm. I'd noticed those messages too, but since I'd also seen them on a Ubuntu session, and they've never seemed to interfere with e17 being able to run, nor seemed to interfere with it's operation, I'd dismissed them as not being relevant.

If it's actually preventing e17 from starting, then I'll look into finding out the problem there. Is there anything specific in your setup that would force e to stop after those errors?

[roberts]

With enlightenment, I get what appears to be a language select screen, except it is totally blank. Nothing to select. The cursor is very blurred. I tried to click on the wbar terminal and nothing worked. I don't know this window manger, so it is likely me. When exiting the window manager, I see the error messages. Reading the .info file did not help.

[althalus]

Is the cursor blurry, or does the drop shadow just make it look blurry? E17 has the attitude of "We can be a lightweight desktop environment fast enough for embedded devices, AND be fancier than gnome!", but it does make the default cursor a little hard on the eyes.

On first run, it's usually best to boot with "noicons". There's actually a "Next" button hidden under wbar, and whatever e17 does on that first boot interferes with wbar's behaviour. After you get through the config screen, add /home/tc/.e to your backup and then you can turn wbar back on - I have previously promised to update the info file to include this information, but simply haven't had the time to do it properly yet.

[roberts]

Ah, see, the noicons is the trick.

However, this window manager is very difficult for low vision users, such as myself. There is still much of which I am unable to read. After a reboot, sans noicons, wbar seems to still be incompatible.

With implementing freedesktop.org for core menu should help this window manager. I have started such.

[roberts]

I updated the .info with
Best to use 'noicons' boot option.

[jls]

if u don't see well u can customize E.
if u start wbar with -above-desk then when u install an extension which adds an entry in wbar, wbar doesn't crash

[althalus]

Ah, see, the noicons is the trick.

However, this window manager is very difficult for low vision users, such as myself. There is still much of which I am unable to read. After a reboot, sans noicons, wbar seems to still be incompatible.

E is highly customisable, and I'm sure it would be trivial to adjust things for low vision users (Just don't ask me how, as it's not a problem I've needed to solve yet)

With implementing freedesktop.org for core menu should help this window manager. I have started such.

I will be interested in seeing the progress to see how this affects freedesktop DE's.

[roberts]

Another issue with Enlightenment, I see that the freedesktop.org .desktop specification of

Terminal=true

does not work with this extension. I have the other Tiny Core menu items working.

I also have no issue with LXDE extension in using the Terminal=true specification.

Is it just this build or a general issue with Enlightenment?