Re: Go-oo and Java

On Fri, 2010-04-09 at 01:48 +0200, Michael Hansen wrote:

> Because of the fact that the Go-oo project is a Fork (or kind of),

No, it's *not* a fact that Go-OO is a fork.  Some may say "it's
debatable whether Go-OO is a fork or not" (even Wikipedia says that),
but it's not.  It's a downstream version.  A "fork" is something that's
*totally* been branched off of the original (or upstream) version,
without tracking the development of the original (or upstream) version
anymore.  Go-OO tracks the upstream version, with the goal of eventually
merging its changes upstream.  That makes Go-OO a non-fork.

That upstreaming process has not always been easy, but that's another
topic.

>  I am asking me, whether there are any intensions to make Go-oo work
> completely independent from a JRE and get rid of any dependencies.

No, I don't think we intend to remove all of JRE dependencies.  But
let's indulge for a moment and say that we want to remove all our JRE
dependencies.  What do we need to do?  First, we will lose some fringe
functionalities that depend on JRE, such as various wizards.  Also, some
extensions we bundle with depend on Java.  If we were to remove JRE
dependency we would somehow need to re-write those in C++.

But the biggest issue would be Base's JRE dependency with hsqldb.
Without JRE, you won't be able to store database with the Base document.

So, there would be some hurdles to overcome in order to remove JRE
dependencies altogether without losing functionality.  Whether it's
doable or not within reasonable effort, or if the loss of these
functionalities is warranted in the name of removing JRE dependency, is
beyond my knowledge and judgment capability.

Kohei

-- 
Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc.
<[email protected]>