Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of gstein@gmail.com designates
 209.85.212.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=XOMDzPjX/Up7uuEfvvFXF3vrEvE0rvsouda0fOUaw59gdmHJ29QdDx24Y4sVsU6Vvy
         0X+FyeFBHmBCNKQtLQKfcDeEJTVKI9R7iiDQNflWm6upgh8y+0saaNVSxi9tIyWtNkmw
         8Uv7ObtY0JFr4kUxKp5h5+Ee1XfhYMEXJzj54=
MIME-Version: 1.0
In-Reply-To: <4DF7D090.5090000@lippka.com>
References: <4DF7D090.5090000@lippka.com>
Date: Tue, 14 Jun 2011 18:29:38 -0400
Message-ID: <BANLkTim-WTEhoY42hJ8-L6u+ChSawbsh4Q@mail.gmail.com>
Subject: Re: [discuss] remove of binfilter module
From: Greg Stein <gstein@gmail.com>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 14, 2011 at 17:20, Christian Lippka <cl@lippka.com> wrote:
>...
> Proposal
>
> I suggest to remove the binfilter module after the code has been provided
> under the AL.
> Therefore we have it inside the SVN and could re activate it later.
> Preferable as a separate
> extension.

I'm unfamiliar with OOo's extension system. How hard would it be to
add "import OLD format $FOO"(*) as an extension?

If it can be implemented "soon" or "later" as an extension, then it
seems moving this in that direction makes sense *regardless* of the
binfilter problems (ie. as a way to modularize). And that you could
start out by tossing everything on Day Two, then letting the
"interested devs" bring the feature back as a set of one or more
extensions.

Cheers,
-g

(*) assuming my understanding is that binfilter is *only* about
importing archaic formats