As there was a little glitch in one of the contained packages, I refreshed the net-oo-rexx packages and changed the date in the name to 20250907 at <https://wi.wu.ac.at/rgf/rexx/tmp/net-oo-rexx-packages/>.

Having a little bit of time, here is a "hands-on" direction:

 * download the zip archive for your operating system ("OPSYSNAME", i.e., one of 
"windows.x86_64",
   "macos.universal_64", or "ubuntu2204.x86_64")

     o if it is Windows or MacOS, then before unzipping, dequarantize the 
zip-archive as documented
       in "NOTE # 1" in the readme file at
       
<https://wi.wu.ac.at/rgf/rexx/tmp/net-oo-rexx-packages/readme_net-oo-rexx.txt>

 * unzip the zip archive and
     o then change into the created subdirectory
       "net-oo-rexx.macos.OPSYSNAME-portable-release-20250907"

     o then run "setup.cmd" (Windows) or "./setup.sh" (MacOS, Linux)

         + this will create the shell scripts "run" (Unix)/"run.cmd" (Windows), and 
"setenv"
           (Unix)/"setenv.cmd" (Windows)

             # "run"/"run.cmd": set the environment variables to point to the 
net-oo-rexx oorexx,
               netrexx, and packages temporarily (for the duration of the 
execution of the run
               shell script); on Windows you only need to use "run", on Unix 
you need to include
               the current directory, i.e. use "./run" instead of "run" such 
that e.g.

                 * run oorexxshell ... will run oorexxshell from net-oo-rexx, 
an incredible useful
                   shell for Rexx programmers

                 * run rexx testoorexx.rex ... will run the 'testoorexx.rex' 
from net-oo-rexx,
                   which displays the characteristics of the ooRexx interpreter 
that gets used

                 * run rexx highlight -a testoorexx.rex ... will use 
"highlight.rex" from the
                   net-oo-rexx package rexx-parser, which will syntax highlight 
"testoorexx.rex"
                   with ANSI escape sequences such that you can see the colors 
in your terminal
                   window; if you were to use the switch "-h" instead, the Rexx 
program will get
                   syntax highlighted in HTML; hint: you could use the name of 
one of your Rexx
                   programs instead

                 * run rexx rexxdebugger testoorexx.rex ... this will use the 
net-oo-rexx package
                   rexxdebugger, which allows you to debug any Rexx program in 
a GUI; hint: you
                   could use the name of one of your Rexx programs instead

                 * run rexx rexxdebugger packages/rexxdebugger/tutorial.rex ... 
this will use the
                   net-oo-rexx package rexxdebugger with a very nice 
tutorial.rex file, explaining
                   how to use the rexxdebugger (very impressive!)

                 * run rexx tracetool -tr testoorexx.rex ... this will use the 
net-oo-rexx supplied
                   "tracetool.rex" to run "testoorexx.rex" with "trace result" 
and save a tracelog
                   in a file named "testoorexx.rex_trace.xml"; hint: you could 
use the name of one
                   of your Rexx programs instead

                     o run rexx tracetool -s testoorexx.rex_trace.xml ... will 
display the tracelog
                       formatted as "trace r" would format it
                     o run rexx tracetool -p testoorexx.rex_trace.xml ... will 
create a profile
                       from the tracelog
                     o run rexx tracetool -p -sl testoorexx.rex_trace.xml ... 
will create a profile
                       SQLite script from the tracelog, such that you could use 
it to analyze the
                       tracelog data for profiling

                 * run rexx -e "call bsf.cls;say .bsf4rexx~display.version" ... 
will execute the
                   Rexx program supplied in the string, which will display the 
version of ooRexx,
                   BSF4ooRexx, Java and operating system in use (BSF4ooRexx is 
one of the packages
                   contained in net-oo-rexx)


             # "setenv"/"setenv.cmd": used to set the environment variables in 
the shell to point
               to the net-oo-rexx oorexx, netrexx, and packages; in Unix you need to 
