Hi Jeff,
On 29.10.2024 17:14, Jeff Hennick wrote:
Some reports on installing net-oo-rexx.
I had it running on a Windows 11 system.
I just tried to download and run it on a Windows 10 laptop. After getting it on the memory stick,
here is the first result:
PS D:\> cd rexx PS D:\rexx> setup.cmd "creating 'run.cmd' and 'setenv.cmd'
scripts using
'setup.rex' ..." "using any rexx.exe available on this system to execute
'setup.rex'" 147 *-*
do scriptName over ("run", "setenv") -- note: scriptnames are also used for
resource names!
Error 37 running D:\Rexx\setup.rex line 147: Unexpected ",", ")", or "]"
Error 37.1:
Unexpected "," PS D:\rexx>
This indicates that there is some Rexx interpreter installed that is not at least ooRexx 5.0 which
got (surprisingly) used in this case (see below). (The error indicates that it is not able to
understand the new array syntax sugar of ooRexx 5.0.)
And when trying this again on the Windows 11,
PS D:\rexx> .\setup.cmd
"creating 'run.cmd' and 'setenv.cmd' scripts using 'setup.rex' ..."
"using any rexx.exe available on this system to execute 'setup.rex'"
'rexx.exe' is not recognized as an internal or external command,
operable program or batch file.
PS D:\rexx>
Any help on this would be appreciated. Thank you.
That is a little bit strange as the message 'using any rexx.exe available' indicates that there was
no "D:\rexx\bin\rexx.exe" found which by default should be used to run 'setup.rex'. Here the
content of 'setup.cmd':
echo "creating 'run.cmd' and 'setenv.cmd' scripts using 'setup.rex' ..."
rem use rexx.exe of this unzipped archive
IF EXIST "bin\rexx.exe" goto portable
echo "/using any rexx.exe available on this system to execute
'setup.rex'/"
rexx.exe setup.rex
goto end
:portable
echo "using 'bin\rexx.exe' (assuming portable rexx) to execute
'setup.rex'"
bin\rexx.exe setup.rex
:end
If you unzipped the zip-archive (after de-quarantizing it the Windows way) you should have created a
directory named something like "net-oo-rexx.windows.x86_64-portable-release-20240827". If so you
should go into that directory (e.g. "cd net-oo-rexx.windows.x86_64-portable-release-20240827") and
run "setup.cmd" as it then should find "bin\rexx.exe" from there.
Have you restructured the unzipped archive by any chance? If so you would be on your own as these
setup scripts depend on the unzipped directory layout and can only work if not changed.
If not change into the unzipped archive and rerun "setup.cmd" from there.
=========
Earlier this week I attempted to do it on a friend's Mac laptop. A few things I found out -- I
don't know if these are true for all Macintoshs or it is just this one machine:
* The download went automatically to the DOWNLOADS folder
That is the default location.
* Download automatically unzipped the file, so had a full directory tree in
DOWNLOADS to copy to
the memory drive
This is strange and should not happen by default.
* The given de-quarantine command removed the attribute from ONLY the top
level directory. I
had to lookup and use the recursive version (adding -r) to get all the
files:
xattr -dr com.apple.quarantine filename
Indeed, this would be needed in this case which I have not yet seen.
* This machine did not have Java installed. This gave a bunch of error
messages running setup.
Which ones?
* A check for Java should be in the instructions and early in the program so
it quits gracefully.
(After installing Java:)
Will have to check the script as it should not abend if Java is not installed. Not having Java
installed has the consequence that neither BSF4ooRexx nor NetRexx could be used as both depend on
Java being present. There is a note to that effect in the accompanying /readme_net-oo-rexx.txt/.
* The memory drive's name must be a single word. "Mac Rexx" caused problems
for setup.sh This
should be noted and/or setup have some more quotes added in places.
What exact problems?
(If you look up setup.sh there is no problem related to the drive name as no
absolute path gets used.)
(For now, I no longer have access to the Mac.)
On the Mac make sure to use the same directory layout as contained in the zip-archive such that
portable ooRexx gets used to run setup.rex.
---
Will check the scripts with these observations in mind.
Being sidetracked a lot I have not yet been able to update the net-oo-rexx package so whatever
changes get applied to the setup scripts (to setup.rex).
So please, once it is updated (may take up to two weeks) try it out and supply
feedback!
Cheers
---rony
On 8/16/2024 11:05 AM, Rony Flatscher wrote:
There was a typo: to run the debugger on your own Rexx program you should use the proper name for
the debugger, namely "rexxdebugger"! So this is the command:
run rexxdebugger myOwnRexxProgram
---rony
On 16.08.2024 16:41, Rony Flatscher wrote:
An updated version with Dom's GUI-Rexx and ooRexx debugger was just uploaded to:
<https://wi.wu.ac.at/rgf/rexx/tmp/net-oo-rexx-packages/>.
It takes two (sic!) minutes to download, de-quarantine and run it. So if you ever wanted your
Rexx or ooRexx program to be debugged with a GUI debugger, with break points, watch window of
your variables at runtime and much more, this is the opportuntiy to check it out on Windows,
Apple and Linux!
To do so you run "setup.cmd" (Windows) or "setup.sh" (Unix) which create "run.cmd"/"run" and
"setenv.cmd"/"setenv".
E.g. you could use the following command to debug your own Rexx program
'myOwnRexxProgram.rex' with:
run oorexxdebug myOwnRexxProgram.rex
You immediately get your Rexx program into the debugger, can set breakpoints, use watch windows
and much more!
It cannot get easier for you or your Rexx friends!
---rony
P.S.: This package allows for using ooRexx, all ooRexx packages - includes Dom's great
ooRexxDebugger for Windows and Unix systems - and NetRexx in parallel to your installed Rexx.
On 25.07.2024 13:21, Rony Flatscher wrote:
This is the follow-up to the "oorexx-packages" bundle that got introduced to the community
about a month ago.
This time the latest ooRexx, oorexxshell, oorexx-debugger, and - as a bit of surprise and favor
to the community - NetRexx is on board!
Needed steps: you download it, de-quarantine (see note # 1 below) the zip archive, unzip, and
run "setup," and off you go!
It cannot get easier for interested programmers, so there is no excuse for anyone not to check
it out as soon as possible!
Currently, the following 64-bit net-oo-rexx bundles are readily available for the most
important operating systems (in alphabetic order):
*
net-oo-rexx.macos.arm64-portable-release-20240724.zip
*
net-oo-rexx.macos.x86_64-portable-release-20240724.zip
*
net-oo-rexx.ubuntu2004.x86_64-portable-release-20240724.zip
*
net-oo-rexx.windows.x86_64-portable-release-20240724.zip
Here the temporary download link:
<https://wi.wu.ac.at/rgf/rexx/tmp/net-oo-rexx-packages/>
Here the content of the readme_net--oo-rexx.txt file:
"net-oo-rexx packages"
======================
This is the readme file for "net-oo-rexx", a bundling ready to use that
gives immediate access to a number of Rexx packages, like:
- bsf4oorexx (ooRexx-Java bridge for all operating systems) - dbus4oorexx
(ooRexx-DBus
bridge for Linux) - executor packages (see oorexxshell) - log4rexx (logging
for ooRexx) -
netrexx (Java in the clothes of Rexx) - nrws (NetRexx Workspace, a NetRexx
shell) - oorexx
(open object Rexx) - oorexxshell (a rexxtry.rex kind of shell for ooRexx) -
regex (powerful
regular expression implementation in ooRexx) - rexxdebugger (an ooRexx
debugger, exploits
the Java bindings on Unix)
========================
Directions in a nutshell
========================
- download the latest "NetRexx, ooRexx with packages with oorexxshell"
(net-oo-rexx-packages) zip archive from
https://wi.wu.ac.at/rgf/rexx/tmp/net-oo-rexx-packages/
- de-quarantine the zip archive (see NOTE # 1 below)
- unzip the archive
- change into the unzipped directory and enter in the system shell
Windows Unix Comment
------- ---- +------
setup.cmd ./setup.sh | creates two scripts
This will create the two scripts:
run.cmd run | allows to run
net-oo-rexx programs
setenv.cmd setenv | allows to set
environment to net-oo-rexx in Terminal
----------------------------------------------------------------------------------------
---> use the generated 'run.cmd/run' script
Windows Unix Comment
------- ---- +------
run oorexxshell ./run oorexxshell | runs oorexxshell (a
script)
run rexx testoorexx.rex ./run rexx testoorexx.rex | use ooRexx to run
testoorexx.rex
run rexx which_rexx.rex | use ooRexx to run
which_rexx.rex
run nrc -exec which_rexx.rex | use NetRexx to run
which_rexx.rex
----------------------------------------------------------------------------------------
---> use the generated 'setenv.cmd/setenv' script
Windows Unix Comment
------- ---- +------
setenv.cmd source ./setenv | sets the environment
in the Terminal to net-oo-rexx
the following commands will work on Windows as well as on Unix:
oorexxshell | runs oorexxshell
rexx testoorexx.rex | use ooRexx to run
testoorexx.rex
rexx which_rexx.rex | use ooRexx to run
which_rexx.rex
rexxdebugger packages/rexxdebugger/tutorial.rex | use ooRexx to run the
rexxdebugger with its tutorial.rex
nrc -exec which_rexx.rex | use NetRexx to run
which_rexx.rex
nrc which_rexx.rex | use NetRexx to
compile which_rexx.rex to which_rexx.class
java which_rexx | use Java to run
which_rexx.class (note: no ".class" extension!)
======================
Additional information
======================
To learn about the functionality of oorexxshell, take a few minutes and see
the
asciinema demos at [4].
First feedback
--------------
- "install this bundle, you run a small, trivial setup program, and, poof,
you have immediate access to a real trove of packages -- no additional
installation needed"
(JMB)
- "I even was able to load the JDOR handler, then "address JDOR", and then
construct one of the JDOR samples step-by-step, by manually writing the
(quoted) JDOR commands. This is very impressive, and very useful too,
from a pedagogical point of view, since it provides immediate
incremental
visual feedback for the JDOR commands. You just have to move the Java
window besides the command window and you have a fantastic experience."
(JMB)
-------------------------------------------------------------------------------
=====
NOTES
=====
---------------------------------------
NOTE # 1: Microsoft and Apple do not allow programs from the Internet to run
if they are not signed using their fee-based service citing
"security
reasons".
Therefore, before installing or unzipping open source projects you
need
to "de-quarantine" (remove the respective attributes) the zip
archives
before unzipping.
Windows: after downloading, open with a right-mouse click the
property
menu, mark the "unblock" check mark and click "apply".
Thereafter you can install or unzip the file. Or open a
command line window and run (change 'filename' to the name
of
the downloaded file):
powershell Unblock-File filename
e.g.,
powershell Unblock-File
net-oo-rexx.windows.x86_64-portable-release-20240707.zip
macOS: after downloading, open a Terminal window and run "xattr
filename"
to see the extended attributes of the downloaded file (replace
'filename' with the name of the zip archive), then issue
(again,
change 'filename' to the name of the downloaded file):
xattr -d com.apple.quarantine filename
e.g.,
xattr -d com.apple.quarantine
net-oo-rexx.macos.x86_64-portable-release-20240707.zip
---------------------------------------
NOTE # 2 for Unix versions.
In case the execution bit of shell scripts and executables got
removed,
run the supplied script makeAllExecutable.sh from the unzipped
directory:
sh ./makeAllExecutable.sh
---------------------------------------
NOTE # 3: Dual Installations (Linux & Windows)
You can use the same set of installed files to run the
net-oo-rexx
bundle under both Windows and Linux, including the Windows
Subsystem
for Linux (WSL2) and other mechanisms like VirtualBox shared
folders.
Once you have run the necessary initializer scripts (setup.cmd
under
Windows, and ./setup under Linux/WSL), you will be able to use
the
other scripts (run/setenv) under both operating systems. For
example,
you can test a program under Windows, then use the "wsl" command
to
switch to Ubuntu, and test the same program under Ubuntu, while
sharing
the same net-oo-rexx installation.
About WSL,
cf.<https://learn.microsoft.com/en-us/windows/wsl/about>
---------------------------------------
NOTE # 4: rerun the "setup.cmd" (Windows)/"setup" (Unix) script each time
the
portable files get relocated or, if on a USB stick, each time you
plug in the USB stick. This will recreate on Windows the
"run.cmd"
and "setenv.cmd" scripts, on Unix the "run" and "setenv"
scripts,
thereby adjusting them to their new location.
---------------------------------------
NOTE # 5: bsf4oorexx (ooRexx-Java bridge)
In order to load and run bsf4oorexx programsyou need to have
Java/OpenJDK on your computer and either have PATH point to the
directory where the binary file java.exe (Windows)/java (Unix)
can be
found or set the environment variable JAVA_HOME to point to the
Java
home directory in which the Java subdirectories 'bin', 'lib' and
the
like are located.
You can download Java/OpenJDK from the Internet (usually for
free),
e.g., from Amazon, azul, bellsoft, IBM, Microsoft, ORACLE, SAP,
and
many more sites (all distributions use the same Java/OpenJDK
source
code).
Please make sure to pay attention to the following two important
points:
- download the "full version" respectively the version that
includes
"JavaFX", otherwise the interesting bsf4oorexx JavaFX samples
cannot
run
- download the Java/OpenJDK version matching your operating
system
and the machine type of your computer, e.g., a 64-bit Intel
(machine
type "x86_64") Windows version download the "x86_64" (Intel,
AMD)
Windows Java/OpenJDK installation package or zip archive. If
you
use macOS or Linux then download the respective full
Java/OpenJDK
versions.
It is possible to have different versions of Java/OpenJDK
present on
your computer at the same time. The environment variable
JAVA_HOME
can then be used to point to the Java/OpenJDK directory that you
wish
to use in your current session/terminal/command line window.
This way
you can develop and test bsf4oorexx programs for different
versions
of Java/OpenJDK on the same computer.
To see what becomes possible with bsf4oorexx, check out the
samples
in packages/bsf4oorexx/samples which all get briefly described
in the
index.html file located there as well.
bsf4oorexx programs can be executed directly with rexx[.exe] or
via
Java using the shell scripts "rexxjh.cmd" (Windows)/"rexxjh.sh"
(Unix),
e.g.,
cd packages/bsf4oorexx/samples
rexxjh.cmd 1-040_list_charsets.rxj -- Windows: Java loads
ooRexx to run script
rexxjh.sh 1-040_list_charsets.rxj -- Unix: Java loads
ooRexx to run script;
rexx 1-040_list_charsets.rxj -- Rexx loads Java to
run script
Apple users please note: if running any bsf4oorexx script that
creates a GUI, then
you must use the scripts rexxjh.sh to run them.
---
If you have any questions or comments please communicate via the RexxLA
member's
mailing list (cf.https://www.RexxLA.org).
Alternatively, communicate via the ooRexx developer list (cf. [2], [3]).
[1] Portable ooRexx
5.1.0:<https://sourceforge.net/projects/oorexx/files/oorexx/5.1.0beta/portable/>
[2] ooRexx mailing list subscription
page:<https://sourceforge.net/p/oorexx/mailman/>
[3] ooRexx web mail interface to the developer mailing list:
<https://sourceforge.net/p/oorexx/mailman/oorexx-devel/>
[4] Jean Louis Faucher'sasciinema demos, at the top the demos
forooRexxShell:
<https://jlfaucher.github.io/executor.master/demos/index.html>.
Please note that these demos may use experimental extensions of Jean
Louis
executor (a special version based on ooRexx 4.2) which are not present
in the regular versions of ooRexx.
--------------
as of 20240725
Please give us feedback on what you think about this project; it has taken some time and effort
to improve, extend, and test, hoping that it benefits each Rexx developer!
Cheers
---rony
_._,_.
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
