OO.o or Go-oo?
I might be a bit slow on the uptake, but I've just discovered that there's a "new" fork of OO.o out in the wild, Go-oo.
Before downloading and installing the latest OO.o (3.0.1), I'd like to hear if anybody here have any experiences with the new OO player? Is it worth it, or should I just stick with OO.o? :) /Thomas |
I've used OxygenOffice Professional, which is the only Go-OO package that can be installed easily under Slackware.
At the time, it could open DocX files while OpenOffice.org could not. There were no other differences that mattered to me though. |
I believe Go-oo need mono?? I recall reading that somewhere, could be wrong.
|
Quote:
Quote:
|
I use GO-OO, and it's significantly faster than regular openoffice, you can also open the evil OpenXML format, and it has 3D rendering speedups. It also crashes somewhat less.
I have it installed on slamd64, not really Slackware, but I also have a slackware machine with it, and it works fine on there. I installed it locally, so I wouldn't know how to integrate it properly. |
H_TexMex_H, you please post a HowTo for downloading and installing Go-OOO? The exact steps (even which files to download) are not obvious.
|
I tried installing go-oo, but it requires pam :(
|
Quote:
I just downloaded ooo-build-3.0.0.3.6.tar.gz and could get it to configure by adding "--disable-pam". I did not try the next step as I'm still exploring other configure options. If someone can recommend some options for slackware, I'd love to see them here! |
Quote:
1) Make a new directory where you want to download the packages. 2) Go into there and make a new file called 'packages.txt', and paste this into there: Code:
ooobasis3.0-base-3.0.0-9358.i586.rpm Code:
wget -i packages.txt -B http://go-oo.mirrorbrain.org/stable/linux-i586/3.0/ Code:
for i in *.rpm Global install: This will result in an 'opt' directory. You can now make a new directory, move 'opt' into there, then run 'makepkg go-oo-2.0.tgz' (or similar) inside that new directory to make an installable package. 'installpkg' the package. Or you may be able to put the rpms in a tgz and use a Slackbuild as they have the same titles as openoffice ones. These rpms would have to be in an RPMS subdirectory. Local install: Copy the 'opt' directory somewhere stable and symlink 'soffice' into your PATH. |
Thanks for the howto, I'm going to have a bash at modifying the OO.org Slackbuild for this. Just a quick question first - won't a non-KDE user also need the freedesktop package?
Code:
./openoffice.org3.0-freedesktop-menus-3.0-9358.noarch.rpm |
Quote:
Also, note that you will need an extension in order to spellcheck english text. Use the extension manager to install it. |
Quote:
Thought I would give it a go with the latest version, 3.1.1, so I made the appropriate changes to the text file and ran "wget ...." and that ran well, no problems . Ditto the second step and the "opt" directory was created. I then made a directory, in this case, go-ootwo and moved the new opt directory to it. However, when I ran 'makepkg go-oo-3.1.1.tgz' it returned the error message, "ERROR: Can't make output package in current directory." So where do I go next? I'll try and make another folder and direct the make package to it and see what happens. Thanks. |
try:
Quote:
|
Quote:
BTW, Go-OO is faster and "smoother" than the "original" OpenOffice. I did have to manually add it to the KDE menu. "They" claim it is suppose to bit more "multi-media friendly," so I was hoping it would do a better job of playing the sound files in pps/ppt slideshows, but that was not the case, unfortunately. |
FYI:
Just for chuckles I removed the go-oo package, downloaded the freedesktop menus file mentioned by Eternal Newbie, added it to the list, and rebuilt and installed the new package. This time the menus were automatically created. Thanks H_TexMex_H, External Newbie, Speccy, and everyone in this thread! :hattip: |
All times are GMT -5. The time now is 07:08 PM. |