[Oberon] Incremental evolution of piping system?

[eas lab]

What's the value of the ability to quickly write a <DoIt> program in
our nice Oberon syntax?

Python has also got a nice syntax.
Can it make stand-alone scripts, which can be launched by the user,
without further intervention from the user ?

Under *nix, one would write a script to do the task;
but the disadvantage is the difficult syntax, requiring a
steep-learning-curve.

It should be easy to extend ETHO to do:
 under M$, launch DoIt1.com or DoIt1.exe
which does:
 from file1 fetch the </path/file> of <textFile>;
 from file2 fetch the </path/file> of <DestinationFile.mp3>.

 Do a sequence of transformations on <textFile>, which
  are equivalent to no more than 99 characters of *nix script;
  and it would be nice if Oberon could similarly do <piping> to:

 Call existing outside program to:
    translate <updated textFile> to Temp.wav;
 Call existing outside program to:
    translate Temp.wav to <DestinationFile.mp3>;
 delete Temp.wav.

NB. the sequence of 3 consecutive:
 transformations on <textFile>
 and <updated textFile> to Temp.wav
 and Temp.wav to <DestinationFile.mp3>
fit naturally together using the piping style.
I.e. with no extra variables and the other advantages of
 functional programming.
-------------------

A further example of needing a stand-alone DoIt:
 So far Oberon V4 was the only program found which can display
multiple text files together on the one screen on this
<lame M$ x64> operating system.

While navigating the file-tree, it is often found that multiple
files in a directory, and possibly some in other directory/S
need to be viewed and accessed TOGETHER.
How else do you easily/visually confirm that fileA contains
sections from fileB and fileC ?!

Since unlike Linux-based-ETHO, which can be launched from any
directory, V4 would need to find the directory-to-change-to,
listed in a fixed location.
It's not possible to mouse-paste from lame:M$.

A StandAlone DoIt should write the Current directory to a
file that V4 can access. A further problem, suitably solved by
piping/functional approach, is that for some strange reason:
"V4 Oberon for WindowsTM  V4.0-2.3 on Windows NT 6.2",
although developed for M$, writes paths with "/" instead of "\".
So the correct M$-syntax written by the proposed DoIt, can't be
read by the [appaarently faulty] V4.
But changing "\" to "/" is an ideal extra little FUNCTIONAL job
for DoIt, to make the path readable by faulty V4.

It's not about rigerous perfection; it is about mimimum effort
to get the job done.

BTW. how do YOU <paste>
 "V4 Oberon for WindowsTM  V4.0-2.3 on Windows NT 6.2"
 from V4 to M$:IE:gmail ?

== Chris Glur.