Thorsten Behrens wrote:
Caolan McNamara <[EMAIL PROTECTED]> writes:
On Fri, 2007-02-02 at 14:18 +0100, Pavel Janík wrote:
What about making binfilter SO only module? ;-)
-1
Unfortunately .sdw etc documents exist and are a fact of life, we do
still need to import them. e.g. my performance review still comes
in .sdw format, we wouldn't want to drop importing that :-)
Hm - hard to estimate how many of those binary documents are still in
active use. And it would be interesting if they are kept just because
of laziness, or for good reasons (I clearly suspect the former).
Laziness is a good reason. No one is going over back up tapes just for
converting old documents ... as long as it is reasonably safe to assume
it's still safe to open the old documents. "Active use" is a misleading
term here. I still want to be able to look into - let's say - old
exchanges with the tax authorities but I wouldn't ever want to change
these documents. Be able to do that without fiddling around with an old
version of OpenOffice.org is a major convenience.
At any rate, binfilter is a huge, tangled mess (yes, more so than the
average OOo module), and maintaining/building/shipping it benefits
only those tiny fraction of users with sd?-documents.
*If* we want to start reducing build time/reduce developer load/free
resources for other tasks, then reducing code size is clearly top on
the list - and binfilter would be a huge blob we could drop in one
go.
There are at least three possible ways to do this gracefully:
a) drop binfilter for the next major release, telling users to convert
their documents using OOo2.x. Can even implement a tiny filter
replacement, that says so in a message box.
Before we drop our own legacy filters (which would be a major
inconvenience for "lazy" long time office users) we should think hard
about obsolete 3rd party filters which could be removed without
alienating our own user base.
b) move _all_ modules below binfilter into that module, possibly after
stripping them to the necessary minimum. Build it once, and tuck it
into a safe place (comes close to a, but is smaller & integrates
with OOo3).
Unrealistic, because rebuilding the binfilters might be necessary for
all kind of reasons: compiler changes, base line changes, bug fixes, new
platforms etc. Over long it would be part of the regular build again,
now only bigger than ever before.
c) have a webservice at services.openoffice.org, that runs OOo2.x,
and gets accessed from the sd?-filter of OOo3
A webservice for confidential documents? Not a good idea ...
Heiner
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
