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


I'm working up an independent c++ app (win32 console application) that talks
to Libreoffice, "preferably via pipes"... and will open, close and manage a
Calc spreadsheet. This is a proof of concept..to see if LibreOffice can add
value.  Can anyone send me a sample.  sample can be for a linux or windows
platform.

An independent C++ application (console application) can talk to libreoffice
via tcp.ip, pipes or ole. ( could be others?)  The problem is that
LibreOffice samples that work with a  calc doc, that I have found googling,
cover two different LibreOffice architectures.   

Todate, I have only found one c++ sample that works with a calc doc, that
uses Windows DCOM, that built and worked without any error codes.

All samples that I have found, googling, use a deprecated libreoffice
architecture. ( except for one ole dcom sample)
Deprecated architecture: Samples work with LibreOffices by using file
<comphelper/processfactory.hxx>,  Last seen in version 4.0.0.3 ( about)

Plus there are architecture differences in working with rdb files, etc...

And then functions,in a current version of LibreOffice, that are deprecated
due to architecture changes,  return abort().  This increases difficulty in
debugging.  Because this allows a build, but then if that function is
called, it makes an app crash.  It's hard to fanthom why this approach was
used.

A good example 

cppuhelper/source/compat.hxx

line 56.  Reference<XSimpleRegistry>createSimpleRegistry(OUString const&)
returns std::abort. 
There is a comment "//avoid "must return a value warning"











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.