Le 16/02/11 12:07, rony a écrit :

Hi Rony,

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.


> 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 ?


> 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.


Anyway, I will check out the stuff on the Wien server - a book would be
a real plus !!! :-))

Alex


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to