[cp-patches] X/Escher peers
roman at kennke.org
Thu Jun 29 09:35:58 UTC 2006
> Oh, and also, why can't we include the Escher source in external/? It
> sounds to me like it needs to be forked anyway (especially if it's
> going to get Xauthority handling, which it definitely needs). Is the
> author even working on it any more?
Escher is an external library, just like GTK or Qt. Only that it happens
to be programmed in Java. The original author isn't actively working on
it atm. BUT I do, and he made me co-maintainer of Escher. I already did
a couple of fixes to get the X peers working and will do a realease
I agree, having this in external/ would make things easier, but it seems
a cleaner approach to handle it like other libs that we depend on. What
do others think?
“Improvement makes straight roads, but the crooked roads, without
Improvement, are roads of Genius.” - William Blake
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://developer.classpath.org/pipermail/classpath-patches/attachments/20060629/32dd9b4b/attachment.pgp
More information about the Classpath-patches