OOoWPS100.wpi - first experience

Hi all,

Read a first look at the newly released package at my webpage 
http://andreas-ludwig.info/index.php?page=ooo-wps-integration

The most important things:

1. Install the integration package into the same dir as OpenOffice.org
itself. The default install path ([Boot]\ecs\system or something like this)
does NOT work, because the path to soffice.bin seems to be hard coded in the
dll (why?)

2. You need to change the file type of any old document to OOo????File (With
??? being Writer, Calc, ...) before you can see the new info page in the
settings notebook.

3. Drag and drop of printing means drop to ANY printer object and it prints
to what ever printer you set IN THE DOCUMENT (for instance the last printer
you printed to before saving the last time). So you cannot determine where to
print to with dragging to a specific printer object. :o(
Here I actually have to load the document into OOo first and THEN can drag
the file into the printer object to print (?!). When I just drop it with OOo
not running, the program will start, load up a BLANK page and do nothing.
Unfortunately these two things pretty much defeat the purpose of the feature
in the first place...

Anyways, it's a first step into the right direction and a good sign of good
work in progress, but there needs to be a fixed version 1.1 soon.

Have fun
Andreas



-- 

Andreas Ludwig
Vancouver, BC
using PMINews 2 on eCS 1.2R German!
http://andreas-ludwig.info/

On Sun, 18 Nov 2007 17:09:25 +0100, Sjoerd Visser wrote:

>> Yeah, I figured this out as well.
>> But additionally the templates folder is no longer populated once
>> the classes are installed. This causes a hang of the whole WPS.
>> After uninstalling the classes, all is fine again.
>
>I can confirm this. Checkini /c did not correct it, My advise is to stay 
>away from the OOOrg WPS package  as long it destabilizes the WPS.

Hm. I cannot confirm this. My system got instable once, but I thought this to
be a problem with the multiple WPS restarts (using WarpIN's built in WPS
reset) rather than the class. 

I'm running now for almost 2 days and must say that loading performance and
functionality actually improved with the classes installed. Before I could
get hangs with second instances of soffice.bin invoked when I double clicked
on say a powerpoint file while a OOo writer file was open. This problem is
completely gone here. 

The templates are all still available - both the generic OS/2 ones and the
OOo templates (they are just a little odd, as OS/2 and eCS do not need
special file formats that ask you to 'save as' for a new document. You used a
template to create a NEW document anyways. But I guess this could be easily
changed with some spare time on my hands ;o)

Cheers
Andreas

-- 

Andreas Ludwig
Vancouver, BC
using PMINews 2 on eCS 1.2R German!
http://andreas-ludwig.info/

On Mon, 19 Nov 2007 00:21:25 +0100, Sjoerd Visser wrote:

>When I opened \ecs\system\OOoWPS\program\ooodoc.dll with PMDLLL 
>(checking for dependencies) PMDll reported no problems. Only non OOOrg 
>binaries were called.
>
>But the \program\ in the path suggests indeed that the program folder of 
>the OOORG binaries should be its meant destination.

Interesting. I could not get soffice.bin to load whenever I installed the dll
into ANY other directory than where OOo is. Don't you get a meaningful error
message telling you something about path not found?

Cheers
Andreas

-- 

Andreas Ludwig
Vancouver, BC
using PMINews 2 on eCS 1.2R German!
http://andreas-ludwig.info/

> 1. Install the integration package into the same dir as OpenOffice.org
> itself. The default install path ([Boot]\ecs\system or something like
this)
> does NOT work, because the path to soffice.bin seems to be hard coded in
the
> dll (why?)

Yeah, I figured this out as well.
But additionally the templates folder is no longer populated once
the classes are installed. This causes a hang of the whole WPS.
After uninstalling the classes, all is fine again.

The preview feature in the properties notebook seems to work here as well.
But as long as the hang is not resolved these classes stay away from
my desktop. Haven't they tested this stuff upfront? At least such simple
stuff should have been discovered.

> 3. Drag and drop of printing means drop to ANY printer object and it
prints
> to what ever printer you set IN THE DOCUMENT (for instance the last
printer
> you printed to before saving the last time). So you cannot determine where
to
> print to with dragging to a specific printer object. :o(
> Here I actually have to load the document into OOo first and THEN can drag
> the file into the printer object to print (?!). When I just drop it with
OOo
> not running, the program will start, load up a BLANK page and do nothing.
> Unfortunately these two things pretty much defeat the purpose of the
feature
> in the first place...

Heiko Nitzsche wrote:
>> 1. Install the integration package into the same dir as OpenOffice.org
>> itself. The default install path ([Boot]\ecs\system or something like 
>> this)
>> does NOT work, because the path to soffice.bin seems to be hard coded 
>> in the
>> dll (why?)
> 
> Yeah, I figured this out as well.
> But additionally the templates folder is no longer populated once
> the classes are installed. This causes a hang of the whole WPS.
> After uninstalling the classes, all is fine again.

I can confirm this. Checkini /c did not correct it, My advise is to stay 
away from the OOOrg WPS package  as long it destabilizes the WPS.