[Foa-devel] RE: JDK 1.1.8

[<bf...@ew...>]

>From: "Giannetti, Fabio" <Fab...@hp...>
>To: foa...@li...
>Date: Thu, 12 Sep 2002 09:37:53 +0100
>Subject: [Foa-devel] RE: JDK 1.1.8
>
>Ben,
>	this is very good !
>Can you create some instruction, or an how-to, to be added to the
>distribution especially for mac users ?
>I will put these instructions into the web site.
>Thanks,
>Fabio
>
>> -----Original Message-----
>> From: bf...@ew... [mailto:bf...@ew...]
>> Sent: Wednesday, September 11, 2002 1:01 PM
>> To: Giannetti, Fabio; foa...@li...
>> Subject: JDK 1.1.8
>>
>>
>> I have been able to get Foa to compile on Mac OS 9 with Metrowerks
>> 6. This version loads and runs - I have a screen shot (60 kByte)
>> to prove it, which I could forward to anyone interested.
> >
> > I am still looking for build instructions using, say, make or
> > ant for use on linux.

Unfortunately, the instructions would involve the sacrifice of a goat
and several chickens: in other words it is not on (at the time of
writing) for people who need a 'how-to'.

I could add, that under JDK 1.1.8/Mac OS 9, the dialogue boxes
come up on top of their parents, which they don't on mac OS X, and
the Tree display of attribute sets in the Attribute Set manager
works (which I don't think that it does on Mac OS X).

(I have screenshots which demonstrate these features).

The point of my post was to state that it was possible.

We now need to discuss whether it is desirable and/or whether any
compromises required are sustainable.

(I think 'yes' partly because the Mac is my favoured system,
and partly because of the extra power of debugging one gets
by adding another system).

The final hurdle is that the rendering part of Foa calls certain
Java 2 features of Swing, starting with BufferedImage in PreviewRenderer
and PreviewPanel. I would like to deal with this by dividing Foa
into a standalone core (Foa1) which compiles and runs on Java 1,
and several extensions, appendages or developments which may
require later versions of Java (Foa2). Clearly the solution to
my BufferedImage problem is to exclude those files and that functionality
from the Basic or central Foa and place them in the Advanced or
greater Foa.

Another possibility would be obtain Java 1 implementations of the
required classes, though this would require analysis of the licencing
issues involved.

The main modifications to the core of Foa are:

1. Restrict the Dimension class to the Java 1 features.
2. Only use the Java 1 constructors for the various GUI widgets,
	notably JButton.
3. Provide an implementation or workaround for the DeleteCharAt( )
	method of StringBuffer.

My first question is whether the Foa team would allow this Java 1
pollution of what might otherwise be clean Java 2 code.

I expect that I am the only person who is that interested, and
maybe this needs to be put on hold.

Another way forward would be to develop an 'ant' target that
delivered Java 1 code. This was used successfully by the Fop
team until they 'let go' the Java 1 edition of Fop (I am still
using Fop 0.14, which runs on Mac OS 9).

This is one reaon why I am interested to know the best way
of building Fop on linux, as I feel that using ant might prove
to be an advantage.

Grateful for any comments.

Ben.
-- 
Privileged/Confidential Information may be contained in this message.
If you are not the addressee indicated in this message (or responsible 
for delivery of the message to such person), you may not copy or deliver 
this message to anyone. In such case, you should destroy this message 
and kindly notify the sender by reply email.  Please advise immediately 
if you or your employer do not consent to Internet email messages of this
kind.  Opinions, conclusions and other information in this message that 
do not relate to the official business of ewitness Limited shall be 
understood as neither given nor endorsed by it.

eWitness Limited, Alpha House, Redvers Close, Lawnswood Business Park, Leeds, LS16 6QY
Telephone:  0113 2951112  Fax: 0113 2951114