[Oberon] Re. batch job thread.

[eas lab]

> if the command is followed by a *,
> the parameter is the selected viewer.

Yes, I haven't done Oberon programming for years; [but use LNO for
 superb analysis/documentation of complex stuff, which needs:
 1. see multiple files, together on ONE screen;
 2. Color/Font related concepts/text - like koki-pens on paper;
but I remember experimenting with the <* F1 frame-marker> to pipe
stage N to stage N+1 via the OutputFrame => InputFrame.

> With Andreas‘ automating method your „Unix piping“ could look
> like this:
>
> Oberon.Batch
>   WAV.FromText input.text => temp.wav ~
>   MP3.FromWAV temp.wav => final.mp3 ~
>   System.DeleteFiles temp.wav ~
> ~

I like that! Could it easily be ported to LNO? From where?
---
PS. LEO <linux eth Oberon> was the most magical system I ever used.
And I could never understand how no one else ever mentioned it.
And the Canadian who eventually got more aggressive to be given
 d/l info, was banned from this forum....
Only later, after much painfull testing did I discover that I had
been just lucky that my 486PC, installed LEO perfectly [font sizeS
etc.] on the first installation attempt.
Now on my 2 laptops <LEO's font sizeS> are only usable via Debian7
installation CD set for 486. I can't bootup the CD just to use LEO!
A simple example of LEO's superiority is:
   show me the latest 22 file names on USBstik2/home/ETH:
= System.Execute ls -t /mnt/Stik2/home/ETH | less -22
This relates also to the common absurdity, also adopted by ETHO,
of not having the DEFAULT file listing in RECENTCY order.
Imagine working with 3 tools from a toolbox of 50 tools, where
<put down CoffeeCup to fetch TeaSpoon causes CoffeeCup to sinkdown
to its <alphabetic level>. Which relates to the fact that only after
computers had been used for sometime was it obvious that the STACK;
ie. RECENTCY was the best ordering.
-- Sorry for rant!!



On Thu, Oct 8, 2020 at 9:23 AM Jörg <joerg.straube at iaeth.ch> wrote:

> If I look at your request, you ask for TWO Unix/Linux mechanisms to be
> ported to OberonOS.
> 1) reading/writing from/to standard input/output
> 2) building a sequence of tasks by „piping“
>
> Let‘s start with your requirement 2): running different commands in a
> sequence is not a functionality that the base Oberon OS offers. However
> both Andreas and Michael provided Oberon modules offering batch
> capabilities. We ourselves use these batching tools to automate the Oberon
> OS build process.
>
> Coming back to your requirement 1). If you write an Oberon command like
> e.g. System.CopyFiles you have to carefully plan, how the input/output to
> your commands look like. Are the parameters numbers, strings, files, texts,
> viewers...
> The Oberon OS offers basically three methods
> - parameters are read directly following the command
> - if the command is followed by an ^, the parameters are read from the
> mouse selection
> - if the command is followed by a *, the parameter is the selected viewer.
>
> If you plan to run different commands in a sequence and one command shall
> take input of other commands, the prefered method is to work with files.
> Mainly as the RAM on the original system is limited...
>
> With Andreas‘ automating method your „Unix piping“ could look like this:
>
> Oberon.Batch
>   WAV.FromText input.text => temp.wav ~
>   MP3.FromWAV temp.wav => final.mp3 ~
>   System.DeleteFiles temp.wav ~
> ~
>
> br
> Jörg
>
> > Am 08.10.2020 um 16:46 schrieb eas lab <lab.eas at gmail.com>:
> >
> > 
> > Sorry that I failed to reply to the existing thread via my intolerable,
> > continualy updating [changing to screw the captivated public] M$pook
> > mailer.
> > ---------
> > What about extending [AFAI understand this] to chaining the data thru
> > various stages; eg. instead of just having each stage write a TextFrame
> > which is MANUALLY marked for input to the next stage.
> >   *nix scripting needs only a few lines to use existing <functions> to:
> > <TextToMP3(TextFile, MP3File) == described in natual language:
> >  remove "[<digits>]"
> >  replace <these absurd 3-bytes> with corresponding single/dbl:quotes
> >  <other clean text fuctions: each via CHAIN input to output
> >  Input to existing TextToWav function
> >  Chain to existing WavToMP3
> >  Chain to final destination file.
> >
> > --
> > Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> > https://lists.inf.ethz.ch/mailman/listinfo/oberon
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.inf.ethz.ch/pipermail/oberon/attachments/20201008/31a5bdf8/attachment.html>