Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index



On Mon, 2011-04-04 at 16:23 +0100, Caolán McNamara wrote:
On Sun, 2011-04-03 at 17:00 +0200, archlid wrote:
Is pyAltFCFGMerge supposed to replace the Java merging program? 
I read that the Java dependencies will be reduced in LibreOffice.

        Oooh - I missed that :-)

I wrote it a long time ago as basically a direct copy and paste and
re-word version of the java one when I was trying to port to something
that didn't have any working java IIRC. It gets used alright with
--disable-java, I'm not 100% sure that it still works perfectly, but it
munges together the config "fragments" in
filter/source/config/fragments/ to make the list of filters that
LibreOffice shows in file->open, save as, etc. 

        It looks like it does an identical job - at least my diff -u before and
after having SOLAR_JAVA enabled shows exactly no difference in the
output :-)

        Andreas - it would be great to get a patch to kill the java config
fragment merging tool, and use this python one un-conditionally instead.

        Should be just a matter of hacking:

        filter/source/config/fragments/makefile.mk

        And binning the FCFGMerge.jar compilation / source code etc.

        Any chance you could look at that as an easy-hack-alike ? :-)

        Thanks,

                Michael.

-- 
 michael.meeks@novell.com  <><, Pseudo Engineer, itinerant idiot


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.