missing accessibility options in pager #58

Open
opened 2024-01-03 11:08:15 -08:00 by Seegras · 3 comments

The pager (in the shelf) by default shows a scaled down real-time image of each workspace; which appars to be non-configurable.

This has two problems:

  • Certain backgrounds don't lend themselves to be tiled, and the pager will look ugly and/or badly recognizable. The attachement shows the pager, the background image (a photo) looks quite ugly hectic when minimized and tiled.

  • If an game or video, or even a video-conference(!) is not running full-screen, the real-time icon becomes a huge distraction at the edge of the screen. This is an very bad user-interface design fail.

An option to at least turn this off and return to a "dumb"-mode, showing a single-colour (or gradient) background and only the outlines of windows, would be advisable.

In fact, showing only rectangles of the screens (with names), without any representations of the windows on it would even suffice.

The pager (in the shelf) by default shows a scaled down real-time image of each workspace; which appars to be non-configurable. This has two problems: - Certain backgrounds don't lend themselves to be tiled, and the pager will look ugly and/or badly recognizable. The attachement shows the pager, the background image (a photo) looks quite ugly hectic when minimized and tiled. - If an game or video, or even a video-conference(!) is not running full-screen, the real-time icon becomes a huge distraction at the edge of the screen. This is an very bad user-interface design fail. An option to at least turn this off and return to a "dumb"-mode, showing a single-colour (or gradient) background and only the outlines of windows, would be advisable. In fact, showing only rectangles of the screens (with names), without any representations of the windows on it would even suffice.
Owner

Theme can add boundaries/bordering and layering on top of the mini view - so the "backgrounds tiling" is a theme design choice thing really. Every pager view will show the background of that desktop. if they have different wallpapers - they will show differently per pager view. if they are animated gifs or even video backgrounds (yes - you can select e.g. a mp4 file as a background ine) all the pagers will play a miniature of thet video per desktop mini view correctly.

As for the mini view windows matching the real window content... that is the whole point. Yes. if the window updates, the mini view updates. That is actually a big usability plus as it allows visual identification of what yo switch tyo and what is there and tyhe state it's in. Has the web paged finished loading? has the build in the terminal stopped scrolling? etc. if it didn't update then you'd have a whole host of new bugs. One kproblem here is - it's pretty hard to keep this out of sync with the screen. the mini vierw literally re-uses the same compositor content and objects pointing to the same data - "zero copy". To have it not keep up actually adds overhead and would involve jumping throkugh some major hoops to try and NOT have them sync. there isn't actually any infrastructure in evas or enlightenment to do that (making a copy of it on the fly - cpu read-back for example).

There was once a plain pager module. I removed it as it was partly broken - didn't match the defult pager in what it displayed (the set of windows, stacking of windows etc.) and was ignored/unmaintained/untested except for like 1 or 2 people who chose to use it. As it had far too few users for the given workload to keep maintained (required extra theme work too to have blank windows with lots of icons in the pager view that were so small that they didn't really tell you much what the window was so had a whole new set of usability issues) etc., I removed it from a maintenance point of view. I don't have bandwidth to maintain both view modes.

So ... given no one will step up to maintain an alternate view with the added theme elements, and this is the first complaint about a missing plain pager in the last 3 years since I removed it, I think that speaks to just how generally unpopular a plain pager look is. It's removed until such a time as there are enough people willing to agree to do that maintenance and maintain it. In fact the only sane way to maintain it is to make the core deskview miniature view itself have a non-real miniature mode and not a whole separate pager module... :)

FYI a plain pager (wuth icons, labels) is more useless as generally you get maybe 1 or 2 letters into a window in miniature most of the time. Often not even that. When you have 10 terminals and every one has only "Te" in it... it's pretty useless. So work to maintain vs amount of use IMHO doesn't justify it unless someone else is willing to do the work to maintain and work on it.

