Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: alu on July 20, 2009, 05:27:38 PM
-
is it possible to split the openoffice extension in order to have a separate writer, a separate xcalc, and so on?; i come up to this idea remembering dsl which, as i believe, did offer this opportunity in order to save ram usage.
-
Does it make a big difference if you use the tczl version?
-
with the oo2.tclz extension, i get 115.6 MB loaded, while i am using writer only; if i had to load writer only, i would come up with around 65 MB, i think; it would make a big difference for me
-
why not try abiword ?
and gnumeric for spreadsheet.
-
i'd like to use it (abiword), but even if i am not an experimented user of abiword, it has not some functionalities that i am used to use with openoffice; f.ex. quotation marks and apostrophes are not supported in several languages, and i am writing in almost 4 languages for which i need 4 different quotation marks' and apostrophes' styles without using the insert menu function or the copy/paste one at each time. Otherwise, my experience with abiword was not so good (maybe it's me) as f.ex. when i have to import a doc document with graphics and so on; it takes a long time to load, and it forces me to reformate the document in most of the cases (footnotes messed up each time, and to reformate footnotes with abiword is really a pain). Last but not least: it will be a detail for you folks, but the (smooth or non-smooth) scrolling functionality in abiword is really something that sucks. That's why i got back to openoffice writer which deserve my purposes without too much time lost. So spliting the oo2.tczl extension would enable me to reduce memory storage without any loss of productivity.
-
BTW OO 2.3 is rather old now, current version is 3.1.0
-
yes, but i think that oo3.1 would be much difficult to split (a guess from me there), and frankly, oo2.3 works very well; it has in my view only one big issue which is it can not read docx files; about that last point, i would agree with you, and would also say that we need a oo3.1 extension; but that's already too much requests within one post.
-
There are some more changes in 3.x but not so significant for the every day use.
For .docx files you can use a 3rd party tool, odf-converter-integrator for example:
http://katana.oooninja.com/w/odf-converter-integrator
-
mmmhh... do i have to compile it, or is it a shorter way to get that odf-converter-integrator working; thanks anyway Bella for the tip, even if i remain sceptical with 'translations' apps. you know, if tex would offer better ways to deal with doc and other common sense formats, i would have been stuck at that. simplicity, no brain washing, but your know the story for sure
-
I'm not using it, but guess it must be compiled and converted to a tce/tcz extension.
-
I've started to look at openoffice-3.1 - it seems to start compiling OK (after a couple of hacks), but I had to <ctrl-c> out as 2GB ram is (obviously) not enough.
Once I line up some hd space to compile, I'll try to compile the whole thing and test it works before trying to split the components.
-
People around have recommended Go-office as the "better" OO.o fork currently. Maybe starting from it would be better? (go-oo.org)
-
Looks good at first glance. Lets see it.
-
I've started to look at openoffice-3.1 - it seems to start compiling OK (after a couple of hacks), but I had to <ctrl-c> out as 2GB ram is (obviously) not enough.
Once I line up some hd space to compile, I'll try to compile the whole thing and test it works before trying to split the components.
I agree go-office looks like a better starting point.
-
Hmm...
making .dpslo
----------------------------------------------------------
- start unit test on library ../unxlngi6.pro/lib/libbasegfx_tests.so
----------------------------------------------------------
testshl2 -sf /tmp/mkjJKbjj -forward ../unxlngi6.pro/bin/ ../unxlngi6.pro/lib/libbasegfx_tests.so
terminate called after throwing an instance of 'CppUnit::StubException'
dmake: Error code 134, while making '../unxlngi6.pro/misc/unittest_succeeded'
ERROR: Error 65280 occurred while making /mnt/sdb1/usr/src/OOO310_m11/basegfx/test
rmdir /tmp/12036
dmake: Error code 1, while making 'build_instsetoo_native'
Command exited with non-zero status 255
real 33m 43.52s
google doesn't find an answer to this
-
fwiw, there is a similar tracker entry: http://www.openoffice.org/issues/show_bug.cgi?id=98159
-
Thanks, I'd seen it - 'trouble is, there's no solution yet.
I'll try with gcc-4.4.0 tonight.
-
indeed, go-Office seems nice; i have looked at their servers, and packages seems to be really small, or have i missed smthg
-
At first glance, it seems the go-oo download is a front-end for compiling the same 175mb behemoth?
-
mmmhhh google seems to return different results for go-oo, varying from 108mb to 180mb, but indeed, it remains bigger than expected
-
It is an OO variant, do no expect miracles in size.
-
Hi!
Hope you get it done Juanito. That would really make the day. It would probably turn more eyes from the linuxcommunity towards MC and TC also. So, good luck in your endeavour to make an openoffice extension!
Have fun guys advancing this nice distro,
meo
-
Not looking good I'm afraid - gcc-4.4.0 gives the same error and the openoffice bug report says gcc-3.x cannot be used to compile openoffice-3.1 either.
'Makes you wonder how they compiled openoffice-3.1 in testing...
-
Juanito, any related issue with the lack of enable handle exceptions in gcc-4.0 (in opposite to gcc-3.0)?:
(terminate called after throwing an instance of 'CppUnit::StubException')
See topic: http://forum.tinycorelinux.net/index.php?topic=2360.0
Regards.
(with only 1 Gb of RAM I could not compile gcc-4.X to try)
-
It could be related, but the original openoffice bug report was from a system that has no connection with tinycore...
-
Anyway, It is possible to get a gcc.4.x version with the enable handle exceptions, just for any tries?
It will be much appreciated.
Thanks
-
I've compiled gcc with and without "-fno-exceptions" (and "-fno-rtti") with the same results...
Any suggestions would be welcome
-
Hi guys!
I hope that someone could come up with a solution because openoffice is kind of connected with linux distributions. I think that it is a vital part of a pc-os to have some kind of office solution. If that could be done for MC and TC I think a lot of people in the linux-community would react very positive to that. A good office solution is what many looks for to even consider using a certain distribution. So it would be a very good thing if openoffice could be compiled into an extension for MC and TC.
Have fun extending this incredible distro,
meo
PS I'm very sorry that I can't come up with something constructive regarding OO myself DS