Re: Has someone experimented with jedit?

[Mark Wielaard]

Hi,

On Wed, 2005-10-05 at 14:29 +0200, Roman Kennke wrote:
> We (especially Mark) usually test JEdit before making a release, but
> since this app is not usable at all with Classpath, it is not a
> showstopper. We focus on fixing Classpath with simpler apps first (like
> the TestRunner that David mentioned, or the BeanShell JConsole), this
> will also improve the complex application to a certain degree.

I always make sure jedit at least starts up when we are doing a new
release. And with each release it does become more and more usable. You
can now actually open a document, edit a bit, search and replace, etc.
But there are certainly still a lot of drawing/refresh bugs. Also the
embedded beanshell used to not work properly, but this might now be
fixed.

> Of course it would be nice if you could regularily test JEdit against
> GNU Classpath (keep in mind, you need a build with Java2D/Cairo enabled)
> and post results (and/or bugreports).

You need to compile classpath with the --enable-cairo-gtk option to
configure and run jedit with -Dgnu.java.awt.peer.gtk.Graphics=Graphics2D
defined.

Unfortunately GdkGraphics2D is broken in current CVS. With the patch of
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24099 you can get it to work
a bit again though.

Cheers,

Mark

signature.asc
Description: This is a digitally signed message part