Hi Johan,
Johan Vromans wrote:
What feature are you thinking of in particular?There has been a list of features requiring Java on one of the lists
some time ago. Features included were (a.o.) writer wizards.
IIRc some of the 1.1.x wizards were written in Java as well. So I don't see a qualitative change there.
We want to give this choice to users.
That's good. So there will be two flavours of OOo 2 to be downloaded: one that requires Java (leaving it up to me to install this if it is not on my platform already) and one that works with gcj (leaving it up to me to install this if it is not on my platform already).
I don't know any details about gcj, but I would assume that it is intended to be a drop-in replacement for Java. That would mean that it offers library interfaces and a VM that are binary compatible to Java's JNI and JVM. If this is true, then there would be no need to have different versions; a single version could work with a JRE (if present) or gcj (if present) or without either (without the Java features).
The one point where OOo might have to be adapted to gcj is the framework that discovers installed Java runtimes and configures the OOo application to work with the libraries and VM from a particular one. This framework (in OOo 2.0) is designed to support JRE's from multiple vendors through a plugin architecture. I don't know whether gcj needs anything special here or whether the people working on gcj support will contribute any necessary pieces by the release of OOo 2.0.
If gcj turned out to not be ABI-compatible to Java, a different solution would be needed.
Ciao, J�rg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
