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


Hi Clemens,

On Tue, 2011-11-08 at 15:55 +0100, webmaster@csz-online.de wrote:
I'm currently working on some data format exportation tests with the  
LibreOffice SDK and Java. I want to develop an addon, which can export  
the current opened file in another dataformat.

        Sounds fun :-) if it is a generally useful one, I'd strongly recommend
doing it as native C++ in the core - it'll be very substantially faster,
and of course we can then ship it with the core product.

 I already have some converter-methods, which can be used. The only
thing I need is to get access to the opened document in some Java
object(s).

        The normal way to do this would be with some ODF <-> [other]
transformation in a filter. An example of an import filter that does
validation, in java is here:

http://cgit.freedesktop.org/libreoffice/core/tree/filter/source/xsltvalidate/XSLTValidate.java

I already tried to search in the development manuals of LibreOffice  
and OpenOffice but there was no result. Perhaps anyone of you guys  
could help?

        Cf. above, if you can help write up a nice nice page in the LibreOffice
wiki, with some sample / template / "Hello World" / skeleton code making
this easy as you unwind it, that'd be much appreciated.

        All the best,

                Michael.

-- 
michael.meeks@suse.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.