Need Java recommendation

Nitro.

The answer is Swing.

For what you are doing Java and Swing is the best choice. Used right JTable does not have any performance issues; glazedlist is something you can look into if you want a more advanced table ui.

For an example of a nice fast crossplatform Swing application:

http://www.jetbrains.com/idea/nextversion/free_java_ide.html

Which incidentally also is the best Java IDE around.

 

Thanks for all the replies. I will look for Swing tutorials online.

 

I have seen Jetbrains and before it, I thought there weren't any good IDEs for Java. I am not a fan of Eclipse.

 

No. IntelliJ is a very good IDE. Industry leading in many areas.

And if you use an open source tool chain - say apache ant (or maven) for building and subversion for version control - then this free edition completely covers what you need.

 

As I pointed out above, it's not the table or the grid, it's the cell renderer(s) that need to be optimized if the default one isn't quick enough. They are where all the work is done.

Though on a modern machine with a decent graphics card, out of the box may well work fast enough and it makes no sense doing anything else until some prototype benchmarks have been done.

In any case, is there any point in updating table cells a hundred times a second? Nobody can read that quickly. Some sort of throttling in line with system requirements may be the most sensible optimization at the end of the day.

 

Here is a somewhat old but do doubt still relevant article on optimizing JTable performance for "real time" apps:

http://java.sun.com/products/jfc/tsc/articles/ChristmasTree/

 

One other reminder for anybody new to Swing. Anything that causes Swing components to be (re)painted should be done from the AWT event thread. You may or may not have problems if you don't observe this discipline.

See SwingUtilities.InvokeLater () or SwingUtilities.InvokeAndWait ()

 

Check out Groovy and its SwingBuilder. You can cut the code of your GUIs down by 75% or more and supply the proper function pointers (better: closures!) and other dynamic deliciousness. Scala is also much better at GUIs that Java and also interoperates well.