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 gcaiod-ooo-dev@m.gmane.org
 designates 80.91.229.12 as permitted sender)
To: ooo-dev@incubator.apache.org
From: Alexander Thurgood <alex.thurgood@gmail.com>
Subject: Re: Report Builder extension (was Re: [proposal] development for
 the first AOO release)
Date: Thu, 10 Nov 2011 17:00:18 +0100
Lines: 51
Message-ID: <j9gsei$hbf$1@dough.gmane.org>
References: <j9gaep$nc8$1@dough.gmane.org>
 <1320938186.32013.YahooMailClassic@web113508.mail.gq1.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
In-Reply-To: <1320938186.32013.YahooMailClassic@web113508.mail.gq1.yahoo.com>

Le 10/11/11 16:16, Pedro Giffuni a �crit :

Hi Pedro, Ariel,

Oh I understand perfectly well why it is being done in this way, I make
my living out of intellectual property so I would be the first one to
say "IP clearance takes precedence" in line with the rules that Apache has.

I also understand that it could still continue to be built separately,
for those who have the time, energy and will to correct the inevitable
bitrot build errors that will creep in over time because code has
changed elsewhere, but no one thought to bother about adapting those
code changes to keep this module buildable. In other words, it will
become harder to build and maintain over time because it has been dropped.

Nonetheless, even if one looks on the optimistic side, there still
remain a few questions :

(1) who in all honesty will do it ?
 - if any of the Linux distribs are interested, they will package it
with their own build of AOOo (assuming that some of them switch from
LibreOffice to AOOo or just continue to provide both)

- what about distrib independent versions - obviously, there will be
none from within AOOo itself, since it can not, so quo vadis ?

- what about Mac ?
- what about Windows ?

I think that realistically, resources are spread too thinly on the
ground for this to happen at present.


(2) what kind of message does this convey to Joe Public ?
- AOOo (aka OOo) is destined only for those who know how to build and code ?

Somehow, I don't think that you'll hit your target audience with such an
approach - a binary version that misses bits of what has become
essential functionality for many will not sway people to switch from OOo
to AOOo - in fact, it might well even make them switch to competing
products.


Perhaps someone will find a way of furthering the development of the
original report designer instead, because that at least does form part
of the SGA (it was already in the initial release of the OOo code all
those years ago). I hope so, I really do.


Alex