On 1/3/12 1:53 AM, Mario Torre wrote:
> Hello all,
Ugh, cross-post overload. I'll limit my reply to what seems like the most
appropriate mailing list.
> 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
>>> 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
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 i
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 Swi
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 burde
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
