Message: previous - next
Month: August 2011

Re: [trinity-devel] LibreOffice 3.4.2

From: "Timothy Pearson" <kb9vqf@...>
Date: Tue, 16 Aug 2011 21:07:16 -0500
> On Wednesday 17 August 2011 04:15:03 Timothy Pearson wrote:
>> > There is no support for KDE3 file picker dialog boxes. No option even
>> > exists in the Options.
>> >
>> > I'm using 3.5.10, which is not Trinity, but I'm guessing if the
>> upstream
>> > RPM from ODF is like this then Trinity likely gets miffed too.
>> >
>> > How do we convince the ODF developers to directly provide KDE3/Trinity
>> > support upstream when they build their official release?
>> >
>> > Darrell
>> >
>> By providing a plugin that is maintained by the official TDE project.
>> That is on our to-do list, but has not yet been started.
> What plugin if nobody removed KDE3 support from LibreOffice?
>> Essentially the following must happen:
>> 1.) Pull the KDE3 picker code (including build script alterations) from
>> the OpenOffice 3.2 / TDE 3.5.12 builds on QuickBuild.
> Why namely from 3.2? It works well in my 3.3.3 as well.

This was a starting point; I know the code in 3.2 works because I patched
and tested it myself on a large deployment of Linux.  Of course if the
newer versions work then that is good.

>> 2.) Ensure that they apply to LibreOffice and produce working binaries
>> on
>> TDE 3.5.13 with Qt3.
>> 3.) Convert to TQt (a simple process that I can do in a day or so AFAIK)
>> and rename all "KDE" strings to "TDE".
>> 4.) Rebuild, test, etc. until everything works properly.
>> 5.) Push the patches into our GIT and notify LibreOffice that we have a
>> new plugin for them!
> Big plans, only why if the current LO builds well with KDE3 support?

And you will guarantee that the upstream LibreOffice project continues to
build an unmaintained plugin just for us?  In my experience unmaintained
code in a project is usually purged after it creates a nontrivial build
failure, if not sooner.  Besides, the main distributions have spoken and
they are NOT building the KDE3 plugin for us, which means that it is in
especially high danger of being purged from the upstream codebase due to
low usage.