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

Hi Ben,

Am 28.01.2011 15:55, schrieb BRM:


Why go through the effort of (i) scripting LO and (ii) enabling your application 
to do that, when you could simply
just make a UI to (a) show the existing document to the user in a view mode 
(read-only), (b) get the specific data you need in your application,
presenting controlled interfaces to do so, and (c) write the ODF document 
yourself?

While it may seem easier to incorporate an existing product like LO to do the 
document editing for you; it is likely far
easier to just do it yourself and use a tool like ODF Tool Kit to write the 
output document and load it for display - at the very least,
showing the user the output document with any kind of program (LO, OOo, 
Symphony, Calligra, etc.) would be very easy to do without having to enhance any 
of them for scripting.

$0.02

Ben

thanks for you thoughts. I want to be as close as possible to the office
application. For example the user could create document templates with
defined field names which are populated with external data. Sure there
are solutions for every scenario to avoid using and scripting LO but I
see value in providing this kind of functionality in an office context.

Regards
Thorsten Guenther

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.