[Oberon] Oberon on the Raspberry Pi

[eas lab]

>> - The Oberon screen is not part of normal WM Window. May be it is, but
>> it looks if its not.
>>
>> Anyway, the behaviour is different to that of other linux systems, f.e.
>> debian / ubuntu on x86. Here is
>> Oberon Screen is per default part of a window which i can grab and move
>> around. I see no reason, why
>> FXDE on RaspPi should behave other as Gnome/Unity on my x86.

X11 is known to be monster.
LNO also has problems running under X.
Whereas the FrameBuffer version has less problems, and it's
spectacular to see the 'graphic screen' in console mode.

But now I remember: so was it to see V5 in console mode.
I've 'lost' the text and mouse on my V5; only the mouse pointer
is visible when it goes off the V5 frame. But I'm not going to spend
effort debugging it unless I can access my <log file> written in V5.
Otherwise it's just a journey going nowhere.

== Chris Glur.


On 4/19/14, eas lab <lab.eas at gmail.com> wrote:
> Think outside-the-box, like criminals do.
> If the bus-driver passes your gate 4 times a day; when you tie a green-rag
> to the gate, he can be pre-programmed to:
>  IF SeeGreenFlag THEN <launch *nix [or any] commands>.
>
> Even in *.Obj [binany executables] the <string variables> are in ASCII.
> There's no good reason to transform then.
>
> IIRC, my log-file which I started, when ARM:V5 eventually worked, was
> still accessible, after I needed to power-down, to exit.
> So my text must have been saved in a file.
> If I'd know before, I could have saved <the dir info> and seem what had
> changed. Unfortunately rPi lacks a RTC, to show the most recent
> file-changes.
>
> ==Chris Glur.
>
>
> On 4/18/14, Paul Thomas Melville <ptmelville at gmail.com> wrote:
>> On Fri, Apr 18, 2014 at 11:58 AM, eas lab <lab.eas at gmail.com> wrote:
>>
>>> Sure, V5 doesn't know about *nix, but the designers know where the
>>> file is saved.
>>> And it won't be encrypted. If they can tell me where/what it is, I'd
>>> expect to be able
>>> to extract the near-plain-ASCII, and it should be easy also to make a
>>> <formatter>
>>> for reading in. I can read AosFS textfiles on rPi, with less pain than
>>> using  Windows.
>>
>> PO2013 doesn't use AsciiCoder. Tools.Convert can be used to strip any
>> formatting, which will result in plain text files. This way you will get
>> plain
>> ASCII without much trouble.
>>
>> You can read about PCLink is section 15.2 of the book. It is used to send
>> or receive one file at the time from and to Oberon. I pointed out
>> previously
>> related tools used by emulator.
>>
>>> To launch *nix [or any] commands, you have a cronJob/timer, which
>>> occasionally
>>> looks at the files that V5 writes. Even it the underlying system can
>>> only
>>> detect
>>> the size or date change, that can be a signal.
>>
>> Cron is used for scheduling periodic tasks. For monitoring files on Linux
>> provides inotify - there are multiple tools that are based around it. It
>> is
>> just
>> better tool for this task, but I don't see how it helps in this
>> situation and how
>> it could be used.
>>
>> --
>> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
>> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>>
>