trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: May 2012

Re: [trinity-devel] apache OpenOffice TDE Integration?

From: "David C. Rankin" <drankinatty@...>
Date: Wed, 16 May 2012 12:59:33 -0500
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 :)

-- 
David C. Rankin, J.D.,P.E.