How much has been pushed upstream?
neugens.limasoftware at gmail.com
Mon Sep 21 04:51:03 PDT 2009
Il 21/09/2009 13:33, Michael Franz ha scritto:
>> You don't need anymore those patches, with the latest FontManager push,
>> everything is upstream now, so just use the Cacio repo, it's completely self
>> So, I should use http://hg.openjdk.java.net/caciocavallo/jdk7/ ? If
> everything is pushed upstream can I also use
Well, Cacio itself is not upstream, but it doesn't require any new
patches. It should be in sync with the current OpenJDK, but because the
internal API is changing a lot, you may need to add or remove some
methods, but most of the time, it's enough to either return false or do
>> What API you'll use for the graphics port?
>> Are you referring to the internal/external option? My understanding is
> that the internal is easier (less coding) so I will look at that.
Yeah, true, the internal it's relatively easy to do, but while the
external is of course still an option, we are simply not developing it
anymore, so probably it's in fact also your only option.
The hope is that new patches that come from Sun will still keep things
separated enough so that we don't end up in the same mess that we had
before starting the project, although we only "require" that the
internal code itself doesn't rely on a specific implementation of the
peers, which is in Sun's own interest anyway.
The external option was just a proof of concept, and it's really only
interesting for projects like Classpath and Harmony, but because
resources are limited, we are just "happy" with the current state of
things and hope it still works :)
What I was referring to is what is the API you choose for the backend,
for example, X11, GTK etc?
The X11 code should work well on the BSD, so you don't even need Cacio,
if you are doing an OSX port, you may give a look at the SDL backend, it
needs lots of love, but it should work out of the box without an X Server.
More information about the caciocavallo-dev