From harmony-dev-return-8156-apmail-incubator-harmony-dev-archive=incubator.apache.org@incubator.apache.org Fri Jun 02 09:00:04 2006 Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 34582 invoked from network); 2 Jun 2006 09:00:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Jun 2006 09:00:03 -0000 Received: (qmail 94328 invoked by uid 500); 2 Jun 2006 09:00:01 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 94013 invoked by uid 500); 2 Jun 2006 09:00:00 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 94002 invoked by uid 99); 2 Jun 2006 09:00:00 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jun 2006 02:00:00 -0700 X-ASF-Spam-Status: No, hits=3.2 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_SORBS_WEB,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of oliver.deakin@googlemail.com designates 64.233.182.185 as permitted sender) Received: from [64.233.182.185] (HELO nf-out-0910.google.com) (64.233.182.185) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jun 2006 01:59:59 -0700 Received: by nf-out-0910.google.com with SMTP id p77so995452nfc for ; Fri, 02 Jun 2006 01:59:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=MyOkhPR3pQ4bDeF2Y+T1h0Azm533t6IKXEkFT8ZG8//a9uqSzNJbNJkXeN8PPG1TbIEyM08Cx3sujp4tbDlbbYn66H7oqKQM6G+zQWpZYDvWvNtsD5JYtVcxtzstmotYt9vwGMju5/p2iVPJsjy6fRRZ7pbYxgIZJx4oRqX30Lc= Received: by 10.48.12.19 with SMTP id 19mr1696089nfl; Fri, 02 Jun 2006 01:59:36 -0700 (PDT) Received: from ?9.20.183.162? ( [195.212.29.75]) by mx.gmail.com with ESMTP id o45sm2193636nfa.2006.06.02.01.59.35; Fri, 02 Jun 2006 01:59:36 -0700 (PDT) Message-ID: <447FFDF6.90706@googlemail.com> Date: Fri, 02 Jun 2006 09:59:34 +0100 From: Oliver Deakin User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: harmony-dev@incubator.apache.org Subject: Re: AWT, Java2D and SWING contribution References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Just a note - since the shape of the classlib deploy directory has recently changed, anyone building the swing/awt contribution will find that the built binaries go into deploy/jre/ instead of deploy/jdk/jre/. The fix for this is simple - just add "jdk" into the harmonybin.path property defined in each of the modules//make/build.xml files. i.e. replace with Regards, Oliver Alexey Petrenko wrote: > Dear all, > > I am glad to announce next contribution to Harmony > classlib on behalf of Intel. The archive with the contribution > is uploaded to the following location: > > http://issues.apache.org/jira/browse/HARMONY-528 > > The contribution consists of the following modules: > awt – AWT and Java2D packages > swing – SWING package > misc – utility classes that do not belong to AWT or SWING but > are used by both modules. > > We have tested these modules with ClassEditor, JUnit and > JEdit. Geir has used these modules for demo on JavaOne. > > The Java2D implementation uses GDI+ library on Windows and > Xlib on Linux. For more information on AWT and Java2D > implementation internals, you can read documentation inside > the awt module. > > The building system included with the contribution is > entirely written on ANT. Eclipse 3.1.1 compiler is used for > compile the Java code. The native code can be built with > MSVC or Intel C compiler on Windows and GCC or Intel C > compiler on Linux IA32. The build uses header files and > libraries from current Harmony workspace. All the resulting > jars and dynamic libraries are placed in corresponding > subdirectories of Harmony/deploy directory. You can find > systematic building instructions in the README.txt file in the archive. > > However, there are many things to do in these modules such > as Java 1.5 support, bidirectional text handling, complete implementation > of drag and drop, HTML and RTF formats support, Multi and Synth > look-and-feels and others. The java.awt.PrintJob class and image data > flavors have been removed or commented out because they depend on > the packages javax.print and javax.imageio respectively, which are not > available in Harmony yet. Please refer to the README.txt file for bigger > list of To-Dos and known issues. > > You are welcome to try the contribution and share your opinion! > > SY, Alexey > -- Oliver Deakin IBM United Kingdom Limited --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org For additional commands, e-mail: harmony-dev-help@incubator.apache.org