Hi Rony, Am 14.07.20 um 16:34 schrieb Rony G. Flatscher: > Hi Matthias, > > On 14.07.2020 16:14, Matthias Seidel wrote: >> Am 14.07.20 um 16:03 schrieb Rony G. Flatscher: >>> Hi there, >>> >>> yesterday I intended to test the ooRexx macro language oxt file against the >>> MacOS Developer Build >>> (4.2) to test whether <https://bz.apache.org/ooo/show_bug.cgi?id=127966> is >>> fixed. >>> >>> As the install script that has been working for more than 10 years on OO >>> (and LO) failed I looked >>> into the cause and saw that the "soffice" (and "unoinfo") executable now >>> resides in >>> "/Applications/OpenOffice Developer Build.app/Contents/*MacOS*/soffice" >>> whereas it used to be >>> located in "/Applications/OpenOffice.app/Contents/*program*/soffice". >> As it is a Developer Build the PRODUCTNAME is "OpenOffice Developer Build" >> I am pretty sure that your script works as expected with a "normal" build. > Yes, this is o.k. (not the problem). > > The problem is that in the "Contents" directory there is no "program" > subdirectory in the developer > build, rather it is named "MacOS" instead. I realized that now (see my other mail) > > The installation script assumes on the Mac that "soffice" and "unoinfo" are > located in > "/Applications/OpenOffice[ Developer Build].app/Contents/program". (If this > is intentional I would > change the script accordingly.) I don't think that was intentional. Let's wait for a "normal" build. > >> Maybe there is a possibility to get the script recognize the difference? >> (the same would apply to a Beta Build) >> >> @Jim: Could you provide some plain mac builds? >> >> BTW: I always wanted to test your ooRexx extension, Rexx was my first >> "language" on OS/2. > You would be surprised! ;-) > > Actually "Object-oriented Rexx" was created as an object-oriented replacement > of "Rexx" for OS/2 > Warp by IBM. The Windows version generated quite some income for IBM when > their user base switched > from OS/2 to Windows and learned that there were tons of Rexx programs that > also needed to run on > Windows. > > Later IBM handed the source code over to the non-profit SIG "Rexx Language > Association" which then > released an open-source version of it under the name "Open Object Rexx" > (ooRexx) in 2005. Ever since > then it got steadily improved and the current 5.0 (officially in beta but in > release quality) > release is imminent. > > The OpenOffice plugin of ooRexx was created using the Java-bridge > "BSF4ooRexx" (Apache BSF and > ooRexx), which also has its roots in OS/2 believe it or not: Java played an > important role for OS/2 > and portable (even GUI) applications became possible with the Java bridge > such that Rexx programs > developed under OS/2 ran unchanged on Windows (and vice versa). > > Today the Java bridge BSF4ooRexx is bi-directionally complete, i.e. Java > classes and Java objects > are camouflaged as ooRexx classes and objects, sending them ooRexx messages. > On the other hand Java > code can invoke ooRexx methods without realizing that the implementation is > done in ooRexx (e.g. > when extending Java classes in ooRexx or implementing abstract Java methods > in ooRexx). > > Like with Rexx ooRexx is a dynamically typed, interpreted language with a > "human-centric" syntax, > such that it can be learned quite fast and programs can be understood quite > easily. > > So, if you have interest and a little bit of time, it may be very worthwhile > to look into it. > Creating ooRexx-macros and/or using OpenOffice from ooRexx programs is > straight-forward and quite easy.
If I only had the time (and knowledge)... ;-) But in fact I still use OS/2 (ArcaOS in VirtualBox) with AOO installed. Regards, Matthias > > ---rony > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org >
smime.p7s
Description: S/MIME Cryptographic Signature
