On Wed, 19 Jan 2005 20:40:32 +0100
Jochen Staerk [EMAIL PROTECTED] wrote:
Hi,
I always thought that adding the class path to your manifest would
be
sufficient and has the same effect than using the cp-commandline
switch
but I could be completely mistaken.
I thought a MANIFEST like
Hi Simon,
and thanks for your answer and the classloader-sample-code,
normally if you have the oo-jars (all from oo-home/program/classes) in
your classpath (manifest or CLASSPATH or with the -cp switch) the
libraries are found. There is a helüper-class, which load the
If you want to deploy your
Hi Simon,
I mean the order can changed by newer releases. The officebean.dll
depends on MSVCR70, UWINAPI, sal3, jpipe (this is the order to
load it). But this can be changed with OO2.0 or 1.1.x.
I have not looked at OO2.0 and I don't know if the new OfficeBean will
handle this self,
Yes,
Following Michael Hoenig's advice (unanswered questions), here I am again.
AIM: check the current API's support for prototyping a grammar-checker API
externally, i.e. without messing with OOo's source.
MY QUESTIONS TO API DEVELOPERS REGARDING THE CURRENT API'S CURRENT FEATURES (not
necessary
I have been blathering on for some time about the need for an
environment that facilitates collaborative development of OOo macros. I
have decided (being rather stupid I needed others to recommend this) to
try using Issue Tracker.
As an experiment I have cobbled together a macro for finding OOo
