[Oberon] Re (2): Re (2): PO2013 - System.CloseTrack / System.ExtendDisplay
peter at easthope.ca
peter at easthope.ca
Sun May 5 17:13:00 CEST 2019
From: =?utf-8?Q?J=C3=B6rg_Straube?= <joerg.straube at iaeth.ch>
Date: Sun, 5 May 2019 08:23:34 +0200
> A touchscreen is an ergonomical nightmare when vertical. I mean when
> you sit in front of it at a distance of ~40 cm
Yes, for that case, use a mouse as mentioned in my preceding message.
From: peter at easthope.ca
Date: Sat, 04 May 2019 07:44:21 -0700
> ... pointing can be implemented via mouse or finger. Approximately
> equivalent ...
===================================================
The specific initial challenge was to allow an unprogrammed user to
manipulate displays and tracks, some of which are hidden. Two
concepts should be recognized. (1) Input and output mechanisms; ie.
the known technologies of keyboard, mouse, screen and screen touch.
And (2) the conceptual interface by which the system is manipulated.
The interface integrates I/O mechanisms with system concepts.
My message at 2018-05-09 described a small variation of the Oberon
interface where a hidden or implicit command is made visible.
Therefore avoiding non-evident means such as specially assigned
combinations of buttons and keys. MM+MR, <Fn>, <Ctrl>+<N> and etc.
As luck would have it, the proposal requires pointing; any pointing.
Keyboard input is not required but harmless.
When an annoying bug in the Mail module and a few other things are
fixed will work on a prototype again.
Regards, ... Lyall E.
--
Composed and transmitted by software designed to avoid the
complication and vulnerability of antivirus software.
More information about the Oberon
mailing list