KDE AWT title text bug in sbb 1.1.6 v1-test

[clemens]

Hi all,

sbb jdk1.1.6v1 seems to have an awt bug when running KDE.

Frames have always the title text "AWTapp" visible.

Interestingly the same bug appeared in early 1.1.5
versions.

My system:
   Suse 5.1 (libc5)
   KDE Beta 4
   sbb JDK 1.1.6 v1-test source diffs + orig. Sun sources
   lesstif 0.84

I hope the problem lies not in compiling the jdk myself,
but everything else looks nice.

Cya,
   Clemens


P.S. Thanks again Steve for your great contribution.

--
/**
 * Test for jdk 1.1.5 (sbb) libc5 and KDE. Title of Frame is "AWTapp"
 * but it should be "Test". Does work with 1.1.5v5.
 * With sbb jdk 1.1.6v1-test it doesn't work again.
 */
public class FrameTitleTextTest {
   public static void main(String[] asArg_) {
  Frame pFrame = new Frame("Test");
  pFrame.addWindowListener(new WindowAdapter() {
 public void windowClosing(WindowEvent pWindowEvent_) {
System.exit(0);
 }
  });
  pFrame.setBounds(400, 400);
  pFrame.setVisible(true);
   }
}

Re: Classbrowser for Java & Emacs

[Chr. Clemens Lahme]

Hi Franz,

take a look at Jacob:

http://mats.gmd.de/clemens/jacob/

It might be exactly what you are looking for.

Cu,
   Clemens

> From: Franz Reitinger <[EMAIL PROTECTED]>
> Date: Wed, 3 Jun 1998 14:35:10 +0200
> 
> Developing Java-apps with Emacs is a fine thing. However  source files
> may increase and sooner or later you will loose the overall view.
> Therefore a thing like SNIFF in conjunction with Emacs or Emacs & a
> classbrowser would make java-developement  easier.
> Does somebody use such nice tools?
> 
> Tankx!

Re: Java Shell

[Chr. Clemens Lahme]

As much as I would love to have something like a java bash
(ok, call me a java junky), there is already something to avoid
continues jvm loading. It's called Echidna. You can find it at:

http://www.javagroup.org/echidna/

You can start different java applications in one jvm.
The author used it also in server mode to start javac
several times and saved some seconds compiling
his project. (ok, might be still slower than jikes,
but just as an example).

Bye,
   Clemens

Re: (long) finalizer() - potential bug

[Chr. Clemens Lahme]

As someone else mentioned the test code did work for me with jdk1.1.7 v1a
with java, but not with jre.
Just wanted to add, that,
when I added a System.exit( 0 ) call to main, jre does work for me.

Bye,
   Clemes

Changed test example:

public class  F
   {
  protected void finalize() throws Throwable
 {
System.out.println("finalize");
super.finalize();
 }
  public static void main(String[] args) throws Throwable
 {
F f = new F();
System.runFinalizersOnExit(true);
Runtime.getRuntime().runFinalizersOnExit(true);
f = null;
System.gc();
System.exit( 0 );
~
 }
   }

Re: Java IDE

[Chr. Clemens Lee]

Rachit Siamwalla wrote:
> 
> If you are used to emacs and are looking for something not much more
> than organization of files, build, syntax highlighting and step-through
> debugging / code browsing, JDE for Emacs works well. I use it all the
> time.
> 
> Thing I hate about most IDE's is that they try to incorporate thier own
> editing tool and none come near the power of vi or emacs.

The same applies to Jacob (http://www.kclee.com/clemens/jacob/).
Like JDE it is a Java class browser and project manager that uses Emacs.
One of the differences is that it is written in Java itself. 
You can also use both Jacob and JDE together.
For the Java purists, you can also combine Jacob with jEdit for editing.

   Clemens


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]