970
votes
994
29
24
89
votes
274
100
185
Solution #2:
Help the development of a c/c++ alternatives with gtk+
Written by
jeypeyy the 19 Feb 09 at 20:04.
OpenOffice is written with "Native Widget Framework" (
http://people.redhat.com/dcbw/ooo-nwf.html ) and that might be a reason why it is so slow*. Also it integrates badly with gnome. If we helped an alternative written in c/c++ and with gtk+ it could be faster.
The developers could help developing alternatives like AbiWord and Gnumeric. There should also be an integration between those applications before Ubuntu decides to change.
*Note that I'm not sure if this really is the reason. If it's not, please leave a comment and vote this down.
OpenOffice is written with "Native Widget Framework" (http://people.redhat.com/dcbw/ooo-nwf.html ) and that might be a reason why it is so slow*. Also it integrates badly with gnome. If we helped an alternative written in c/c++ and with gtk+ it could be faster.
The developers could help developing alternatives like AbiWord and Gnumeric. There should also be an integration between those applications before Ubuntu decides to change.
*Note that I'm not sure if this really is the reason. If it's not, please leave a comment and vote this down.
-149
votes
90
37
239
Solution #5:
Use a (Optional) preloading system to quick-start Openoffice
For those people who needs faster openoffice, Ubuntu should provide a task that preloads some OOO's libraries or modules on system start, that will increase booting time but decrease OOO start time.
This behaviour should be optional.
For those people who needs faster openoffice, Ubuntu should provide a task that preloads some OOO's libraries or modules on system start, that will increase booting time but decrease OOO start time.
This behaviour should be optional.
55
votes
76
24
21
Solution #6:
Transition bottlenecked portions of OpenOffice to C/C++
Written by
Mishtal the 17 Mar 09 at 20:14.
There are ways to use C and C++ functions from interpreted languages like Java. The parts of OpenOffice that are the major bottlenecks could be transitioned to C/C++, or other compiled languages.
This gives us the benefit of keeping all the current features of OpenOffice, in addition to allowing new features to be added without significant changes in the implementation of these new features compared with the implementation of them on a non-transitioning OpenOffice
There are ways to use C and C++ functions from interpreted languages like Java. The parts of OpenOffice that are the major bottlenecks could be transitioned to C/C++, or other compiled languages.
This gives us the benefit of keeping all the current features of OpenOffice, in addition to allowing new features to be added without significant changes in the implementation of these new features compared with the implementation of them on a non-transitioning OpenOffice
34
votes
43
8
9
Solution #7:
Solution 1 but with support from Ubuntu
Written by
Basem the 23 Mar 09 at 08:14.
Open Office is great, but i cant stop feeling its starting to lag behind in terms of features...ubuntu should start giving Sun some support.
Open Office is great, but i cant stop feeling its starting to lag behind in terms of features...ubuntu should start giving Sun some support.
-4
votes
6
4
10
Solution #8:
Use Abiword instead
Abiword, while less featureful than OO, is light and fast. Plus, it's written natively in gtk, so it supports theming.
Abiword, while less featureful than OO, is light and fast. Plus, it's written natively in gtk, so it supports theming.
6
votes
6
1
0
Solution #9:
Improve Open Office to load less files
Starting the Open Office Writer 3.2 needs OS to load 1575 files. You can try this yourself:
strace -f -e trace=open oowriter 2>&1 | perl -npe 's/^[[]pid \d+[]] *//' | grep ^open | sort -u | wc -l
(Some of the files on that list are "file not found" but it still asks OS to try to load all those files.) A reasonable way to improve start up time would be to get it to load less files during startup. Whether this is implemented as Solution #1 (load files ondemand) or as some another solution (e.g. reimplement some functionality to have simpler implementation and not tons of code in a thousand separate files).
Starting the Open Office Writer 3.2 needs OS to load 1575 files. You can try this yourself:
strace -f -e trace=open oowriter 2>&1 | perl -npe 's/^[[]pid \d+[]] *//' | grep ^open | sort -u | wc -l
(Some of the files on that list are "file not found" but it still asks OS to try to load all those files.) A reasonable way to improve start up time would be to get it to load less files during startup. Whether this is implemented as Solution #1 (load files ondemand) or as some another solution (e.g. reimplement some functionality to have simpler implementation and not tons of code in a thousand separate files).