Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9D5FAD669 for ; Tue, 21 Aug 2012 08:49:04 +0000 (UTC) Received: (qmail 56830 invoked by uid 500); 21 Aug 2012 08:49:04 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 56571 invoked by uid 500); 21 Aug 2012 08:49:02 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 56544 invoked by uid 99); 21 Aug 2012 08:49:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2012 08:49:01 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jogischmidt@gmail.com designates 74.125.83.47 as permitted sender) Received: from [74.125.83.47] (HELO mail-ee0-f47.google.com) (74.125.83.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2012 08:48:52 +0000 Received: by eekb57 with SMTP id b57so1575786eek.6 for ; Tue, 21 Aug 2012 01:48:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=hi89wJTQJt2CxdHMZAubH3zAJNQGX9DMtgQwgXXoiIY=; b=GUX5hELFIhT+4sNDJpil8q6n+PynUONLNZqqoi2850VZoSha9ckkDzNNieuWHN+FKp EIPgkq7tLmuxIV0aubA0sRmPocPKGiBM/gbmBSTWhsIloWBUtKd5s5HSNaz7zXBJIgye NQUVQBh6Y6EMvVM/g/HYkroNpewE9VrnFF/iYM+zLEGDxrSpKwqOD2h7NCBYttRzO4Ut 2bnMNze3kEPFyRKV8ysa3or//XLEQw//dHX9/UpQnp5tb4Lkp0u/XBsMqZFYhA0Ky3rA HRoGxjUd5lvC3Mg1FtaqAohm/SZt94LxRbxogLIPa/3KCfvQZ1VL7lUIWh2ujjxX9xPR 9dHA== Received: by 10.14.220.70 with SMTP id n46mr12522078eep.42.1345538912240; Tue, 21 Aug 2012 01:48:32 -0700 (PDT) Received: from [9.155.131.47] (deibp9eh1--blueice1n2.emea.ibm.com. [195.212.29.164]) by mx.google.com with ESMTPS id h2sm2389935eeo.3.2012.08.21.01.48.31 (version=SSLv3 cipher=OTHER); Tue, 21 Aug 2012 01:48:31 -0700 (PDT) Message-ID: <50334B5E.9010707@gmail.com> Date: Tue, 21 Aug 2012 10:48:30 +0200 From: =?UTF-8?B?SsO8cmdlbiBTY2htaWR0?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: [DISCUSS]: I would like to propose a new conversion mode parameter References: <50324F94.3020201@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 8/21/12 3:46 AM, Rob Weir wrote: > On Mon, Aug 20, 2012 at 10:54 AM, Jürgen Schmidt wrote: >> Hi, >> >> OpenOffice is not only used as desktop application but also as hidden >> part of other software and often as a conversion engine in the backend. >> >> OpenOffice has very good filters for many file formats and the usage as >> a conversion engine is straight forward. And the conversion from one >> format into another can be improved and optimized by some special >> handling of parts of the document. >> >> For example external linked parts can be ignored and don't have to be >> loaded during conversion, embedded images can be simply copied etc. >> >> I would like to improve AOO for this kind of usage by introducing a new >> parameter "-conversionmode". It's not comparable with the command line >> parameter "-headless" or the "hidden" property for loadComponentFromUrl(). >> >> The intention of this new global option is to have it available >> everywhere in the underlying code to optimize the performance of the >> conversion. >> > > It is an interesting idea. Perhaps in the future it could be combined > with a #define and its own makefile so we could compile the project > for this purpose specifically, perhaps having a smaller memory > footprint. Or do you think you can get most of the benefit with > run-time flags alone? probably not and it can be a combination of both. I think mechanisms to exclude specific code at compile time will provide further opportunities. This can evolve over time and we can make use of this on demand. Juergen > > -Rob > >> This should have no influence/impact on the normal workflow but will >> help to make AOO potentially more attractive for backend usage. Means it >> will help to grow the broader eco-system around AOO. >> >> Juergen >> >>