HOW2 get output of ORTool.DecSym and ORTool.DecObj in a file.
Dear All, I see two valuable commands inside ORTool.Mod.txt, ORTool.DecSym and ORTool.DecObj. I used them as follows: ORTool.DecSym Files.smb ~ ORTool.DecObj Files.rsc ~ Beautifully they present their desired output. :-) However, instead of reading the output from System.Log, I would like to get the output collected in a file. So that, I can easily take the generated file out from Oberon Simulator (Peter De Wachter's), and read/analyze it on my Linux desktop. How can the code of ORTool.DecSym and ORTool.DecObj be changed, so that they can produce their output collected in a file? Confessions: 1. You can suggest me to copy paste the output from System.Log to a file. But I find it very hard, because output is very long and copy-paste it needs a special trick. 2. I find it easier to use pcreceive.sh and pcsend.sh to send files in/out of Oberon Simulator, and to modify code/text on Linux Desktop. With thanks and best regards, Yours sincerely, Srinivas Nayak Home: http://www.mathmeth.com/sn/ Blog: http://srinivas-nayak.blogspot.in/
Hi Srinivas The beauty of Oberon is that System.Log is a file already. You only have to store it. To do so, you can click at the lower edge of the menu bar of System.Log and insert the text „Edit.Store“ in the menu bar. Then click on that command and voila: your System.Log is stored as a file with name System.Log. Jörg
Am 12.07.2016 um 17:37 schrieb Srinivas Nayak <sinu.nayak2001@gmail.com>:
Dear All,
I see two valuable commands inside ORTool.Mod.txt, ORTool.DecSym and ORTool.DecObj.
I used them as follows: ORTool.DecSym Files.smb ~ ORTool.DecObj Files.rsc ~
Beautifully they present their desired output. :-)
However, instead of reading the output from System.Log, I would like to get the output collected in a file. So that, I can easily take the generated file out from Oberon Simulator (Peter De Wachter's), and read/analyze it on my Linux desktop.
How can the code of ORTool.DecSym and ORTool.DecObj be changed, so that they can produce their output collected in a file?
Confessions: 1. You can suggest me to copy paste the output from System.Log to a file. But I find it very hard, because output is very long and copy-paste it needs a special trick. 2. I find it easier to use pcreceive.sh and pcsend.sh to send files in/out of Oberon Simulator, and to modify code/text on Linux Desktop.
With thanks and best regards,
Yours sincerely, Srinivas Nayak
Home: http://www.mathmeth.com/sn/ Blog: http://srinivas-nayak.blogspot.in/ -- Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon
Can you type "Edit.Store *" anywhere, star mark the System.Log, and save it that way as well? On Tue, Jul 12, 2016 at 4:28 PM, Joerg <joerg.straube@iaeth.ch> wrote:
Hi Srinivas
The beauty of Oberon is that System.Log is a file already. You only have to store it. To do so, you can click at the lower edge of the menu bar of System.Log and insert the text „Edit.Store“ in the menu bar. Then click on that command and voila: your System.Log is stored as a file with name System.Log.
Jörg
Am 12.07.2016 um 17:37 schrieb Srinivas Nayak <sinu.nayak2001@gmail.com :
Dear All,
I see two valuable commands inside ORTool.Mod.txt, ORTool.DecSym and ORTool.DecObj.
I used them as follows: ORTool.DecSym Files.smb ~ ORTool.DecObj Files.rsc ~
Beautifully they present their desired output. :-)
However, instead of reading the output from System.Log, I would like to get the output collected in a file. So that, I can easily take the generated file out from Oberon Simulator (Peter De Wachter's), and read/analyze it on my Linux desktop.
How can the code of ORTool.DecSym and ORTool.DecObj be changed, so that they can produce their output collected in a file?
Confessions: 1. You can suggest me to copy paste the output from System.Log to a file. But I find it very hard, because output is very long and copy-paste it needs a special trick. 2. I find it easier to use pcreceive.sh and pcsend.sh to send files in/out of Oberon Simulator, and to modify code/text on Linux Desktop.
With thanks and best regards,
Yours sincerely, Srinivas Nayak
Home: http://www.mathmeth.com/sn/ Blog: http://srinivas-nayak.blogspot.in/ -- Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon
-- Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon
-- (email is my preferred communication media) Aubrey McIntosh, Ph.D. 1502 Devon Circle Austin TX 78723-1814 (512)-348-7401
Yes. This is the other method Paul described in an earlier mail. Jörg
Am 13.07.2016 um 00:04 schrieb <Aubrey.McIntosh@alumni.utexas.net> <Aubrey.McIntosh@alumni.utexas.net>:
Can you type "Edit.Store *" anywhere, star mark the System.Log, and save it that way as well?
On Tue, Jul 12, 2016 at 4:28 PM, Joerg <joerg.straube@iaeth.ch <mailto:joerg.straube@iaeth.ch>> wrote: Hi Srinivas
The beauty of Oberon is that System.Log is a file already. You only have to store it. To do so, you can click at the lower edge of the menu bar of System.Log and insert the text „Edit.Store“ in the menu bar. Then click on that command and voila: your System.Log is stored as a file with name System.Log.
Jörg
Am 12.07.2016 um 17:37 schrieb Srinivas Nayak <sinu.nayak2001@gmail.com <mailto:sinu.nayak2001@gmail.com>>:
Dear All,
I see two valuable commands inside ORTool.Mod.txt, ORTool.DecSym and ORTool.DecObj.
I used them as follows: ORTool.DecSym Files.smb ~ ORTool.DecObj Files.rsc ~
Beautifully they present their desired output. :-)
However, instead of reading the output from System.Log, I would like to get the output collected in a file. So that, I can easily take the generated file out from Oberon Simulator (Peter De Wachter's), and read/analyze it on my Linux desktop.
How can the code of ORTool.DecSym and ORTool.DecObj be changed, so that they can produce their output collected in a file?
Confessions: 1. You can suggest me to copy paste the output from System.Log to a file. But I find it very hard, because output is very long and copy-paste it needs a special trick. 2. I find it easier to use pcreceive.sh and pcsend.sh to send files in/out of Oberon Simulator, and to modify code/text on Linux Desktop.
With thanks and best regards,
Yours sincerely, Srinivas Nayak
Home: http://www.mathmeth.com/sn/ <http://www.mathmeth.com/sn/> Blog: http://srinivas-nayak.blogspot.in/ <http://srinivas-nayak.blogspot.in/> -- Oberon@lists.inf.ethz.ch <mailto:Oberon@lists.inf.ethz.ch> mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon <https://lists.inf.ethz.ch/mailman/listinfo/oberon>
-- Oberon@lists.inf.ethz.ch <mailto:Oberon@lists.inf.ethz.ch> mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon <https://lists.inf.ethz.ch/mailman/listinfo/oberon>
-- (email is my preferred communication media) Aubrey McIntosh, Ph.D. 1502 Devon Circle Austin TX 78723-1814 (512)-348-7401
-- Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon
No. I'm pretty sure Edit.Store * won't do anything useful. The procedure works out a viewer to save and then sets up a scanner to parse the filename to save under - these two things come from the same place when the command is executed from a viewer menu, and from (usually) different places when the name (or selection) is specified explicitly in the command. (Strange, because I seem to remember something like an Edit.Store * as well - but I checked in the code in the original book, and it's similar to the 2013 version.)
Yes. This is the other method Paul described in an earlier mail. Jörg
Am 13.07.2016 um 00:04 schrieb <Aubrey.McIntosh@alumni.utexas.net> <Aubrey.McIntosh@alumni.utexas.net>:
Can you type "Edit.Store *" anywhere, star mark the System.Log, and save it that way as well?
Paul In a much earlier version (1993), Edit.Store looked like this: PROCEDURE Store*; VAR V: Viewers.Viewer; S: Texts.Scanner; T: Texts.Text; BEGIN IF Oberon.Par.frame = Oberon.Par.vwr.dsc THEN V := Oberon.Par.vwr ELSIF Oberon.Pointer.on THEN V := Oberon.MarkedViewer() END; IF (V # NIL) & (V IS MenuViewers.Viewer) & (V.dsc IS TextFrames.Frame) & (V.dsc.next IS TextFrames.Frame) THEN Texts.OpenScanner(S, V.dsc(TextFrames.Frame).text, 0); Texts.Scan(S); IF (S.class = Texts.Name) OR (S.class = Texts.String) THEN Str("Edit.Store "); Str(S.s); T := V.dsc.next(TextFrames.Frame).text; Texts.Close(T, S.s); Int(T.len); Ln; END END END Store; Back then "Edit.Store *" was possible and it stored the text of the marked viewer. But basically the * was ignored... br Jörg -----Original Message----- From: Oberon [mailto:oberon-bounces@lists.inf.ethz.ch] On Behalf Of Paul Reed Sent: Mittwoch, 13. Juli 2016 11:04 To: ETH Oberon and related systems <oberon@lists.inf.ethz.ch> Subject: Re: [Oberon] HOW2 get output of ORTool.DecSym and ORTool.DecObj in a file. No. I'm pretty sure Edit.Store * won't do anything useful. The procedure works out a viewer to save and then sets up a scanner to parse the filename to save under - these two things come from the same place when the command is executed from a viewer menu, and from (usually) different places when the name (or selection) is specified explicitly in the command. (Strange, because I seem to remember something like an Edit.Store * as well - but I checked in the code in the original book, and it's similar to the 2013 version.)
Yes. This is the other method Paul described in an earlier mail. Jörg
Am 13.07.2016 um 00:04 schrieb <Aubrey.McIntosh@alumni.utexas.net> <Aubrey.McIntosh@alumni.utexas.net>:
Can you type "Edit.Store *" anywhere, star mark the System.Log, and save it that way as well?
-- Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon
To do so, you can click at the lower edge of the menu bar of System.Log and insert the text âEdit.Storeâ in the menu bar. Then click on that command and voila: your System.Log is stored as a file with name System.Log.
Edit.Mod's command procedure named Store allows two ways of saving text (the first IF statement). Either, the text in the viewer (main frame) of the menu frame containing the command Edit.Store is saved (which Joerg has engineered above by adding the command to the Log's menu); or, the text in the marked viewer (marked by the star pointer, set up by pointing with the mouse and pressing Ctrl-Z) is saved under the name parameter of the Store command. You can even make it get the name from the current selection by specifying the name as "^". So, as an alternative, you can for example just enter the command "Edit.Store Result1.Log" in the log (or in any other viewer or tool), mark the viewer whose text you wish to save under that (arbitrary) name, and execute the command. HTH Paul PS: As an exercise, work out how much stack and heap space is used to do the above in the Oberon System, compared with how much resource is needed to save a text document in your mainstream operating system of choice :)
Paul: thinking of possible applications of the FPGA Oberon, these would be easier to develop if the SD card could be read under the workstation OS as a regular SD card. Are there any plans to develop the common file system which would make it possible? I am not expecting miracles from the unpaid community. I am just wondering how to make the life simpler. The prime reason to develop instruments running the FPGA Oberon OS would be to collect data. The SD card is a wonderful means of data storage, if it can be read outside the Oberon System. Two methods come to my mind: (1) The SD card is formatted in a regular way, like every digital camera would do. (2) Alternatively, there could be a Windows/Mac/Linux application which can open the SD card, display its content, and make it easy to copy the files. On a more general note, what are the means of easily and efficiently exchanging data between the FPGA Oberon and the workstation world? The accent is on both "easily and efficiently". If I collect a 2GB data file then I would like to easily and efficiently transfer it to the analysis environment. Trickling the file through the wireless or serial is not quite adequate in this case. What are your thoughts? Thank you, Wojtek ________________________________________ From: Oberon [oberon-bounces@lists.inf.ethz.ch] on behalf of Paul Reed [paulreed@paddedcell.com] Sent: Tuesday, July 12, 2016 6:51 PM To: ETH Oberon and related systems Subject: [Oberon] How to save a viewer's text as a file
To do so, you can click at the lower edge of the menu bar of System.Log and insert the text „Edit.Store“ in the menu bar. Then click on that command and voila: your System.Log is stored as a file with name System.Log.
Edit.Mod's command procedure named Store allows two ways of saving text (the first IF statement). Either, the text in the viewer (main frame) of the menu frame containing the command Edit.Store is saved (which Joerg has engineered above by adding the command to the Log's menu); or, the text in the marked viewer (marked by the star pointer, set up by pointing with the mouse and pressing Ctrl-Z) is saved under the name parameter of the Store command. You can even make it get the name from the current selection by specifying the name as "^". So, as an alternative, you can for example just enter the command "Edit.Store Result1.Log" in the log (or in any other viewer or tool), mark the viewer whose text you wish to save under that (arbitrary) name, and execute the command. HTH Paul PS: As an exercise, work out how much stack and heap space is used to do the above in the Oberon System, compared with how much resource is needed to save a text document in your mainstream operating system of choice :) -- Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.inf.ethz.ch_mailman_listinfo_oberon&d=CwIFaQ&c=kbmfwr1Yojg42sGEpaQh5ofMHBeTl9EI2eaqQZhHbOU&r=uUiA_zLpwaGJIlq-_BM9w1wVOuyqPwHi3XzJRa-ybV0&m=LPuTSpHPa9C8QVePF2gCfvWFa2hzQmG68Q_wTaCcBJo&s=V7oEVvKgd927-f40LfKKTz36UzxclGTaHKwCvLurEOI&e=
Many thanks Jorg, You did my job lot easier. On the Simulator, if I click at the lower edge of the menu bar of System.Log, the cursor is not visible, but backspace works! Initially I thought, since cursor is not visible, may be adding command to menu bar is not possible. Anyway, with a little guess of cursor position, it is doable... With thanks and best regards, Yours sincerely, Srinivas Nayak Home: http://www.mathmeth.com/sn/ Blog: http://srinivas-nayak.blogspot.in/ On 07/13/2016 02:58 AM, Joerg wrote:
Hi Srinivas
The beauty of Oberon is that System.Log is a file already. You only have to store it. To do so, you can click at the lower edge of the menu bar of System.Log and insert the text „Edit.Store“ in the menu bar. Then click on that command and voila: your System.Log is stored as a file with name System.Log.
Jörg
Am 12.07.2016 um 17:37 schrieb Srinivas Nayak <sinu.nayak2001@gmail.com>:
Dear All,
I see two valuable commands inside ORTool.Mod.txt, ORTool.DecSym and ORTool.DecObj.
I used them as follows: ORTool.DecSym Files.smb ~ ORTool.DecObj Files.rsc ~
Beautifully they present their desired output. :-)
However, instead of reading the output from System.Log, I would like to get the output collected in a file. So that, I can easily take the generated file out from Oberon Simulator (Peter De Wachter's), and read/analyze it on my Linux desktop.
How can the code of ORTool.DecSym and ORTool.DecObj be changed, so that they can produce their output collected in a file?
Confessions: 1. You can suggest me to copy paste the output from System.Log to a file. But I find it very hard, because output is very long and copy-paste it needs a special trick. 2. I find it easier to use pcreceive.sh and pcsend.sh to send files in/out of Oberon Simulator, and to modify code/text on Linux Desktop.
With thanks and best regards,
Yours sincerely, Srinivas Nayak
Home: http://www.mathmeth.com/sn/ Blog: http://srinivas-nayak.blogspot.in/ -- Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon
-- Oberon@lists.inf.ethz.ch mailing list for ETH Oberon and related systems https://lists.inf.ethz.ch/mailman/listinfo/oberon
However, instead of reading the output from System.Log, I would like to get the output collected in a file. So that, I can easily take the generated file out from Oberon Simulator (Peter De Wachter's), and read/analyze it on my Linux desktop.
You can use the emulator's Clipboard module. The command Clipboard.CopyViewer will copy all text from a window and then you can paste it in a Linux editor. It's the easiest way to transfer text files.
Dear All, You made my day. All my questions answered. I like this community most for everybody's help and support. This is another nice forum where people actively answer and help. I am grateful for you kind help. :-) With thanks and best regards, Yours sincerely, Srinivas Nayak Home: http://www.mathmeth.com/sn/ Blog: http://srinivas-nayak.blogspot.in/
participants (7)
-
Aubrey.McIntosh＠alumni.utexas.net -
Joerg -
Jörg
-
Paul Reed -
Peter De Wachter -
Skulski, Wojciech -
Srinivas Nayak