From neugens.limasoftware at gmail.com Tue Jan 3 01:53:24 2012 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Tue, 3 Jan 2012 10:53:24 +0100 Subject: Merge CacioWeb Message-ID: <45BEDE89-B92A-4A00-98FC-F551997A4E56@gmail.com> Hello all, I would like to ask a question about the future directions for Caciocavallo, and CacioWeb. As you may already know, Cacio is a project we started for the OpenJDK Innovators Challenge and was aimed at refactoring the graphics code in OpenJDK to allow custom peers (and hence easy the portability of the platform to new systems). It evolved from the set of patches necessary to allow plugging of a custom backend, to a full abstract implementation of the AWT peer code and has been quite successfully used in commercial environments for quite a lot of time, and it is now in maintenance mode since at least a couple of years, apart from some small patches and fixes that land from time to time. I think that the level of activity justifies to start thinking about the future and the final merge of the project on the JDK repositories (I think JDK8/JDK9 timeframe would be the goal). As I introduced, Cacio started as a series of JDK6 patches to enable custom graphics backends (and required a custom build of the JDK at the time), but those patches were all formally included in the JDK7, so today is already possible to use a Cacio based peer on JDK7 onward by just adding the shared Caciocavallo and peer code jar file without any extra patch or custom build. This makes a lot of sense, since Cacio is formally separated by the JDK, but at the same time puts some efforts on our side, since we need to maintain different versions of the project for each JDK release (major release). We decided to address this issue by only following the latest development version, while we tag a release where backward compatibility is known to break, and this approach seems to work quite well. On the other end, it could make more sense to include Cacio in the build process of the main JDK, especially since the only usable peer (and the only being actively developed) is currently the HTML5 one, and by integrating this in the JDK forest as well, my hope is to enable builds to pass (or be tested against) the TCK. I also hope that by having the code directly integrated in the JDK we will be able to reach more testers and fix more issues, since now Cacio is used in very specific environments only. In addition to that, in order to support the web peer, we are implementing a number of features that will surely be beneficial for the Java ecosystem, like client filesystem support over the HTML5. I believe that those additions could be very useful, and we call this project internally as WebJDK (spoiler: we will unveil something at FOSDEM if you would like to attend and are interested). I know that based on the new rules I will have to formally propose a project, but before doing this I want to see if a formal WebJDK would be something interesting for the community and not only for us, and if Cacio would be likely to be integrated in the JDK, or if you prefer the current situation where it's a separate library. If accepted, the WebJDK will include a custom JDK8 forest (or perhaps just the patches since are easier to manage) with all the code needed to enable web support (filesystem, deployment code, etc...), plus Cacio and the HTML5 peer code. We will develop this in the JDK8 timeframe and hopefully merge everything that makes sense in the "real" JDK9 forest. Any ideas, suggestions, criticism? Thanks, Mario --- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF http://www.ladybug-studio.com IcedRobot: www.icedrobot.org Proud GNU Classpath developer: http://www.classpath.org/ Read About us at: http://planet.classpath.org OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/ From kadir at bayner.com Tue Jan 3 03:37:50 2012 From: kadir at bayner.com (Kadir BASOL) Date: Tue, 03 Jan 2012 13:37:50 +0200 Subject: Merge CacioWeb In-Reply-To: <45BEDE89-B92A-4A00-98FC-F551997A4E56@gmail.com> References: <45BEDE89-B92A-4A00-98FC-F551997A4E56@gmail.com> Message-ID: <4F02E88E.7090600@bayner.com> Hello , the most lack of future on java is , java on embedded systems. Its consuming much memory and still swing like gui futures requires X Window system. I think best thing is implementing java swing run on linux framebuffer on Linux with OpenGL ES Future and another important is , It must be flexible like we can inject C++ JNI codes on some canvases inside , so if some critical function required , we use C++ on GUI. If we do it , Java can be best on embedded systems... All accept ? On 03/01/2012 11:53, Mario Torre wrote: > Hello all, > > I would like to ask a question about the future directions for Caciocavallo, and CacioWeb. > > As you may already know, Cacio is a project we started for the OpenJDK Innovators Challenge and was aimed at refactoring the graphics code in OpenJDK to allow custom peers (and hence easy the portability of the platform to new systems). > > It evolved from the set of patches necessary to allow plugging of a custom backend, to a full abstract implementation of the AWT peer code and has been quite successfully used in commercial environments for quite a lot of time, and it is now in maintenance mode since at least a couple of years, apart from some small patches and fixes that land from time to time. > > I think that the level of activity justifies to start thinking about the future and the final merge of the project on the JDK repositories (I think JDK8/JDK9 timeframe would be the goal). > > As I introduced, Cacio started as a series of JDK6 patches to enable custom graphics backends (and required a custom build of the JDK at the time), but those patches were all formally included in the JDK7, so today is already possible to use a Cacio based peer on JDK7 onward by just adding the shared Caciocavallo and peer code jar file without any extra patch or custom build. This makes a lot of sense, since Cacio is formally separated by the JDK, but at the same time puts some efforts on our side, since we need to maintain different versions of the project for each JDK release (major release). We decided to address this issue by only following the latest development version, while we tag a release where backward compatibility is known to break, and this approach seems to work quite well. > > On the other end, it could make more sense to include Cacio in the build process of the main JDK, especially since the only usable peer (and the only being actively developed) is currently the HTML5 one, and by integrating this in the JDK forest as well, my hope is to enable builds to pass (or be tested against) the TCK. > > I also hope that by having the code directly integrated in the JDK we will be able to reach more testers and fix more issues, since now Cacio is used in very specific environments only. > > In addition to that, in order to support the web peer, we are implementing a number of features that will surely be beneficial for the Java ecosystem, like client filesystem support over the HTML5. > > I believe that those additions could be very useful, and we call this project internally as WebJDK (spoiler: we will unveil something at FOSDEM if you would like to attend and are interested). > > I know that based on the new rules I will have to formally propose a project, but before doing this I want to see if a formal WebJDK would be something interesting for the community and not only for us, and if Cacio would be likely to be integrated in the JDK, or if you prefer the current situation where it's a separate library. > > If accepted, the WebJDK will include a custom JDK8 forest (or perhaps just the patches since are easier to manage) with all the code needed to enable web support (filesystem, deployment code, etc...), plus Cacio and the HTML5 peer code. > > We will develop this in the JDK8 timeframe and hopefully merge everything that makes sense in the "real" JDK9 forest. > > Any ideas, suggestions, criticism? > > Thanks, > Mario > --- > pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF > Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF > > http://www.ladybug-studio.com > > IcedRobot: www.icedrobot.org > Proud GNU Classpath developer: http://www.classpath.org/ > Read About us at: http://planet.classpath.org > OpenJDK: http://openjdk.java.net/projects/caciocavallo/ > > Please, support open standards: > http://endsoftpatents.org/ > > > From kadir at bayner.com Tue Jan 3 03:47:23 2012 From: kadir at bayner.com (Kadir BASOL) Date: Tue, 03 Jan 2012 13:47:23 +0200 Subject: we can help you Message-ID: <4F02EACB.80404@bayner.com> we can help you on this project. But we dont know what to do for OpenGL ES side. You can give us responsibility for this side. From xerxes at zafena.se Tue Jan 3 04:45:51 2012 From: xerxes at zafena.se (=?ISO-8859-1?Q?Xerxes_R=E5nby?=) Date: Tue, 03 Jan 2012 13:45:51 +0100 Subject: we can help you - caciocavallo OpenGL ES backend and possibly OpenVG backend. In-Reply-To: <4F02EACB.80404@bayner.com> References: <4F02EACB.80404@bayner.com> Message-ID: <4F02F87F.1010603@zafena.se> 2012-01-03 12:47, Kadir BASOL skrev: > we can help you on this project. But we dont know what to do for OpenGL ES side. You can give us responsibility for this side. > Hi today there exist two good Java binding/frameworks LWJGL and JOGL that you can use in combination with OpenJDK to get access to the OpenGL-ES 2.0 drivers. These bindings provide a JSR 239: JavaTM Binding for the OpenGL ES API, that are similar to the Java OpenGL-ES bindings found inside the Android API stack. I have put some notes on the TrimSlice forum: http://www.trimslice.com/forum/viewtopic.php?f=48&t=402 - OpenGL-ES acceleration using JogAmp JOGL + OpenJDK http://www.trimslice.com/forum/viewtopic.php?f=48&t=393 - OpenGL-ES acceleration using LWJGL + OpenJDK These notes explain how to test and build these two frameworks on embedded systems to render hardware accelerated and shaded primitives using the OpenGL-ES 2.0 pipeline. It basically work like this: First you need the OpenJDK classes and a suitable JVM. JVMs that are known to work on embedded systems and can be built from free software are JamVM, CACAO, Zero and Shark. JOGL 2.0 and/or LWJGL can then be used as a clean interface to the GPU manufacturers libGLES_v2.so and libEGL.so libraries. Try write a caciocavallo back-end based on the JOGL 2.0 or LWJGL example code! OpenGL-ES itself are fast to render 3D polygons but you will need to write a clever rasterizer in order to make OpenGL-ES render all the frequently found curves and shapes that are commonly found in Java 2d GUI applications. Switching topic OpenVG (Open Vector Graphics): One of the best ways get accelerated java 2d and 2.5d (think overlapped windows) gui's on embedded hardware are to first create a open source binding for OpenVG. OpenVG exist in silicon on most embedded system on a soc chips with integrated GPU core. I know that Nokia and RIM are providing a OpenVG implementations based on JSR 287: Scalable 2D Vector Graphics API 2.0 for Java ME. Unfortunately currently no free or open-source implementation exist for OpenVG that I am aware of. There do exist some projects that emulates the OpenVG layer by rasterizing OpenVG primitives into OpenGL-ES calls like the jni intense androidvg project. The JogAmp community have started on implementing a "JOVG" sister project to JOGL that would allow JOGL to make use of OpenVG hardware acceleration in combination with the OpenJDk classes. https://github.com/syntelos/jovg Cheers Xerxes From ralf.heini at aicas.de Wed Jan 4 07:17:33 2012 From: ralf.heini at aicas.de (Ralf Heini) Date: Wed, 04 Jan 2012 16:17:33 +0100 Subject: Merge CacioWeb In-Reply-To: <45BEDE89-B92A-4A00-98FC-F551997A4E56@gmail.com> References: <45BEDE89-B92A-4A00-98FC-F551997A4E56@gmail.com> Message-ID: <4F046D8D.2080102@aicas.de> Hi Mario, It's nice to hear that Cacio evolves. :-) We'd be happy if Cacio and CacioWeb will make it into the official OpenJDK. As we have several graphical implementations here using Cacio (Win32, QNX Photon, MAUI, WindML and even more experimental ones), we found out that lots of code is duplicated in each target, like the generation of mouse "clicked" events. It would be nice if those things were part of the abstract implementation. We'd like to pass our changes like bug fixes, clean-up, documentation and maybe even refactoring to the Cacio project. We still use OpenJDK6 here and probably will continue our development there for some time so we need to work around JDK7 stuff. I hope this will be possible for quite a while. This CacioWeb thing is pretty cool and might become very interesting for us, though we haven't used it yet. Regards, Ralf Mario Torre wrote: > Hello all, > > I would like to ask a question about the future directions for Caciocavallo, and CacioWeb. > > As you may already know, Cacio is a project we started for the OpenJDK Innovators Challenge and was aimed at refactoring the graphics code in OpenJDK to allow custom peers (and hence easy the portability of the platform to new systems). > > It evolved from the set of patches necessary to allow plugging of a custom backend, to a full abstract implementation of the AWT peer code and has been quite successfully used in commercial environments for quite a lot of time, and it is now in maintenance mode since at least a couple of years, apart from some small patches and fixes that land from time to time. > > I think that the level of activity justifies to start thinking about the future and the final merge of the project on the JDK repositories (I think JDK8/JDK9 timeframe would be the goal). > > As I introduced, Cacio started as a series of JDK6 patches to enable custom graphics backends (and required a custom build of the JDK at the time), but those patches were all formally included in the JDK7, so today is already possible to use a Cacio based peer on JDK7 onward by just adding the shared Caciocavallo and peer code jar file without any extra patch or custom build. This makes a lot of sense, since Cacio is formally separated by the JDK, but at the same time puts some efforts on our side, since we need to maintain different versions of the project for each JDK release (major release). We decided to address this issue by only following the latest development version, while we tag a release where backward compatibility is known to break, and this approach seems to work quite well. > > On the other end, it could make more sense to include Cacio in the build process of the main JDK, especially since the only usable peer (and the only being actively developed) is currently the HTML5 one, and by integrating this in the JDK forest as well, my hope is to enable builds to pass (or be tested against) the TCK. > > I also hope that by having the code directly integrated in the JDK we will be able to reach more testers and fix more issues, since now Cacio is used in very specific environments only. > > In addition to that, in order to support the web peer, we are implementing a number of features that will surely be beneficial for the Java ecosystem, like client filesystem support over the HTML5. > > I believe that those additions could be very useful, and we call this project internally as WebJDK (spoiler: we will unveil something at FOSDEM if you would like to attend and are interested). > > I know that based on the new rules I will have to formally propose a project, but before doing this I want to see if a formal WebJDK would be something interesting for the community and not only for us, and if Cacio would be likely to be integrated in the JDK, or if you prefer the current situation where it's a separate library. > > If accepted, the WebJDK will include a custom JDK8 forest (or perhaps just the patches since are easier to manage) with all the code needed to enable web support (filesystem, deployment code, etc...), plus Cacio and the HTML5 peer code. > > We will develop this in the JDK8 timeframe and hopefully merge everything that makes sense in the "real" JDK9 forest. > > Any ideas, suggestions, criticism? > > Thanks, > Mario > --- > pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF > Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF > > http://www.ladybug-studio.com > > IcedRobot: www.icedrobot.org > Proud GNU Classpath developer: http://www.classpath.org/ > Read About us at: http://planet.classpath.org > OpenJDK: http://openjdk.java.net/projects/caciocavallo/ > > Please, support open standards: > http://endsoftpatents.org/ > > > -- Dipl.-Inform. Ralf Heini * Development and Support * Tel: +49-721-663 968-51 aicas GmbH Haid-und-Neu-Stra?e 18 * D-76131 Karlsruhe * Germany http://www.aicas.com * Tel: +49-721-663 968-0 USt-Id: DE216375633, Handelsregister HRB 109481, AG Mannheim Gesch?ftsf?hrer: Dr. James J. Hunt From ralf.heini at aicas.de Wed Jan 4 07:40:36 2012 From: ralf.heini at aicas.de (Ralf Heini) Date: Wed, 04 Jan 2012 16:40:36 +0100 Subject: Patch: Fix initial visibility of managed windows Message-ID: <4F0472F4.5040001@aicas.de> As a ManagedWindow can be used for top level and other windows, the initial visibility depends on the AWTComponent. This fixes the problem that mouse events do not arrive at a Component that was added to a Container after that has been set to visible. -- Dipl.-Inform. Ralf Heini * Development and Support * Tel: +49-721-663 968-51 aicas GmbH Haid-und-Neu-Stra?e 18 * D-76131 Karlsruhe * Germany http://www.aicas.com * Tel: +49-721-663 968-0 USt-Id: DE216375633, Handelsregister HRB 109481, AG Mannheim Gesch?ftsf?hrer: Dr. James J. Hunt -------------- next part -------------- A non-text attachment was scrubbed... Name: fix-managed-window-initial-visibility.patch Type: text/x-patch Size: 618 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20120104/64f3c379/fix-managed-window-initial-visibility.patch From ralf.heini at aicas.de Wed Jan 4 07:46:38 2012 From: ralf.heini at aicas.de (Ralf Heini) Date: Wed, 04 Jan 2012 16:46:38 +0100 Subject: Patch: Fix endless loop because FocusEvents were processed in the wrong order Message-ID: <4F04745E.7000707@aicas.de> This issue came up using a JDialog on Windows. -- Dipl.-Inform. Ralf Heini * Development and Support * Tel: +49-721-663 968-51 aicas GmbH Haid-und-Neu-Stra?e 18 * D-76131 Karlsruhe * Germany http://www.aicas.com * Tel: +49-721-663 968-0 USt-Id: DE216375633, Handelsregister HRB 109481, AG Mannheim Gesch?ftsf?hrer: Dr. James J. Hunt -------------- next part -------------- A non-text attachment was scrubbed... Name: fix-focus-event-loop.patch Type: text/x-patch Size: 826 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20120104/1b85125e/fix-focus-event-loop.patch From roman at kennke.org Thu Jan 5 12:20:27 2012 From: roman at kennke.org (Roman Kennke) Date: Thu, 05 Jan 2012 21:20:27 +0100 Subject: Merge CacioWeb In-Reply-To: <45BEDE89-B92A-4A00-98FC-F551997A4E56@gmail.com> References: <45BEDE89-B92A-4A00-98FC-F551997A4E56@gmail.com> Message-ID: <1325794827.7469.17.camel@moonlight> Hi all, Thanks Mario for bringing this up. First of all let me explain what is Cacio and why we think it's useful. In essence, it is an (somewhat) abstract implementation of AWT peers. It implements all the AWT widgets by using Swing for painting and event/logic processing. This reduces the burden of porting/implementing the Java graphics stack enourmously. Currently, when one wants to port the Java graphics stack, the AWT peers need to be implemented as well, for compatibility. This is a huge effort, and considered rather pointless by many, because AWT is not that widely used anyway. It is particularily difficult on platforms that don't have any native widgets (most embedded platforms). Using Cacio, this effort is reduced to implementing a Java2D backend and some basic windowing functionality. It even provides a windowing implementation in Java for platforms that don't even support windows (e.g. framebuffers). > On the other end, it could make more sense to include Cacio in the > build process of the main JDK, especially since the only usable peer > (and the only being actively developed) is currently the HTML5 one, > and by integrating this in the JDK forest as well, my hope is to > enable builds to pass (or be tested against) the TCK. Well... I would like to point out that we do have implementations for X11 (rather pointless to merge as the JDK has its own more complete X11 backend), SDL and DirectFB, which are not complete or very useful currently, but we plan to finish both of them to state where they are usable. We also have a somewhat special backend which renders exclusively into a BufferedImage and can only process events generated by Robot, which is particularily useful for unit testing GUI applications without messing around with the user's desktop or without requiring graphics on a continuous integration server (extremely useful if you're into this GUI testing thingy). To me, a very important aspect (as you pointed out) is to get access to the TCK to actually verify that Cacio -based backends are compatible AWT implementations. For this reason I guess we should also do a JDK7 based version, as there's no TCK for Java8 yet AFAIK. One more thing: Caciocavallo already *is* a project :-) I guess there's not much to propose here. We even do have our own JDK7-based forest, which is hopelessly outdated by now. So I guess the question is whether we can: 1. Get a JDK8-based forest next to our JDK7-based one, which we would bring up to date. We would integrate the Cacio code into those forests, based on suggestions and discussions that we hopefully get. 1a. Try to get access to the TCK for the JDK7 forest. 2. Once those are working well, if there is interest, merge those forests back into mainline JDK. What do you think? Regards, Roman > I also hope that by having the code directly integrated in the JDK we will be able to reach more testers and fix more issues, since now Cacio is used in very specific environments only. > > In addition to that, in order to support the web peer, we are implementing a number of features that will surely be beneficial for the Java ecosystem, like client filesystem support over the HTML5. > > I believe that those additions could be very useful, and we call this project internally as WebJDK (spoiler: we will unveil something at FOSDEM if you would like to attend and are interested). > > I know that based on the new rules I will have to formally propose a project, but before doing this I want to see if a formal WebJDK would be something interesting for the community and not only for us, and if Cacio would be likely to be integrated in the JDK, or if you prefer the current situation where it's a separate library. > > If accepted, the WebJDK will include a custom JDK8 forest (or perhaps just the patches since are easier to manage) with all the code needed to enable web support (filesystem, deployment code, etc...), plus Cacio and the HTML5 peer code. > > We will develop this in the JDK8 timeframe and hopefully merge everything that makes sense in the "real" JDK9 forest. > > Any ideas, suggestions, criticism? > > Thanks, > Mario > --- > pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF > Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF > > http://www.ladybug-studio.com > > IcedRobot: www.icedrobot.org > Proud GNU Classpath developer: http://www.classpath.org/ > Read About us at: http://planet.classpath.org > OpenJDK: http://openjdk.java.net/projects/caciocavallo/ > > Please, support open standards: > http://endsoftpatents.org/ > > > > From roman at kennke.org Thu Jan 5 12:40:02 2012 From: roman at kennke.org (Roman Kennke) Date: Thu, 05 Jan 2012 21:40:02 +0100 Subject: Patch: Fix endless loop because FocusEvents were processed in the wrong order In-Reply-To: <4F04745E.7000707@aicas.de> References: <4F04745E.7000707@aicas.de> Message-ID: <1325796002.7469.30.camel@moonlight> Hi Ralf, Nice to hear from you! The patch (and the other one you sent) seem to be fine. I will test it (we have a bunch of things that we need to verify don't break) and integrate it asap. I have a little request: There are a couple of things in the code that I know we keep bouncing back and forth and I feel we never really get to a real solution. Both the focus and visibility I remember we have already changed a couple of times, mostly based on experimenting and single (ofter corner) cases that make problems. I really would like to see some little testing for this code, ideally a unit test the shows how the code breaks, and which the patch resolves. This way we avoid that in some future changes we do something that breaks your patch again. The big question of course is how to test it. Especially when something is only exposed on particular platforms. The testing backend (which only draws to BufferedImage and generates events by means of java.awt.Robot) might be very useful here. Maybe you can think about a test that shows the problem, using this testing backend (tta)? You would make me very happy, and ensure the same problem doesn't happen in the future (i.e. make you happy!). Cheers, Roman Am Mittwoch, den 04.01.2012, 16:46 +0100 schrieb Ralf Heini: > This issue came up using a JDialog on Windows. > > Unterschiede zwischen Dateien-Anlage (fix-focus-event-loop.patch) > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioWindowPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioWindowPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioWindowPeer.java Wed Jan 04 16:41:38 2012 +0100 > @@ -226,10 +226,10 @@ > { > // Simulate what the native system thinks is the currently focused window. > CacioKeyboardFocusManagerPeer.getInstance().setCurrentFocusedWindow(w); > + super.handlePeerEvent(ev); > WindowEvent we = > new WindowEvent(w, WindowEvent.WINDOW_GAINED_FOCUS); > super.handlePeerEvent(we); > - super.handlePeerEvent(ev); > } > break; > case FocusEvent.FOCUS_LOST: From roman at kennke.org Thu Jan 5 12:50:01 2012 From: roman at kennke.org (Roman Kennke) Date: Thu, 05 Jan 2012 21:50:01 +0100 Subject: Merge CacioWeb In-Reply-To: <4F046D8D.2080102@aicas.de> References: <45BEDE89-B92A-4A00-98FC-F551997A4E56@gmail.com> <4F046D8D.2080102@aicas.de> Message-ID: <1325796601.7469.34.camel@moonlight> Hi Ralf, > It's nice to hear that Cacio evolves. :-) We'd be happy if Cacio and > CacioWeb will make it into the official OpenJDK. Thanks :-) > As we have several graphical implementations here using Cacio (Win32, > QNX Photon, MAUI, WindML and even more experimental ones), we found > out that lots of code is duplicated in each target, like the > generation of mouse "clicked" events. It would be nice if those things > were part of the abstract implementation. Yea I agree, there's lots of potential for consolidation here. Something I always wanted to do and never got around to actually doing it :-) > We'd like to pass our changes like bug fixes, clean-up, documentation > and maybe even refactoring to the Cacio project. We still use OpenJDK6 > here and probably will continue our development there for some time so > we need to work around JDK7 stuff. I hope this will be possible for > quite a while. We don't actively follow OpenJDK6 (which is an early fork off OpenJDK7 and not based on JDK6 at all). Now that JDK7 doesn't really change anymore, it should be easy to follow. I doubt we will create a fork for JDK7 and backporting new changes to it though, feel free to do that if you like ;-) Cheers, Roman From kadir at bayner.com Fri Jan 6 05:14:01 2012 From: kadir at bayner.com (Kadir BASOL) Date: Fri, 06 Jan 2012 15:14:01 +0200 Subject: jsunzip support on webjdk ? Message-ID: <4F06F399.9020501@bayner.com> It would be good for compress and decompress swing operations with jsunzip html5 ability... https://github.com/augustl/js-unzip or better solution? From ralf.heini at aicas.de Mon Jan 9 00:34:07 2012 From: ralf.heini at aicas.de (Ralf Heini) Date: Mon, 09 Jan 2012 09:34:07 +0100 Subject: Patch: Fix endless loop because FocusEvents were processed in the wrong order In-Reply-To: <1325796002.7469.30.camel@moonlight> References: <4F04745E.7000707@aicas.de> <1325796002.7469.30.camel@moonlight> Message-ID: <4F0AA67F.2060704@aicas.de> Hi Roman, I agree that we are really kind of "patching" the code and to ensure that all kinds of focus handling (and setting the visibility) works fine on every platform is an important goal. And to be sure that everything will still work fine in the future would really make me happy! :-) So I will have a look at the testing backend. I will probably need to use OpenJDK because JamaicaVM unfortunately does not fully support the Robot yet. For further patches, we also want to test (manually) against the CacioWeb implementation as this is currently the most important one for Cacio. Cheerio, Ralf Roman Kennke schrieb: > Hi Ralf, > > Nice to hear from you! > > The patch (and the other one you sent) seem to be fine. I will test it > (we have a bunch of things that we need to verify don't break) and > integrate it asap. > > I have a little request: There are a couple of things in the code that I > know we keep bouncing back and forth and I feel we never really get to a > real solution. Both the focus and visibility I remember we have already > changed a couple of times, mostly based on experimenting and single > (ofter corner) cases that make problems. I really would like to see some > little testing for this code, ideally a unit test the shows how the code > breaks, and which the patch resolves. This way we avoid that in some > future changes we do something that breaks your patch again. > > The big question of course is how to test it. Especially when something > is only exposed on particular platforms. The testing backend (which only > draws to BufferedImage and generates events by means of java.awt.Robot) > might be very useful here. Maybe you can think about a test that shows > the problem, using this testing backend (tta)? You would make me very > happy, and ensure the same problem doesn't happen in the future (i.e. > make you happy!). > > Cheers, Roman > > Am Mittwoch, den 04.01.2012, 16:46 +0100 schrieb Ralf Heini: >> This issue came up using a JDialog on Windows. >> >> Unterschiede zwischen Dateien-Anlage (fix-focus-event-loop.patch) >> diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioWindowPeer.java >> --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioWindowPeer.java Fri Dec 30 17:09:13 2011 +0100 >> +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioWindowPeer.java Wed Jan 04 16:41:38 2012 +0100 >> @@ -226,10 +226,10 @@ >> { >> // Simulate what the native system thinks is the currently focused window. >> CacioKeyboardFocusManagerPeer.getInstance().setCurrentFocusedWindow(w); >> + super.handlePeerEvent(ev); >> WindowEvent we = >> new WindowEvent(w, WindowEvent.WINDOW_GAINED_FOCUS); >> super.handlePeerEvent(we); >> - super.handlePeerEvent(ev); >> } >> break; >> case FocusEvent.FOCUS_LOST: > > -- Dipl.-Inform. Ralf Heini * Development and Support * Tel: +49-721-663 968-51 aicas GmbH Haid-und-Neu-Stra?e 18 * D-76131 Karlsruhe * Germany http://www.aicas.com * Tel: +49-721-663 968-0 USt-Id: DE216375633, Handelsregister HRB 109481, AG Mannheim Gesch?ftsf?hrer: Dr. James J. Hunt From neugens.limasoftware at gmail.com Mon Jan 9 00:56:56 2012 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Mon, 9 Jan 2012 09:56:56 +0100 Subject: Patch: Fix endless loop because FocusEvents were processed in the wrong order In-Reply-To: <4F0AA67F.2060704@aicas.de> References: <4F04745E.7000707@aicas.de> <1325796002.7469.30.camel@moonlight> <4F0AA67F.2060704@aicas.de> Message-ID: <57F325BB-71CC-472C-B537-F06831E7D1DC@gmail.com> Il giorno 09/gen/2012, alle ore 09:34, Ralf Heini ha scritto: > Hi Roman, > > I agree that we are really kind of "patching" the code and to ensure that all kinds of focus handling (and setting the visibility) works fine on every platform is an important goal. And to be sure that everything will still work fine in the future would really make me happy! :-) > > So I will have a look at the testing backend. I will probably need to use OpenJDK because JamaicaVM unfortunately does not fully support the Robot yet. For further patches, we also want to test (manually) against the CacioWeb implementation as this is currently the most important one for Cacio. > > Cheerio, > Ralf Hi Ralf! This is nice. Since OpenJDK 7 is the reference implementation I think it's correct to also use it as a primary testing platform. Furthermore, I think it will be very cool if aicas will want to integrate the testing backend in its testing framework. If you need any help please, don't hesitate to ask! Cheers, Mario --- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF http://www.ladybug-studio.com IcedRobot: www.icedrobot.org Proud GNU Classpath developer: http://www.classpath.org/ Read About us at: http://planet.classpath.org OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/ From ralf.heini at aicas.de Tue Jan 10 07:16:06 2012 From: ralf.heini at aicas.de (Ralf Heini) Date: Tue, 10 Jan 2012 16:16:06 +0100 Subject: CacioEventSource Message-ID: <4F0C5636.80004@aicas.de> Hi there, Analyzing Cacio via JDepend I detected one cyclic dependency between "sun.awt.peer.cacio" and "sun.awt.peer.cacio.managed": CacioEventSource. This class is used by "managed" code only. Should this become part of the "managed" package? I admit that the design is not clear to me. Best regards, Ralf From ralf.heini at aicas.de Wed Jan 11 07:42:57 2012 From: ralf.heini at aicas.de (Ralf Heini) Date: Wed, 11 Jan 2012 16:42:57 +0100 Subject: Patch: Organize Imports in "cacio-shared" Message-ID: <4F0DAE01.106@aicas.de> Some imports are obsolete and show warnings in Eclipse. Used Eclipse to organize the imports. Called "mvn clean install" to test the changes. -- Dipl.-Inform. Ralf Heini * Development and Support * Tel: +49-721-663 968-51 aicas GmbH Haid-und-Neu-Stra?e 18 * D-76131 Karlsruhe * Germany http://www.aicas.com * Tel: +49-721-663 968-0 USt-Id: DE216375633, Handelsregister HRB 109481, AG Mannheim Gesch?ftsf?hrer: Dr. James J. Hunt -------------- next part -------------- A non-text attachment was scrubbed... Name: cacio-shared-imports.diff Type: text/x-patch Size: 22240 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20120111/7782a0e9/cacio-shared-imports.diff From ralf.heini at aicas.de Wed Jan 11 09:32:31 2012 From: ralf.heini at aicas.de (Ralf Heini) Date: Wed, 11 Jan 2012 18:32:31 +0100 Subject: Patch: Update Eclipse classpath Message-ID: <4F0DC7AF.30404@aicas.de> The files were restructured but the project not updated. Note: There are still some empty directories around that have been moved. The SDL and X11 stuff should be moved somewhere else. -- Dipl.-Inform. Ralf Heini * Development and Support * Tel: +49-721-663 968-51 aicas GmbH Haid-und-Neu-Stra?e 18 * D-76131 Karlsruhe * Germany http://www.aicas.com * Tel: +49-721-663 968-0 USt-Id: DE216375633, Handelsregister HRB 109481, AG Mannheim Gesch?ftsf?hrer: Dr. James J. Hunt -------------- next part -------------- A non-text attachment was scrubbed... Name: cacio-classpath-update.patch Type: text/x-patch Size: 1217 bytes Desc: not available Url : http://mail.openjdk.java.net/pipermail/caciocavallo-dev/attachments/20120111/e31702d3/cacio-classpath-update.patch From neugens.limasoftware at gmail.com Fri Jan 13 13:44:11 2012 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Fri, 13 Jan 2012 22:44:11 +0100 Subject: Merge CacioWeb In-Reply-To: <73CF7BAA-BB54-48A1-AF2F-A8DC651C2B3C@oracle.com> References: <45BEDE89-B92A-4A00-98FC-F551997A4E56@gmail.com> <1325794827.7469.17.camel@moonlight> <73CF7BAA-BB54-48A1-AF2F-A8DC651C2B3C@oracle.com> Message-ID: <7B4EA99F-4B56-48FD-A465-5ABAD55C5092@gmail.com> Il giorno 13/gen/2012, alle ore 17:42, Richard Bair ha scritto: > > On Jan 5, 2012, at 12:20 PM, Roman Kennke wrote: > >> Hi all, >> >> Thanks Mario for bringing this up. >> >> First of all let me explain what is Cacio and why we think it's useful. >> In essence, it is an (somewhat) abstract implementation of AWT peers. It >> implements all the AWT widgets by using Swing for painting and >> event/logic processing. This reduces the burden of porting/implementing >> the Java graphics stack enourmously. Currently, when one wants to port >> the Java graphics stack, the AWT peers need to be implemented as well, >> for compatibility. This is a huge effort, and considered rather >> pointless by many, because AWT is not that widely used anyway. It is >> particularily difficult on platforms that don't have any native widgets >> (most embedded platforms). Using Cacio, this effort is reduced to >> implementing a Java2D backend and some basic windowing functionality. It >> even provides a windowing implementation in Java for platforms that >> don't even support windows (e.g. framebuffers). > > Funny thing, I believe the Mac OS port uses this same technique. Does anybody know what the differences are between the two? :) I think they may have used some ideas :) but we didn't participate in the process. Back ten I suggested to use Cacio (and improve upon it), but I didn't receive any follow up. The design is quite similar indeed. >> We also have a somewhat special backend which renders >> exclusively into a BufferedImage and can only process events generated >> by Robot, which is particularily useful for unit testing GUI >> applications without messing around with the user's desktop or without >> requiring graphics on a continuous integration server (extremely useful >> if you're into this GUI testing thingy). > > That would be very cool. The SQE team uses robot / image testing heavily for FX and "taking over my computer" is one of the chief problems with it (the other being image tests are finicky). Cacio is a Java2D backend in the end, I don't know if it works with JavaFX, but it would be nice to give it a try, maybe you could help us on that? :) Cheers, Mario --- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF http://www.ladybug-studio.com IcedRobot: www.icedrobot.org Proud GNU Classpath developer: http://www.classpath.org/ Read About us at: http://planet.classpath.org OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/ From roman at kennke.org Mon Jan 23 11:33:14 2012 From: roman at kennke.org (Roman Kennke) Date: Mon, 23 Jan 2012 20:33:14 +0100 Subject: Patch: Organize Imports in "cacio-shared" In-Reply-To: <4F0DAE01.106@aicas.de> References: <4F0DAE01.106@aicas.de> Message-ID: <1327347194.2054.45.camel@moonlight> Sorry for the late reply. I think the change is ok. I guess we should wait for checking the contribution status of aicas and try to get you Mercurial access. Cheers, Roman Am Mittwoch, den 11.01.2012, 16:42 +0100 schrieb Ralf Heini: > Some imports are obsolete and show warnings in Eclipse. Used Eclipse to organize the imports. Called "mvn clean install" to test the changes. > > Unterschiede zwischen Dateien-Anlage (cacio-shared-imports.diff) > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/BlitClipHelper.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/BlitClipHelper.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/BlitClipHelper.java Wed Jan 11 16:38:35 2012 +0100 > @@ -26,7 +26,7 @@ > package sun.awt.peer.cacio; > > import java.awt.Composite; > -import java.awt.Rectangle; > + > import sun.java2d.SurfaceData; > import sun.java2d.pipe.Region; > import sun.java2d.pipe.SpanIterator; > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioCanvasPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioCanvasPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioCanvasPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -29,6 +29,7 @@ > import java.awt.Graphics; > import java.awt.GraphicsConfiguration; > import java.awt.peer.CanvasPeer; > + > import javax.swing.JPanel; > > class CacioCanvasPeer extends CacioComponentPeer > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioCheckboxMenuItemPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioCheckboxMenuItemPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioCheckboxMenuItemPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -30,6 +30,7 @@ > import java.awt.event.ItemEvent; > import java.awt.event.ItemListener; > import java.awt.peer.CheckboxMenuItemPeer; > + > import javax.swing.JCheckBoxMenuItem; > > class CacioCheckboxMenuItemPeer extends CacioMenuItemPeer > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioChoicePeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioChoicePeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioChoicePeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -29,6 +29,7 @@ > import java.awt.event.ItemEvent; > import java.awt.event.ItemListener; > import java.awt.peer.ChoicePeer; > + > import javax.swing.ComboBoxModel; > import javax.swing.JComboBox; > import javax.swing.MutableComboBoxModel; > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioComponentPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioComponentPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioComponentPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -43,34 +43,27 @@ > import java.awt.Point; > import java.awt.Rectangle; > import java.awt.Toolkit; > -import java.awt.Transparency; > -import java.awt.Window; > - > import java.awt.event.FocusEvent; > import java.awt.event.KeyEvent; > import java.awt.event.MouseEvent; > import java.awt.event.PaintEvent; > - > import java.awt.image.ColorModel; > import java.awt.image.ImageObserver; > import java.awt.image.ImageProducer; > import java.awt.image.VolatileImage; > -import java.awt.image.WritableRaster; > - > import java.awt.peer.ComponentPeer; > import java.awt.peer.ContainerPeer; > > import javax.swing.JComponent; > > +import sun.awt.CausedFocusEvent.Cause; > +import sun.awt.AWTAccessor; > +import sun.awt.ConstrainableGraphics; > +import sun.awt.PaintEventDispatcher; > +import sun.awt.RepaintArea; > import sun.awt.SunToolkit; > -import sun.awt.CausedFocusEvent.Cause; > -import sun.awt.*; > - > -import sun.awt.RepaintArea; > import sun.awt.event.IgnorePaintEvent; > -import sun.awt.image.OffScreenImage; > import sun.font.FontDesignMetrics; > - > import sun.java2d.pipe.Region; > > /** > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioContainerPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioContainerPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioContainerPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -35,9 +35,10 @@ > import java.awt.event.PaintEvent; > import java.awt.peer.ComponentPeer; > import java.awt.peer.ContainerPeer; > + > import javax.swing.JComponent; > > -import sun.awt.*; > +import sun.awt.AWTAccessor; > > abstract class CacioContainerPeer > extends CacioComponentPeer > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioDialogPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioDialogPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioDialogPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -33,7 +33,7 @@ > > import javax.swing.JRootPane; > > -import sun.awt.*; > +import sun.awt.AWTAccessor; > > class CacioDialogPeer extends CacioWindowPeer implements DialogPeer { > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioEventPump.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioEventPump.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioEventPump.java Wed Jan 11 16:38:35 2012 +0100 > @@ -26,17 +26,16 @@ > package sun.awt.peer.cacio; > > import java.awt.AWTEvent; > - > +import java.awt.Component; > import java.awt.Window; > -import java.awt.Component; > import java.awt.event.ComponentEvent; > import java.awt.event.FocusEvent; > import java.awt.event.KeyEvent; > import java.awt.event.MouseEvent; > import java.awt.event.PaintEvent; > import java.awt.event.WindowEvent; > + > import sun.awt.AWTAutoShutdown; > - > import sun.awt.PaintEventDispatcher; > > /** > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioFileDialogPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioFileDialogPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioFileDialogPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -29,6 +29,7 @@ > import java.awt.peer.FileDialogPeer; > import java.io.File; > import java.io.FilenameFilter; > + > import javax.swing.JFileChooser; > import javax.swing.filechooser.FileFilter; > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioFramePeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioFramePeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioFramePeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -29,8 +29,8 @@ > import java.awt.MenuBar; > import java.awt.Rectangle; > import java.awt.peer.FramePeer; > +import java.awt.peer.MenuBarPeer; > > -import java.awt.peer.MenuBarPeer; > import javax.swing.JMenuBar; > import javax.swing.JRootPane; > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioKeyboardFocusManagerPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioKeyboardFocusManagerPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioKeyboardFocusManagerPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -27,9 +27,11 @@ > > import java.awt.AWTEvent; > import java.awt.Component; > +import java.awt.KeyboardFocusManager; > import java.awt.Window; > import java.awt.event.FocusEvent; > import java.awt.peer.KeyboardFocusManagerPeer; > + > import sun.awt.AppContext; > import sun.awt.CausedFocusEvent; > import sun.awt.CausedFocusEvent.Cause; > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuBarPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuBarPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuBarPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -29,6 +29,7 @@ > import java.awt.MenuBar; > import java.awt.peer.MenuBarPeer; > import java.awt.peer.MenuPeer; > + > import javax.swing.JMenu; > import javax.swing.JMenuBar; > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuComponentPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuComponentPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuComponentPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -28,6 +28,7 @@ > import java.awt.Font; > import java.awt.MenuComponent; > import java.awt.peer.MenuComponentPeer; > + > import javax.swing.JComponent; > > class CacioMenuComponentPeer diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuItemPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuItemPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuItemPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -29,6 +29,7 @@ > import java.awt.event.ActionEvent; > import java.awt.event.ActionListener; > import java.awt.peer.MenuItemPeer; > + > import javax.swing.JMenuItem; > > class CacioMenuItemPeer extends CacioMenuComponentPeer > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioMenuPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -29,6 +29,7 @@ > import java.awt.MenuItem; > import java.awt.peer.MenuItemPeer; > import java.awt.peer.MenuPeer; > + > import javax.swing.JMenu; > import javax.swing.JMenuItem; > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioPopupMenuPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioPopupMenuPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioPopupMenuPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -29,6 +29,7 @@ > import java.awt.Event; > import java.awt.PopupMenu; > import java.awt.peer.PopupMenuPeer; > + > import javax.swing.JMenu; > import javax.swing.JPopupMenu; > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioScrollBarPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioScrollBarPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioScrollBarPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -27,6 +27,7 @@ > > import java.awt.Scrollbar; > import java.awt.peer.ScrollbarPeer; > + > import javax.swing.JScrollBar; > > class CacioScrollBarPeer extends CacioComponentPeer > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioScrollPanePeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioScrollPanePeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioScrollPanePeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -28,15 +28,14 @@ > import java.awt.Adjustable; > import java.awt.Component; > import java.awt.Dimension; > -import java.awt.Graphics; > import java.awt.ScrollPane; > import java.awt.peer.ComponentPeer; > import java.awt.peer.ScrollPanePeer; > + > import javax.swing.JPanel; > import javax.swing.JScrollBar; > -import javax.swing.JScrollPane; > > -import sun.awt.*; > +import sun.awt.AWTAccessor; > > class CacioScrollPanePeer extends CacioContainerPeer > implements ScrollPanePeer { > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioSwingComponent.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioSwingComponent.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioSwingComponent.java Wed Jan 11 16:38:35 2012 +0100 > @@ -25,6 +25,7 @@ > > package sun.awt.peer.cacio; > > +import java.awt.Component; > import java.awt.event.FocusEvent; > import java.awt.event.KeyEvent; > import java.awt.event.MouseEvent; > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioTextAreaPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioTextAreaPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioTextAreaPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -25,16 +25,11 @@ > > package sun.awt.peer.cacio; > > -import java.awt.AWTEvent; > import java.awt.Dimension; > import java.awt.Font; > import java.awt.FontMetrics; > -import java.awt.Graphics; > -import java.awt.Paint; > import java.awt.TextArea; > -import java.awt.event.PaintEvent; > import java.awt.im.InputMethodRequests; > -import java.awt.peer.ContainerPeer; > import java.awt.peer.TextAreaPeer; > > import javax.swing.JScrollPane; > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioTextFieldPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioTextFieldPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioTextFieldPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -2,12 +2,9 @@ > > import java.awt.Dimension; > import java.awt.TextField; > - > import java.awt.event.ActionEvent; > import java.awt.event.ActionListener; > - > import java.awt.im.InputMethodRequests; > - > import java.awt.peer.TextFieldPeer; > > import javax.swing.JPasswordField; > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/CacioWindowPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioWindowPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/CacioWindowPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -48,7 +48,7 @@ > import javax.swing.UIManager; > import javax.swing.border.Border; > > -import sun.awt.*; > +import sun.awt.AWTAccessor; > > class CacioWindowPeer extends CacioContainerPeer > implements WindowPeer { > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/KFMHelper.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/KFMHelper.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/KFMHelper.java Wed Jan 11 16:38:35 2012 +0100 > @@ -27,8 +27,8 @@ > > import java.awt.Component; > import java.awt.KeyboardFocusManager; > +import java.lang.reflect.InvocationTargetException; > import java.lang.reflect.Method; > -import java.lang.reflect.InvocationTargetException; > import java.security.AccessController; > import java.security.PrivilegedActionException; > import java.security.PrivilegedExceptionAction; > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/PlatformToplevelWindow.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/PlatformToplevelWindow.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/PlatformToplevelWindow.java Wed Jan 11 16:38:35 2012 +0100 > @@ -25,8 +25,10 @@ > > package sun.awt.peer.cacio; > > +import java.awt.Dialog; > import java.awt.Frame; > import java.awt.Rectangle; > +import java.awt.peer.WindowPeer; > > public interface PlatformToplevelWindow extends PlatformWindow { > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/PlatformWindow.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/PlatformWindow.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/PlatformWindow.java Wed Jan 11 16:38:35 2012 +0100 > @@ -27,16 +27,16 @@ > > import java.awt.AWTException; > import java.awt.BufferCapabilities; > +import java.awt.BufferCapabilities.FlipContents; > import java.awt.Color; > import java.awt.Component; > import java.awt.Font; > import java.awt.Graphics2D; > +import java.awt.GraphicsConfiguration; > import java.awt.Image; > import java.awt.Insets; > import java.awt.Point; > import java.awt.Rectangle; > -import java.awt.BufferCapabilities.FlipContents; > -import java.awt.GraphicsConfiguration; > import java.awt.image.ColorModel; > import java.awt.peer.ComponentPeer; > import java.awt.peer.ContainerPeer; > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/PlatformWindowFactory.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/PlatformWindowFactory.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/PlatformWindowFactory.java Wed Jan 11 16:38:35 2012 +0100 > @@ -25,8 +25,6 @@ > > package sun.awt.peer.cacio; > > -import java.awt.GraphicsDevice; > - > /** > * Creates {@link PlatformWindow} instances for use by the component peers. > */ > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/ProxyWindow.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/ProxyWindow.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/ProxyWindow.java Wed Jan 11 16:38:35 2012 +0100 > @@ -33,6 +33,7 @@ > import java.awt.event.MouseEvent; > import java.lang.reflect.Field; > import java.lang.reflect.Method; > + > import javax.swing.JComponent; > > /** > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/ProxyWindowPeer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/ProxyWindowPeer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/ProxyWindowPeer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -50,6 +50,7 @@ > import java.awt.peer.ComponentPeer; > import java.awt.peer.ContainerPeer; > import java.awt.peer.WindowPeer; > + > import sun.awt.CausedFocusEvent.Cause; > import sun.java2d.pipe.Region; > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/WindowClippedGraphics.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/WindowClippedGraphics.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/WindowClippedGraphics.java Wed Jan 11 16:38:35 2012 +0100 > @@ -37,9 +37,9 @@ > import java.awt.Polygon; > import java.awt.Rectangle; > import java.awt.RenderingHints; > +import java.awt.RenderingHints.Key; > import java.awt.Shape; > import java.awt.Stroke; > -import java.awt.RenderingHints.Key; > import java.awt.font.FontRenderContext; > import java.awt.font.GlyphVector; > import java.awt.geom.AffineTransform; > @@ -53,6 +53,7 @@ > import java.awt.image.renderable.RenderableImage; > import java.text.AttributedCharacterIterator; > import java.util.Map; > + > import sun.awt.ConstrainableGraphics; > > public class WindowClippedGraphics extends Graphics2D > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/managed/AbstractManagedWindowContainer.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/AbstractManagedWindowContainer.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/AbstractManagedWindowContainer.java Wed Jan 11 16:38:35 2012 +0100 > @@ -30,11 +30,12 @@ > import java.awt.Graphics2D; > import java.awt.Point; > import java.awt.Rectangle; > +import java.awt.event.KeyEvent; > import java.awt.event.MouseEvent; > -import java.awt.event.KeyEvent; > import java.awt.geom.Rectangle2D; > +import java.util.Iterator; > import java.util.LinkedList; > -import java.util.Iterator; > + > import sun.awt.peer.cacio.CacioComponent; > > /** > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/managed/EventData.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/EventData.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/EventData.java Wed Jan 11 16:38:35 2012 +0100 > @@ -28,7 +28,11 @@ > import java.awt.AWTEvent; > import java.awt.Component; > import java.awt.Rectangle; > -import java.awt.event.*; > +import java.awt.event.ComponentEvent; > +import java.awt.event.KeyEvent; > +import java.awt.event.MouseEvent; > +import java.awt.event.MouseWheelEvent; > +import java.awt.event.PaintEvent; > > public class EventData { > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/managed/FocusManager.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/FocusManager.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/FocusManager.java Wed Jan 11 16:38:35 2012 +0100 > @@ -25,13 +25,14 @@ > > package sun.awt.peer.cacio.managed; > > -import sun.awt.peer.cacio.*; > -import sun.security.action.*; > - > import java.awt.Component; > import java.awt.event.FocusEvent; > -import java.security.*; > -import java.util.logging.*; > +import java.security.AccessController; > +import java.util.logging.Level; > +import java.util.logging.Logger; > + > +import sun.awt.peer.cacio.CacioComponent; > +import sun.security.action.GetPropertyAction; > > public class FocusManager { > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/managed/FullScreenEventPump.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/FullScreenEventPump.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/FullScreenEventPump.java Wed Jan 11 16:38:35 2012 +0100 > @@ -25,7 +25,8 @@ > > package sun.awt.peer.cacio.managed; > > -import sun.awt.peer.cacio.*; > +import sun.awt.peer.cacio.CacioEventPump; > +import sun.awt.peer.cacio.CacioEventSource; > > public class FullScreenEventPump extends CacioEventPump { > > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/managed/FullScreenWindowFactory.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/FullScreenWindowFactory.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/FullScreenWindowFactory.java Wed Jan 11 16:38:35 2012 +0100 > @@ -27,7 +27,6 @@ > > import java.awt.Dimension; > import java.awt.GraphicsConfiguration; > -import java.awt.GraphicsDevice; > import java.security.AccessController; > import java.util.Collections; > import java.util.HashMap; > diff -r 5601f95ef66a cacio-shared/src/main/java/sun/awt/peer/cacio/managed/ManagedWindow.java > --- a/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/ManagedWindow.java Fri Dec 30 17:09:13 2011 +0100 > +++ b/cacio-shared/src/main/java/sun/awt/peer/cacio/managed/ManagedWindow.java Wed Jan 11 16:38:35 2012 +0100 > @@ -25,10 +25,10 @@ > > package sun.awt.peer.cacio.managed; > > -import sun.awt.peer.cacio.*; > import java.awt.AWTEvent; > import java.awt.AWTException; > import java.awt.BufferCapabilities; > +import java.awt.BufferCapabilities.FlipContents; > import java.awt.Color; > import java.awt.Component; > import java.awt.Font; > @@ -38,11 +38,10 @@ > import java.awt.Insets; > import java.awt.Point; > import java.awt.Rectangle; > -import java.awt.BufferCapabilities.FlipContents; > import java.awt.event.MouseEvent; > import java.awt.event.PaintEvent; > +import java.awt.image.ColorModel; > import java.awt.peer.ContainerPeer; > -import java.awt.image.ColorModel; > import java.util.Deque; > import java.util.Iterator; > import java.util.LinkedList; > @@ -50,6 +49,9 @@ > > import sun.awt.CausedFocusEvent.Cause; > import sun.awt.ConstrainableGraphics; > +import sun.awt.peer.cacio.CacioComponent; > +import sun.awt.peer.cacio.PlatformToplevelWindow; > +import sun.awt.peer.cacio.PlatformWindow; > import sun.java2d.pipe.Region; > > /** From roman at kennke.org Mon Jan 23 11:34:58 2012 From: roman at kennke.org (Roman Kennke) Date: Mon, 23 Jan 2012 20:34:58 +0100 Subject: Patch: Update Eclipse classpath In-Reply-To: <4F0DC7AF.30404@aicas.de> References: <4F0DC7AF.30404@aicas.de> Message-ID: <1327347298.2054.47.camel@moonlight> Hi Ralf, I think we should remove those Eclipse files altogether. Since the projects are now using Maven, it's possible to open as Maven project and Eclipse (or whatever is your preferred IDE) can infer all settings from the pom.xml. This is one of the big advantages of Maven: it makes projects IDE agnostic. We need to see what to do with the other directories. I will have a look at that soon. I will also finally get around to push my DirectFB port. Cheers, Roman Am Mittwoch, den 11.01.2012, 18:32 +0100 schrieb Ralf Heini: > The files were restructured but the project not updated. > Note: There are still some empty directories around that have been moved. The SDL and X11 stuff should be moved somewhere else. > > Unterschiede zwischen Dateien-Anlage (cacio-classpath-update.patch) > # HG changeset patch > # User Ralf Heini > # Date 1326302953 -3600 > # Node ID e46e22a4a8be887a2f235c4edcbb9ed3a7bbeb1e > # Parent 70702d3e6a642905b592a105bd0e9a4536697d8e > Update Eclipse classpath > > diff -r 70702d3e6a64 -r e46e22a4a8be .classpath > --- a/.classpath Wed Jan 11 16:44:08 2012 +0100 > +++ b/.classpath Wed Jan 11 18:29:13 2012 +0100 > @@ -1,7 +1,13 @@ > > > - > - > + > + > + > + > + > + > + > + > > > From neugens.limasoftware at gmail.com Mon Jan 23 11:58:29 2012 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Mon, 23 Jan 2012 20:58:29 +0100 Subject: Patch: Organize Imports in "cacio-shared" In-Reply-To: <1327347194.2054.45.camel@moonlight> References: <4F0DAE01.106@aicas.de> <1327347194.2054.45.camel@moonlight> Message-ID: Il giorno 23/gen/2012, alle ore 20:33, Roman Kennke ha scritto: > Sorry for the late reply. I think the change is ok. I guess we should > wait for checking the contribution status of aicas and try to get you > Mercurial access. > > Cheers, Roman I actually asked Mark (in CC) a couple of weeks ago to let me know if aicas' OCA is still valid. Mark (or Dalibor, in CC too), can you please check this for us? Thanks :) Roman, if the OCA is fine, we can proceed with the request to allow Ralf as a project contributor (as per bylaws definitions). Cheers, Mario --- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF http://www.ladybug-studio.com IcedRobot: www.icedrobot.org Proud GNU Classpath developer: http://www.classpath.org/ Read About us at: http://planet.classpath.org OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/ From ralf.heini at aicas.de Tue Jan 24 02:07:34 2012 From: ralf.heini at aicas.de (Ralf Heini) Date: Tue, 24 Jan 2012 11:07:34 +0100 Subject: Patch: Update Eclipse classpath In-Reply-To: <1327347298.2054.47.camel@moonlight> References: <4F0DC7AF.30404@aicas.de> <1327347298.2054.47.camel@moonlight> Message-ID: <4F1E82E6.5020206@aicas.de> Hi Roman, Thanks for your reply. I was not aware that Maven can do that so you are probably right. I'm just starting to get experience with Maven. @Mario: Thanks for your request! :-) Best regards, Ralf Roman Kennke schrieb: > Hi Ralf, > > I think we should remove those Eclipse files altogether. Since the > projects are now using Maven, it's possible to open as Maven project and > Eclipse (or whatever is your preferred IDE) can infer all settings from > the pom.xml. This is one of the big advantages of Maven: it makes > projects IDE agnostic. > > We need to see what to do with the other directories. I will have a look > at that soon. I will also finally get around to push my DirectFB port. > > Cheers, Roman > > Am Mittwoch, den 11.01.2012, 18:32 +0100 schrieb Ralf Heini: >> The files were restructured but the project not updated. >> Note: There are still some empty directories around that have been moved. The SDL and X11 stuff should be moved somewhere else. >> >> Unterschiede zwischen Dateien-Anlage (cacio-classpath-update.patch) >> # HG changeset patch >> # User Ralf Heini >> # Date 1326302953 -3600 >> # Node ID e46e22a4a8be887a2f235c4edcbb9ed3a7bbeb1e >> # Parent 70702d3e6a642905b592a105bd0e9a4536697d8e >> Update Eclipse classpath >> >> diff -r 70702d3e6a64 -r e46e22a4a8be .classpath >> --- a/.classpath Wed Jan 11 16:44:08 2012 +0100 >> +++ b/.classpath Wed Jan 11 18:29:13 2012 +0100 >> @@ -1,7 +1,13 @@ >> >> >> - >> - >> + >> + >> + >> + >> + >> + >> + >> + >> >> >> > > From dalibor.topic at oracle.com Tue Jan 24 16:20:42 2012 From: dalibor.topic at oracle.com (Dalibor Topic) Date: Tue, 24 Jan 2012 16:20:42 -0800 Subject: Patch: Organize Imports in "cacio-shared" In-Reply-To: References: <4F0DAE01.106@aicas.de> <1327347194.2054.45.camel@moonlight> Message-ID: <4F1F4ADA.4080406@oracle.com> On 1/23/12 11:58 AM, Mario Torre wrote: > Il giorno 23/gen/2012, alle ore 20:33, Roman Kennke ha scritto: >> Sorry for the late reply. I think the change is ok. I guess we should >> wait for checking the contribution status of aicas and try to get you >> Mercurial access. >> >> Cheers, Roman > > I actually asked Mark (in CC) a couple of weeks ago to let me know if aicas' OCA is still valid. I took a quick look at that, and Aicas would need to submit a fresh OCA. Please see http://openjdk.java.net/contribute/ for details on how to do that. cheers, dalibor topic -- Oracle Dalibor Topic | Java F/OSS Ambassador Phone: +494023646738 | Mobile: +491772664192 Oracle Java Platform Group ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Gesch?ftsf?hrer: J?rgen Kunz Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Astrid Kepper, Val Maher Green Oracle Oracle is committed to developing practices and products that help protect the environment From neugens.limasoftware at gmail.com Wed Jan 25 00:12:20 2012 From: neugens.limasoftware at gmail.com (Mario Torre) Date: Wed, 25 Jan 2012 09:12:20 +0100 Subject: Patch: Organize Imports in "cacio-shared" In-Reply-To: <4F1F4ADA.4080406@oracle.com> References: <4F0DAE01.106@aicas.de> <1327347194.2054.45.camel@moonlight> <4F1F4ADA.4080406@oracle.com> Message-ID: <5040EC0C-6A15-46A7-99D5-55130915B231@gmail.com> Il giorno 25/gen/2012, alle ore 01:20, Dalibor Topic ha scritto: > I took a quick look at that, and Aicas would need to submit a fresh OCA. Please see > http://openjdk.java.net/contribute/ for details on how to do that. Thanks Dalibor, Cheers, Mario --- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF http://www.ladybug-studio.com IcedRobot: www.icedrobot.org Proud GNU Classpath developer: http://www.classpath.org/ Read About us at: http://planet.classpath.org OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/