return 0

First of all: this blog isn't dead! I just made a little vacation. :)
...and I'm back! with new experiences what I want to share with YOU.
Lets get start with my project YAMI. On the site http://yami.googlecode.com you can see that the latest change is from 2009.02.06. :S Yes I was to lazy to touch this code, but today I committed the latest revision r181 with some minimalistic changes like new code formatting rules and such as, and I also added the latest version of the JDBC connector's license. I'm still searching for contributors, please contact me if you have some experience in Java!
You can download the Nightly builds of YAMI - precompiled packages, just start them with:
java -jar yami_nightlyBuild.jar
(Nightly builds are unstable versions, use only for testing!)
The latest stable version is 0.1.3 download here: http://code.google.com/p/yami/downloads/list.
For the source code take a look to: http://code.google.com/p/yami/source/browse/#svn/trunk.

New topic.
Qt Jambi - i started to write a netlimiter-like application in Java using the Qt Jambi framework. I still agree that the framework is lightweight and looks pretty cool compared to the old Java metal style, but... deploying a pure Qt Jambi application is a nightmare.
Why? The documentation is still incomplete, they have no community site or forum (I've already mentioned this on qtlabs). The only thing what the Jambi community have is a mailing list, what is IMHO a bit uncomfortable. I want to finish this project (without Qt Jambi OFC) because there is no netlimiter-like application for Linux with graphical user interface - or at least I can't find any of them. :)
If somebody is interested in this project, please drop and e-mail or add a comment!

Ow, new theme ^^, cool isn't? ;)

Qt Jambi

Hi!
Maybe you've already heard about Qt ( Trolltech ) company. It is best known in the Linux community as the basis for the KDE desktop environment. They are developing a cross platform framework for C++ and Java (Qt Jambi). Today I tested their framework and compared it to Swing/AWT (Sun's framework).
The naming conventions are basically identical to Java, the most difference is that in Qt Jambi everything begins with Q (QTable, QPushButton), and not with J like in Swing (JTable, JButton). :)
The components are being created on the same way in booth frameworks.

Qt Jambi:

QTableWidget table = new QTableWidget(1000, 5);
QTableWidgetItem item = null;

Swing / AWT:

JTable table = new JTable(1000, 5);
Object data = null;

The concept for filling out tables is the same for booth TableModel and AbstractTableModel. Let's fill out these tables:


Qt Jambi:

for(int i = 0; i < 1000; i++) {
   for(int j = 0; j < 5; j++) {
      item = new QTableWidgetItem("Test value");
      table.setItem(i, j, item);
   }
}

Swing / AWT:

for(int i = 0; i < 1000; i++) {
   for(int j = 0; j < 5; j++) {
      data = "Test value";
      table.setValueAt(data, i, j);
   }
}

Qt table uses less memory with ~4MB, which is probably caused by the number of preloaded classes. I hope that Qt's Slot approach for generating events also takes less memory then the Swing listeners. That was for today. I'll come back with new test result as soon as I can.
Bye!