Wonka Classpath
Mark, etc., sorry you haven't heard from me for a few days - other things have been claiming my attention. Yes, I agree that the the revised Classpath exception to the GPL removes one of the main barriers to the use of GPL'd software in embedded systems, namely that pretty well everything in such a system is linked with everything else, and therefore if one component falls under the GPL then the whole system must be distributed on GPL terms. However it still seems to me that GPL+exception excludes the possibility of binary-only distributions, something which we do not wish to exclude. Admittedly there seems to be little reason why a systems integrator would need to make proprietary modifications to a core package such as java.awt (as opposed to wonka.rudolph.peers), but still I can imagine cases where the GPL would impose on the system integrator the obligation to provide source code to anyone who asked. Perhaps Andy of Aicas can explain why this is not a problem for them? In the meantime it remains my feeling that a project should ideally have one owner and one licence, and in the case of Wonka the owner is Acunia and the licence is (revised) BSD. I can consider making the whole available under a second licence as an alternative, but having parts with one owner and licence (Acunia, BSD) and parts with another owner and licence (FSF, GPL+exc.) doesn't make sense to me. However, I still see a lot to be gained by agreeing on a common interface between the java.awt classes and their peers: there is almost no documentation available from the shining light at the centre of our universe, so currently we are just improvising. If Classpath were to propose an interface then we would certainly be willing to review and eventually adopt it; in fact we could probably help with the preparation of the proposal. Then our framebuffer peers (and any other peers developed for Wonka) would be available for use in Classpath-based projects and vice versa. (Note that currently we are also using a Wonka-specific interface for communication between the native and java parts of our peers. Replacing this with JNI has been on our to-do list for a long time, and it just got a goodly priority boost). Best wishes Chris Gray ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: Wonka Classpath
Chris Gray wrote: However it still seems to me that GPL+exception excludes the possibility of binary-only distributions, something which we do not wish to exclude. My reading is that it excludes binary-only distribution of modified libraries, which we *do* want to exclude. Admittedly there seems to be little reason why a systems integrator would need to make proprietary modifications to a core package such as java.awt (as opposed to wonka.rudolph.peers), but still I can imagine cases where the GPL would impose on the system integrator the obligation to provide source code to anyone who asked. I think that is a feature, not a bug in the license. We want to encourage people to submit improvements. -- --Per Bothner [EMAIL PROTECTED] http://www.bothner.com/per/ ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
mauve results posted nightly
So barring accidents of nature or human error I'll hopefully be able to post nightly Mauve results for Kissme/Classpath starting today. The Classpath homepage, http://www.classpath.org/, has been updated with links. I have added japicompat results against 1.1 and updated to japitools-0.9. Please let me know if posting this information in this way is useful. Perhaps other JVMs could be added. Does Gcj do this? Thanks, Brian -- Brian Jones [EMAIL PROTECTED] ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
Re: mauve results posted nightly
Brian == Brian Jones [EMAIL PROTECTED] writes: Brian Please let me know if posting this information in this way is useful. Brian Perhaps other JVMs could be added. Does Gcj do this? Mark Wielaard posts nightly test results to the gcc test mailing list. As I recall he does this for a couple platforms. I usually just glance over these; a mailing list isn't that great of a format for detecting regressions. Ben Elliston is working on a Tinderbox-like system. It will include gcj test results. Ideally it will also send out email when someone introduces a regression (like Geoff's old tester, but it will include libgcj). Tom ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
AWT status
This weekend I did some AWT hacking. Now a lot of TestAWT works for me (using the Gtk+ JNI peers and gcj). In particular all the windows pop up and the layout bugs all seem to be gone. Some bugs remain: * The Cursors window displays things oddly (the button appears twice, though it can be hard to find the second one since it is obscured; you have to resize the window a lot to see it) * Dialog buttons don't work * Ditto File * The Radio Button window works but the second time you pop it up you get Gtk errors. This is due to a problem I introduced in the peers; I didn't realize that the native state support required a special field in the object. This needs some rethinking, since adding a field to CheckboxGroup is probably not what we want to do. * Font peers haven't been implemented yet. * Radio button peers need some special code to let them switch modes at runtime (you can't see this problem with TestAWT) I think there are more tree lock bugs to fix, but I haven't gone looking for them yet. Basically I didn't look for any of them -- I just audited a few classes, adding the synchronization where required. This same procedure should be copied for other classes. Tom ___ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