use "source
               ./setenv"; after setting the environment variables of the 
terminal shell, you can
               issue the commands as:

                 * oorexxshell ... will run oorexxshell from net-oo-rexx, an 
incredible useful
                   shell for Rexx programmers

                 * rexx testoorexx.rex ... will run the 'testoorexx.rex' from 
net-oo-rexx, which
                   displays the characteristics of the ooRexx interpreter that 
gets used

                 * rexx highlight -a testoorexx.rex ... will use 
"highlight.rex" from the
                   net-oo-rexx package rexx-parser, which will syntax highlight 
"testoorexx.rex"
                   with ANSI escape sequences such that you can see the colors 
in your terminal
                   window; if you were to use the switch "-h" instead, the Rexx 
program will get
                   syntax highlighted in HTML; hint: you could use the name of 
one of your Rexx
                   programs instead

                 * rexx rexxdebugger testoorexx.rex ... this will use the 
net-oo-rexx package
                   rexxdebugger, which allows you to debug any Rexx program in 
a GUI; hint: you
                   could use the name of one of your Rexx programs instead

                 * rexx rexxdebugger packages/rexxdebugger/tutorial.rex ... 
this will use the
                   net-oo-rexx package rexxdebugger with a very nice 
tutorial.rex file, explaining
                   how to use the rexxdebugger (very impressive!)

                 * rexx tracetool -tr testoorexx.rex ... this will use the 
net-oo-rexx supplied
                   "tracetool.rex" to run "testoorexx.rex" with "trace result" 
and save a tracelog
                   in a file named "testoorexx.rex_trace.xml"; hint: you could 
use the name of one
                   of your Rexx programs instead

                     o rexx tracetool -s testoorexx.rex_trace.xml ... will 
display the tracelog
                       formatted as "trace r" would format it
                     o rexx tracetool -p testoorexx.rex_trace.xml ... will 
create a profile from
                       the tracelog
                     o rexx tracetool -p -sl testoorexx.rex_trace.xml ... will 
create a profile
                       SQLite script from the tracelog, such that you could use 
it to analyze the
                       tracelog data for profiling

                 * rexx -e "call bsf.cls;say .bsf4rexx~display.version" ... 
will execute the Rexx
                   program supplied in the string, which will display the 
version of ooRexx,
                   BSF4ooRexx, Java and operating system in use (BSF4ooRexx is 
one of the packages
                   contained in net-oo-rexx)

---

The net-oo-rexx packages are meant to use the latest versions of ooRexx, NetRexx and the packages without a need to install them globally on your system. Since ooRexx 5.0 it is possible to have different versions of ooRexx 5.0 and higher running in parallel on the same computer. Therefore, you can use different versions of net-oo-rexx in parallel on the same computer, if need be.

It does not take much for anyone to a) download, b) dequarantine, c) unzip, and d) run "setup.cmd" (Windows) or "./setup.sh" (Unix). After this the above commands should run immediately on *your* computer!

It is easy and adds an incredible wealth of utility to your Rexx world! :)

---rony



On 2025-09-05 3:38 p.m., Rony Flatscher via groups.io wrote:
There are a new net-oo-rexx packages (Windows, MacOS, Linux) available for download from: https://wi.wu.ac.at/rgf/rexx/tmp/net-oo-rexx-packages/

Each net-oo-rexx package can be used to use (or check-out) the latest versions of ooRexx and some helpful packages for it (like BSF4ooRexx, an ooRexx-Java bridge) and NetRexx.

Unquarantine the Windows ("powershell unblock-file *") and MacOS (use 'xattr' to learn the name of the quarantine attribute and then 'xattr -d' to delete it) net-oo-rexx packagaes before unzipping them. Then run "setup" and you can already use ooRexx with BSF4ooRexx, or NetRexx.

One important package is "oorexxshell", which is a *great*, versatile, very useful shell for Windows, MacOS, and LInux by Jean Louis Faucher.

See the enclosed "readme*txt" files for more information.

---rony

_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to