linuxhippy at gmail.com
Thu Mar 3 05:19:29 PST 2011
I am working on a small university-project where the goal is to
execute awt/java2d applications directly on an application server and
re-direct its output to a web-browser.
My plan would be to render to a BufferedImage and send only updated
areas using dirty tracking.
Caciocavallo seems like a perfect fit with its lightweight
peer-implementation and the PlatformScreen abstraction, dirty tracking
could be done through the surface-locking functions.
I had a look at the SDL implementation, but I haven't found how
input-handling is done.
If this isn't a part Cacio cares about, do you have some pointers
where to start?
More information about the caciocavallo-dev