>>>>> "graydon" == graydon hoare <[EMAIL PROTECTED]> writes:
graydon> I wanted to let people know about the status of my native java2d work. graydon> this is visual work and a picture tells at least 1024 words: graydon> http://people.redhat.com/graydon/native-java2d-aug28-2003.png Very cool! graydon> subsequently the structure of the work so far is not as open graydon> to tinkering on the java-side of the JNI as the java2d APIs graydon> might imply. I assume this is a temporary problem, and not a permanent one? graydon> - several of the java2d drawing functions are a bit ambiguous in graydon> specification, so the way they work might not be what you expect. graydon> feel free to correct. For cases like this we usually write a test program to see what Sun does. graydon> in total there's about 140k of code in 9 new files, plus a handful of graydon> little patches around and about. I can post it to the list, or break graydon> it up into lots of separate little patches, or post it to a URL for graydon> reading.. whatever is preferred. comments? Our preferred route is smaller self-contained patches. Sometimes that isn't possible, or desirable -- sometimes it makes more sense to have one big patch. It's your call on that sort of thing; anything defensible is fine :-) Post to java-patches. If there's something likely to be controversial, let's talk about it sans patch on the classpath list. Mostly I'm wondering how this interacts/interferes with other java2d implementations, other platforms, etc. (I'm sure this was already covered and I forgot the answer. Blah.) Tom _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
