Hi there,

FYI the announcement to the "Rexx Language Association
(http://www.RexxLA.org)" members, informing them of a new version of
BSF4Rexx, which includes updated support for OOo scripting and OOo
macros using the scripting language ooRexx
(<http://www.oorexx.org/download.html>).

ooRexx itself is written in C++, the BSF4Rexx package enables ooRexx to
camouflage Java as ooRexx (bridging ooRexx and Java in both directions).
The ooRexx interaction with OOo uses the OOo Java bridge, hence the
packaging of the OOo support with BSF4Rexx.

---rony


-------- Original Message --------
Subject:        New BSF4Rexx released ...
Date:   Fri, 19 Sep 2008 18:25:16 +0200
From:   Rony G. Flatscher <[EMAIL PROTECTED]>
To:     RexxLA Members mailing list <[EMAIL PROTECTED]>



Hi there,

There is a new distribution of BSF4Rexx available from the official
site, since today: <http://wi.wu-wien.ac.at/rgf/rexx/bsf4rexx/current/>.

Please de-install your current BSF4Rexx before installing the new one
(by running the previously created "uninstallOOo" and "uninstallBSF"
scripts).

To install: just download
<http://wi.wu-wien.ac.at/rgf/rexx/bsf4rexx/current/BSF4Rexx_install.zip>,
unzip the archive to a directory of your choice and follow the "readme"
instructions for quickly installing BSF4Rexx.

Some notable changes compared to previous versions:

    * If taking advantage of "BSF.CLS" each string value returned from
      the Java side will have either the string "<O>" or "<S>"
      prepended, which will get stripped automatically by all routines
      and classes of "BSF.CLS".
      However, if you mix oo- and classic-Rexx style of interacting with
      Java (i.e. using the external Rexx function BSF() directly), then
      you need to get rid of the first three bytes that you receive from
      the Java side. The prepending is controlled by the  new BSF()
      subfunction named "bsfPrefixReturnValue" which takes either .true
      or .false (cf. reference card).
    * the fully qualified path to the BSF4Rexx script is now supplied,
      if available, such that PARSE SOURCE can be used,
    * if adding an event handler to a Java class and supplying a wrong
      event name, then the error message will list all event set and
      their events to help the programmer correct the mistake (can be
      quite tedious to figure that one out),
    * when using BSF.CLS, then any error messages that have occurred on
      the Java side will be made available with the local environment
      symbol ".BSF_ERROR_MESSAGE", no matter whether displaying those
      error messages are suppressed or not (cf. external BSF-function
      named "BsfShowErrorMessage()" on the reference card),
    * added entries "file.separator", "line.separator", and
      "path.separator" to the ".BSF4Rexx" directory, values retrieved
      from Java's System class which makes sure that the values are
      supplied according to the platform BSF4Rexx is running on
    * added new external Rexx function "BsfDetach()" to make the
      multithreading support for BSF4Rexx complete.

Some notable changes to the OpenOffice ("OOo") support (supplied via
UNO.CLS) compared to previous versions:

    * added public routine "uno.getScriptMetaData()", which allows to
      retrieve the OpenOffice metadata script object, if a Rexx script
      got invoked as a macro by OOo, cf. reference card for its arguments,
    * supplies script path, such that PARSE SOURCE can be used to
      retrieve the script's location,
    * added convenience routine "uno.createProperty(name[,value])" to
      ease creation of property value objects,
    * "template.rex": template code for new macros via the OOo UI now
      contains commented code to demonstrate how to address all kind of
      document types and how to react upon errors supplying the error
      messages in popups,
    * gives additional and very detailed error information aimed at
      helping the programmer to quickly realize the error and possible
      resolutions,
    * added public convenience routines & methods
      "uno.getInterfaceName()", "uno.supportsService(name)",
      "uno.supportsInterface(name)",
    * added supporting code for interacting with property values through
      the XPropertySet interface: property names now do not have to
      match the case, property values do not have to be explicitly boxed.

Regards,

---rony


Reply via email to