Hi Alex, On 16.02.2011 14:47, Alexander Thurgood wrote: > Le 16/02/11 12:07, rony a écrit : > > Thanks for the links, will check them out. As it happens, the ports > mechanism on Mac has oorexx so I have done installed it through the > ports system. > Yes, but be aware that the version there is still 4.0.1.
Currently, there is no official version for 4.1.0 for MacOSX, although one can build the interpreter from the oorexx svn's "main/releases/4.1.0", though I would suggest to build it from "main/branches/4.1" which incorporates a fix for a bug, that I uncovered while testing the port of ooRexx 4.1.0 and BSF4ooRexx to MacOSX. The port of BSF4ooRexx to MacOSX is not yet publically available, if you want to experiment with it, please drop me a note and I upload it such that you could download it. Currently, the support for OOo is developed/tested, which basically means setting up the environment for Java correctly. There are two students who have taken on the task to create (mostly GUI-based) installers for BSF4ooRexx for various platforms, including MacOSX. Probably, by the end of March an official release can be published (hoping that OOo 3.4 had fixed the Java-bug, such that the "Edit"ing of scripts would work on MacOSX). >> Currently the port of BSF4ooRexx (which includes the OOo integration) >> for MacOSX is in the works. The 32- and 64-bit versions work on MacOSX, >> the OOo-support is now being developed (it seems it is mostly dependent >> on the correct environment settings for Java). >> > Hmmm, I was wondering whether only the 32bit version of BSF4ooRexx would > work with OOo because it is only compiles as 32bit on the Mac at the > moment as far as I know ? > Yes, you must use the 32-bit version of ooRexx as OOo is only available for 32-bit on MacOSX. BSF4ooRexx itself will be able to serve both, 32- and 64-bit ooRexx and Java. >> Unfortunately, it seems according to Christian's URL to the respective >> issue <http://qa.openoffice.org/issues/show_bug.cgi?id=92926>, that >> awt/swing on MacOSX is currently not possible, because OOo does - >> against Apple's documentation dating back to 2005 ! - not load the JVM >> in a separate thread. Hopefully, this is understood as a true >> showstopper for OOo 3.4 by the developers, such that this defect gets >> fixed on MacOSX as soon as possible! >> > > Until recently, OOo was still using an outdated and deprecated mechanism > for finding the JVM in the first place, which caused it to not recognise > the presence of Java on the system, as the automatic update by Apple to > Java 1.6.0_22 showed. That has since been fixed, but the issue had been > notified in advance by Apple, and the NeoOffice project had taken the > necessary steps to avoid the problem, whereas it was only addressed on > OOo when Mac users started filing bug reports that they couldn't get OOo > 3.3 RCxx to function properly on their systems anymore, due to the huge > dependencies on having a recognised JVM. It is symptomatic of the > resource allocation problem IMHO and a shame, but there you go. > This should not be the case, as full and professional support for MacOSX is important for that segment to be able to fully accept OOo. (And, hey, this is mainly Sun/Oracle, the inventor of Java, so that should not be a problem at all!) > Anyway, I will check out the stuff on the Wien server - a book would be > a real plus !!! :-)) > Will report, once the first book is done (hopefully by the end of this summer). ---rony --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