Theme can add boundaries/bordering and layering on top of the mini view - so the "backgrounds tiling" is a theme design choice thing really. Every pager view will show the background of that desktop. if they have different wallpapers - they will show differently per pager view. if they are animated gifs or even video backgrounds (yes - you can select e.g. a mp4 file as a background ine) all the pagers will play a miniature of thet video per desktop mini view correctly. As for the mini view windows matching the real window content... that is the whole point. Yes. if the window updates, the mini view updates. That is actually a big usability plus as it allows visual identification of what yo switch tyo and what is there and tyhe state it's in. Has the web paged finished loading? has the build in the terminal stopped scrolling? etc. if it didn't update then you'd have a whole host of new bugs. One kproblem here is - it's pretty hard to keep this out of sync with the screen. the mini vierw literally re-uses the same compositor content and objects pointing to the same data - "zero copy". To have it not keep up actually adds overhead and would involve jumping throkugh some major hoops to try and NOT have them sync. there isn't actually any infrastructure in evas or enlightenment to do that (making a copy of it on the fly - cpu read-back for example). There was once a plain pager module. I removed it as it was partly broken - didn't match the defult pager in what it displayed (the set of windows, stacking of windows etc.) and was ignored/unmaintained/untested except for like 1 or 2 people who chose to use it. As it had far too few users for the given workload to keep maintained (required extra theme work too to have blank windows with lots of icons in the pager view that were so small that they didn't really tell you much what the window was so had a whole new set of usability issues) etc., I removed it from a maintenance point of view. I don't have bandwidth to maintain both view modes. So ... given no one will step up to maintain an alternate view with the added theme elements, and this is the first complaint about a missing plain pager in the last 3 years since I removed it, I think that speaks to just how generally unpopular a plain pager look is. It's removed until such a time as there are enough people willing to agree to do that maintenance and maintain it. In fact the only sane way to maintain it is to make the core deskview miniature view itself have a non-real miniature mode and not a whole separate pager module... :) FYI a plain pager (wuth icons, labels) is more useless as generally you get maybe 1 or 2 letters into a window in miniature most of the time. Often not even that. When you have 10 terminals and every one has only "Te" in it... it's pretty useless. So work to maintain vs amount of use IMHO doesn't justify it unless someone else is willing to do the work to maintain and work on it.
Author

I already expected something like that zero-copy thing, it's the only explanation why the pager can do what it does, and is so fast.

For me, the pager is mainly an option to change the desktop without using the keyboard, so one without mini-windows (only displaying the desktop number/name) would basically be enough.

I mean, that's the one I use on WindowMaker:

I already expected something like that zero-copy thing, it's the only explanation why the pager can do what it does, and is so fast. For me, the pager is mainly an option to change the desktop without using the keyboard, so one without mini-windows (only displaying the desktop number/name) would basically be enough. I mean, that's the one I use on WindowMaker:
Owner

you know switching desktops is in menus too (other than keybindings by default like alt+f1/f2/f3/f4 also alt+shift left/right arrows too... and tbh i use keys 99% of the time to switch)

there's "show pager popup" action you could bind to a mouse button (like my mouse has extra buttons i could bind) and it pops up a large pager with mini views - click on the desktop to switch and press escape (or click outside the popup) so it only appears when you want/need it.

i mean perhaps what you want is a gadget that allows you to create N "buttons" with any icon and/or label and assign an e "action" to them ... this would be generically useful to creatr custom buttons to do anything e can do...

you know switching desktops is in menus too (other than keybindings by default like alt+f1/f2/f3/f4 also alt+shift left/right arrows too... and tbh i use keys 99% of the time to switch) there's "show pager popup" action you could bind to a mouse button (like my mouse has extra buttons i could bind) and it pops up a large pager with mini views - click on the desktop to switch and press escape (or click outside the popup) so it only appears when you want/need it. i mean perhaps what you want is a gadget that allows you to create N "buttons" with any icon and/or label and assign an e "action" to them ... this would be generically useful to creatr custom buttons to do anything e can do...
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: enlightenment/enlightenment#58
No description provided.