Tim,
As with Libre has anyone looked at dialogs for OpenOffice? Apache openoffice 3.4 was just released and it works great:
http://www.openoffice.org/download/
It is much.., much... more responsive that LO and avoids a couple of nasty formatting bugs that affect line/character spacing in LO. Apache OO does have a nice GTK file browser by default (like the tde browser), but it would be nice to have an integrated browser for AOO as well.
On 14 May 2012 17:02, David C. Rankin drankinatty@suddenlinkmail.com wrote:
Tim,
As with Libre has anyone looked at dialogs for OpenOffice? Apache openoffice 3.4 was just released and it works great:
http://www.openoffice.org/download/
It is much.., much... more responsive that LO and avoids a couple of nasty formatting bugs that affect line/character spacing in LO. Apache OO does have a nice GTK file browser by default (like the tde browser), but it would be nice to have an integrated browser for AOO as well.
For Pete's Sake! Haven't you been keeping up with the news? (old news). Most developers ditched OO.org because their cough cough great parent company was causing more problems than they resolved. LibreOffice forked with a open source and group run mentality. No more corporate crap. Steadily they've been whittling away at the cruft of years and years of badly written code and to much damned Java. Then Oracle ditches OO.org to apache who for some inexplicable reason takes the project on. Down with Open Office! *
Using OO.org would be like sending patches to the xfree86 project.
Calvin
* probably incorrect in some places, a bit biased
On 05/14/2012 07:43 PM, Calvin Morrison wrote:
For Pete's Sake! Haven't you been keeping up with the news? (old news). Most developers ditched OO.org because their cough cough great parent company was causing more problems than they resolved. LibreOffice forked with a open source and group run mentality. No more corporate crap. Steadily they've been whittling away at the cruft of years and years of badly written code and to much damned Java. Then Oracle ditches OO.org to apache who for some inexplicable reason takes the project on. Down with Open Office! *
Using OO.org would be like sending patches to the xfree86 project.
Calvin
- probably incorrect in some places, a bit biased
Yes, Yes, Yes, No - not any longer, just the opposite, different conclusion.
Apache has done a great job with OO, so all that Oracle did, or didn't do, with it -- is irrelevant now.
I cannot currently use LO due to the formatting bug leaving LO incapable of reproducing the 1000's of OO documents I have correctly. (Yes -- it does make a big difference to the court if they ask for a copy of an order or judgment and paragraph 46 is now on page 7 instead of page 6) I opened this bug with LO over a year ago and typical from that project -- nothing has been done.
OO, on the other hand, continues to accurately reproduce documents from all prior versions of OO - that is the bare minimum of what a word processor must do.
So, for different reasons, I come to a different conclusion. The Apache project is an "Open Source" project in the truest sense of the term -- and we as packagers/developers should embrace their project -- we certainly don't having a problem using their web server....
Another Giant ding against LO is it is just S L O W compared to OO. Startup time, document open time, etc.... There have been some very poor design choices made in LO that have led to these issues.
The one thing required in any serious document production environment is that a word processor accurately reproduce files it created in the past. If it doesn't -- it is of no use to me.
The latest build for AOO is in AUR -- give it a shot -- I bet it will change your opinion -- then figure out the coding for the Qt3 dialogs :)
On 05/14/2012 04:02 PM, David C. Rankin wrote:
Tim,
As with Libre has anyone looked at dialogs for OpenOffice? Apache openoffice 3.4 was just released and it works great:
http://www.openoffice.org/download/
It is much.., much... more responsive that LO and avoids a couple of nasty formatting bugs that affect line/character spacing in LO. Apache OO does have a nice GTK file browser by default (like the tde browser), but it would be nice to have an integrated browser for AOO as well.
I talked with the Apache folks about TDE integration in OpenOffice. They said if somebody will develop and maintain the patch, they will include it in OpenOffice. My contact was with Ariel Constenla-Haile arielch at apache.org. I don't know if the old kde3 integration would just plug-in for TDE or not and I have no idea how to go about it, but if we can adapt the libreoffice one for openoffice, or something similar, that would be great to have TDE support in both.
On 05/21/2012 01:10 PM, David C. Rankin wrote:
On 05/14/2012 04:02 PM, David C. Rankin wrote:
Tim,
As with Libre has anyone looked at dialogs for OpenOffice? Apache openoffice 3.4 was just released and it works great:
http://www.openoffice.org/download/
It is much.., much... more responsive that LO and avoids a couple of nasty formatting bugs that affect line/character spacing in LO. Apache OO does have a nice GTK file browser by default (like the tde browser), but it would be nice to have an integrated browser for AOO as well.
I talked with the Apache folks about TDE integration in OpenOffice. They said if somebody will develop and maintain the patch, they will include it in OpenOffice. My contact was with Ariel Constenla-Haile arielch at apache.org. I don't know if the old kde3 integration would just plug-in for TDE or not and I have no idea how to go about it, but if we can adapt the libreoffice one for openoffice, or something similar, that would be great to have TDE support in both.
For now, if you have the GTK2 libraries installed along with TDE, you can use the GTK file chooser with OpenOffice (dual pane, folders on left, files on right -- quite good).
To use the GTK dialogs with OpenOffice on TDE, in your bashrc:
export OOO_FORCE_DESKTOP=gnome
The start OO and choose:
Options->OpenOffice.org->General, then uncheck
[ ] Use OpenOffice.org Dialogs
You will then have usable file dialogs in OO. (the same should work in LO)
To use the GTK dialogs with OpenOffice on TDE, in your bashrc:
export OOO_FORCE_DESKTOP=gnome
The start OO and choose:
Options->OpenOffice.org->General, then uncheck
[ ] Use OpenOffice.org Dialogs
You will then have usable file dialogs in OO. (the same should work in LO)
If we rebuild LO/OO with the TDE patch, do we still need this environment variable? If yes, then if I read the TDE patch correctly, the correct parameter is "tde."
Darrell
On 05/21/2012 03:03 PM, Darrell Anderson wrote:
If we rebuild LO/OO with the TDE patch, do we still need this environment variable? If yes, then if I read the TDE patch correctly, the correct parameter is "tde."
Darrell
Yes,
Another way is to modify the .desktop files for soffice (writer, calc, impress, etc..) so the Exec= line reads:
Exec=OOO_FORCE_DESKTOP=tde soffice %U
The alternative would be to modify your bashrc or the system wide bashrc.local to:
export OOO_FORCE_DESKTOP=tde
In the past, that is what has been required to specify the filechooser. I.e.:
OOO_FORCE_DESKTOP=gnome soffice OOO_FORCE_DESKTOP=kde soffice OOO_FORCE_DESKTOP=kde4 soffice
now looks like we can add:
OOO_FORCE_DESKTOP=tde
Tim, do you know if this same patch will work with openoffice? If so, I can try a rebuild of OO with it and pass it along to OO if it works.
On 05/21/2012 03:03 PM, Darrell Anderson wrote:
If we rebuild LO/OO with the TDE patch, do we still need this environment variable? If yes, then if I read the TDE patch correctly, the correct parameter is "tde."
LO will automatically detect a running TDE session--no need to manually set environment variables unless you are running under LXDE or some other desktop.
Tim, do you know if this same patch will work with openoffice? If so, I can try a rebuild of OO with it and pass it along to OO if it works.
You can try...one build environment (for LibreOffice) is enough for me. Getting everything downloaded and built for something the size of LO/OOo is not exactly fun.
Bear in mind that OOo probably uses a different build system at this point than LO does, so the patch probably won't even apply. You would have to manually cobble together the appropriate build system patches to make it compile.
Tim