[Oberon] ETHO miscl: LEO + LNO + N-O ?

easlab-absa easlab at absamail.co.za
Fri Sep 2 06:23:33 CEST 2011

Pieter Muller wrote:
> Could someone from the ETH please contact me to obtain an 
> archive of historic Oberon files from lillian?

Yes, since I had to buy a Win7 device to connect via my
wireless-connection, I've realised what inferior garbage
apps are foisted on the new generation. 

The WindowsLiveMail default for handling Mail & News is
a Baroque nightmare compared to eg. Forte-Agent, which
I used with Win-3.1, before my ISP told that I'd have to get
W95, and I said screw-you and turned to ETHO & Linux.
I believe the latest Forte-Agent is still good: clear HCI.
When you are reading ETHO in full-screen-mode, and you 
want to extract text-stretches for your notes, there's a 
potential problem or inconvenience, since you haven't 
conveniently got a <workspace> to enter your ETHO 

The macroKeys app: EditKeys.* is convenient here.
I've added to my "p1" macro, which I've been using, thus:-
     p1 ("EditTools.OpenUnix   /tmp/ObnTmp"  call)
     ' ( "CRGtrace.Slctn2ObnTmp"  call)
So, typing "p1" anywhere in a/the textGadget, followed by
the <hotKey>/<insert>, removes/consumes the "p1",
so the eg. full screen textFile is not altered,
and opens the clipBrdFile: /tmp/ObnTmp.
I use "P0" & "P1" in linux to read and append to the
same clipBrd.

LNO-1999 also lists 2 clipboard instructions for
communicating between LNO and the linux-system;
but I as was never able to get them to work.

A wider question, is whether newer-LNO is open source;
eg. to investigate why it loses keyboard access after being
switched-out-of.   This seems to be related to X-windows.
IIRC in frame-buffer-mode it deos NOT lose the key-brd,
but the colours are wrong, besides we normally use X-mode.

Interestingly, to old/1999 LNO version, which could read
DOS-ETHO-files doesn't have these key-brd & display problems;
but since that can't read N-O:format files, it can't do anything
which LEO doesn't already do better.
I want to use some of the facilities of EditKeys/<keyMacro>,
but I haven't been able to understand the source code.
And I'm wondering if it's based on a well known and published
algorithm?  That's why I want to 'copy from *nix to ETHO'.

According to EditKeys.Tool & docos, after you add/define a new
keyMacro, you just need to: EditKeys.Reset &
EditKeys.Read <your file of keyMacros for *this* project> ~
to enable the new-set of macros.

This doesn't work, and the need to reboot, when I still used
N-O, is removed under LEO, where you can just start a 
new/extra LEO to test/debug.
Also System.Free EditKeys doesn't allow the new macro to run.
EditKeys.Mod is documentes as being last updated ca. '93 IIRC.
V4 is dated later ca. '98. But ETHO's has got a wrapper added.
I'm worried/suspecting that no one else is using EditKeys ?

Now I can use the clipBrd to copy this LEO-written text,
to Linux, to get past the mailSendAuthorisation.


== Chris Glur.

PS. I've just realised that my new/additional key macro is redundant
for ETHO, because in ETHO, you can just immediately paste into the
existing `p1-fetched` clipbrd and re-save it. 

More information about the Oberon mailing list