GUI: различия между версиями

Материал из fidoman.ru
Строка 1: Строка 1:
= NeWS =
+
=== NeWS ===
  
 
[https://en.wikipedia.org/wiki/NeWS Sun NeWS (PostScript-based)]
 
[https://en.wikipedia.org/wiki/NeWS Sun NeWS (PostScript-based)]
Строка 5: Строка 5:
 
[https://groups.google.com/g/comp.windows.news/c/pIoof2p2eew/m/HSBV2prw3CoJ?pli=1 eye.ps]
 
[https://groups.google.com/g/comp.windows.news/c/pIoof2p2eew/m/HSBV2prw3CoJ?pli=1 eye.ps]
  
= X =
+
=== X ===
  
 
[http://oldhome.schmorp.de/marc/xcb.html clipboard monitor]
 
[http://oldhome.schmorp.de/marc/xcb.html clipboard monitor]
Строка 12: Строка 12:
  
 
https://stackoverflow.com/questions/23051594/how-to-set-xlib-window-background-transparent
 
https://stackoverflow.com/questions/23051594/how-to-set-xlib-window-background-transparent
 +
 +
== GUI challenge ==
 +
 +
How to reply on user's action?
 +
 +
User clicks something, there is some reaction. But if this action wants give user some reply, how to send it user?
 +
 +
Trivial solutions:
 +
- modal window. Interfere with other actions, do not provide strict relation with message source. As if the GUI is world of one task.
 +
- message log. No graphical relation with source, can be forgotten.
 +
- notification. Desktop-wide, no graphical relation.
 +
 +
So, there should be some graphical object created when action is run. It must be attached to the object, on that the action is performed, so: 1. User can keep track of progressing action, 2. User can see statuses and errors as they arise, and result status, 3. Some additional options can be implemented via this object, e.g. pause/cancel/rollback/prioritize.

Версия от 09:35, 8 марта 2026

NeWS

Sun NeWS (PostScript-based)

eye.ps

X

clipboard monitor

docs

https://stackoverflow.com/questions/23051594/how-to-set-xlib-window-background-transparent

GUI challenge

How to reply on user's action?

User clicks something, there is some reaction. But if this action wants give user some reply, how to send it user?

Trivial solutions:

- modal window. Interfere with other actions, do not provide strict relation with message source. As if the GUI is world of one task.
- message log. No graphical relation with source, can be forgotten.
- notification. Desktop-wide, no graphical relation.

So, there should be some graphical object created when action is run. It must be attached to the object, on that the action is performed, so: 1. User can keep track of progressing action, 2. User can see statuses and errors as they arise, and result status, 3. Some additional options can be implemented via this object, e.g. pause/cancel/rollback/prioritize.