Most of the conversation on this list seems to be about jdk1.2, which is
fair enough given the climate at the moment, but I've a problem with 1.1
(and not only on Linux, I have to say). I would like to run my
"solution" past the list, and see what people have to say about it: "go
for it", "you should be locked up", etc.
We are involved in writing a major music editor, analysis and archive
package. This will be open-ish source and freely redistributable. I had
to work hard to get java as the language, but I wanted to use it, not
just for portablility reasons, but because I like the design,
documentation capacity etc etc, and it's enough like c++ that the
community could offer bug fixes in the open-software spirit.
We are having trouble with our "fonts". They are not real fonts: they
are images created by a memory image source which was created by reading
a TeX pk file. The fonts are read from the pk file to generate a pixel
map with one-bit-per-pixel. We want to write these images on the screen
using a colour model with 1 bit per pixel, i.e. fg (usually black) and
transparent. The "character" will be written on top of the musical
staff, so we need transparency, whether by real transparency or by
setting some writing mode to OR...
Anyway, it appears that the 2bpp modes are broken (this is a documented
problem). We are using 1.1 (actually 1.1.6) with swing, but I
understand thay 2bpp is /still/ broken in 1.2. I am suggesting that it
might be possible to go with a different AWT, e.g. kaffe, but I don't
know what I'll be giving up. So here are my questions: some are
kaffe-specific, but all are to do with Linux (my development platform).
I'd like to invite comments to the following forthright statements (some
of which might just be plain wrong 8-)
?1. Kaffe is open, so it is inherently the better route, even if it is
behind on the 1.2 compatibility
?2. Sound and MIDI isn't there yet, even in so far as it's in the 1.2
spec. We might as well code with JNI and go native.
?3. Java2d on 1.1 isn't any different from Java2d on 1.2
?4. The Kaffe AWT had more bugs that the Sun one, and should be
avoided.
?5. Use <insert favourite class library set>: it's better than <insert
most hated class library set>
?6. Sun is the authoratitive reference, so if there are bugs in it, you
better code around them rather than expect anybody else to use your
minority stuff.
?7. Stop whinging and fix the sun bugs!
I personally don't want to do 7: I'd rather be contributing to something
completely open, and I don't know if it is even possible.
I'd really welcome input from people who have used this stuff in the
large. I've got a nasty feeling this is a mission-critical decision,
and I don't know what I'm talking about (perhaps it's time to apply for
a job in senior management 8-)
Nick/
--
Dr. N.J.Bailey-----------------------------------------------
Lecturer in Electronic and Electrical Engineering
University of Leeds, Woodhouse Lane, Leeds,
LS2 9JT. UK.-------------------------------------------------
http://www.ee.leeds.ac.uk/homes/NJB/
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
