[Oberon] Re (2): Starting V4.

[Jörg]

Peter

I had a look at the code of System.Mod in Linux V4 1.7.02.
There, I find an automation/configuration hook in OpenViewers:
It tries to load the module „Configuration“. It is expected that the module body does all things you want to automate/configure additionally during startup.

If the module Configuration is not found, the text file System.Tool is opened instead.

br Jörg

> Am 05.02.2021 um 10:11 schrieb Jörg <joerg.straube at iaeth.ch>:
> 
> Unfortunately, PO2013 does not foresee an „automation“ hook in the code. Could be added but is normally not needed.
> However, you can automate things yourself by editing System.Mod, adding commands to the procedure OpenViewers and compiling System.Mod
> 
> Let‘s assume you want to automate eg the command MyPalette.InitColors.
> Whether you write this command in a special „automatization“ configuration textfile with something like
>   Task1 = MyPalette.InitColors
> or you add directly to the procedure System.OpenViewers the line
>  Oberon.Call(“MyPalette.InitColors“, d);
> 
> is effort-wise more or less the same. It is strange that the „configuration file“ thingy is something people seem to prefer although there are other ways to do it.
> 
> br, Jörg
> 
>> Am 04.02.2021 um 18:21 schrieb peter at easthope.ca:
>> 
>> From:    "Skulski, Wojciech" <skulski at pas.rochester.edu>
>> Date:    Thu, 4 Feb 2021 16:45:53 +0000
>>> Do not forget the command line parameters which are also a form of 
>>> configuration.
>> 
>> Acknowledged; but must the user execute them interactively at each 
>> boot up?  Can commands be executed automatically when the system 
>> boots? 
>> 
>> Regards,                            ... P. L.
>> 
>> -- 
>> Tel: +1 604 670 0140            Bcc: peter at easthope. ca
>> 
>> --
>> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
>> https://lists.inf.ethz.ch/mailman/listinfo/oberon