[dev] [Fwd: New BSF4Rexx released ...]

[Rony G. Flatscher]

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

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

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

To install: just download
,
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 "" or ""
  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

[dev] Reminder: IRC session on Pinnberg

[Charles-H. Schulz]

Hello,

The IRC session on the future concepts of OOo starts in twenty  
minutes, on Freenode, [EMAIL PROTECTED]


Hope to see you there !

Charles-H. Schulz.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] Can't load the Presenter Screen extension...

[Michal Sawicz]

Hi guys, I'm trying to check out the Presenter Screen extension, but
can't get it to work, I'm using OO 3 as available in the unstable
repository for opensuse, the about page says:

OOO300m5 (Build:9350)
...
Build 3.0.0.3.1

I've tried the extension in both version 1.0 and 1.0.1, both fail with
the following message:

ERROR: (com.sun.star.deployment.DeploymentException) { { Message = "Wyst
\X0105pi\X0142 b\X0142\X0105d podczas aktywacji rozszerzenia:
PresenterScreen.uno.so", Context = (com.sun.star.uno.XInterface)
@81628f0 }, Cause = (any)
{ (com.sun.star.registry.CannotRegisterImplementationException)
{ { Message = "loading component library failed:
file:///home/michal/.ooo3/user/uno_packages/cache/uno_packages/JxvKlG_/sun-presenter-screen-linuxintel.oxt/PresenterScreen.uno.so",
 Context = (com.sun.star.uno.XInterface) @0 } } } }

Any idea what am I doing wrong?
-- 
Michal Sawicz <[EMAIL PROTECTED]>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] Can't load the Presenter Screen extension...

[Michal Sawicz]

Hi guys, I'm trying to check out the Presenter Screen extension, but
can't get it to work, I'm using OO 3 as available in the unstable
repository for opensuse, the about page says:

OOO300m5 (Build:9350)
...
Build 3.0.0.3.1

I've tried the extension in both version 1.0 and 1.0.1, both fail with
the following message:

ERROR: (com.sun.star.deployment.DeploymentException) { { Message = "Wyst
\X0105pi\X0142 b\X0142\X0105d podczas aktywacji rozszerzenia:
PresenterScreen.uno.so", Context = (com.sun.star.uno.XInterface)
@81628f0 }, Cause = (any)
{ (com.sun.star.registry.CannotRegisterImplementationException)
{ { Message = "loading component library failed:
file:///home/michal/.ooo3/user/uno_packages/cache/uno_packages/JxvKlG_/sun-presenter-screen-linuxintel.oxt/PresenterScreen.uno.so",
 Context = (com.sun.star.uno.XInterface) @0 } } } }

Any idea what am I doing wrong?
-- 
Michal Sawicz <[EMAIL PROTECTED]>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] First Open Source Project

[Christian Lins]

Matthew Fehskens schrieb:
> Hello -

Welcome!

> I've always wanted to be a contributor to an open source project.  

> I want to contribute as much as possible because I believe OpenOffice.org is
> what the world needs:  a free, open-source office suite.  I have used it
> since version 1.0 and I would love to see it get as strong a market share as
> Microsoft Office currently has on the world.

You have probably noticed the contributing start page
(http://contributing.openoffice.org/) which contains the most useful
information for upcoming developers.
There are a lot of different parts of OOo, you have to decide what you
like most (or what you dislike most if it's an annoying bug that should
be fixed).

Please note that OOo is not always the best start to get experiences in
OpenSource development as the project is really huge and the structures
are often unclear to new developers.
But if you are willing to spend your time to get through this you are
welcome :-)

Regards,
Christian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]