|Previous||Installation on Linux, Installation on Mac OS or Installation on Windows|
|Further Reading||Signals and Slots-Concept|
After all you should have a working ruby installation with KDE 4 bindings.
So lets try the a very minimalistic Qt 4 application to get a first impression. We don't start with KDE, because it would require some extra lines, that are not necessary when using Qt.
Open a shell and type in irb to start the interactive ruby shell. Now copy the short code example into the irb session.
a = Qt::Application.new ARGV
w = Qt::PushButton.new "Hello Ruby"
Qt::Object.connect( w, SIGNAL( :clicked ), a, SLOT( :quit ) )
Before you starting you start programming your Graphical User Interface (GUI), you have to <require the libraries, in this case Qt4, but korundum4 would also do the job, because the KDE libs automatically also requires the Qt libs for you.
In the second line we create a new Qt Object a of Qt::Application. Qt is the Ruby module (namespace) and Application the name of the class in the module. In C++, the native language of Qt, you would write QApplication. Remember this as you will need it, if you want to take a look in the Qt documentation.
Another object w of Qt::PushButton is created in the third line. "Hello Ruby" is the first (and only) argument of the Constructor. If you check the Qt documentation, you would find out, that this is the caption of the button. Ruby would also allow you to write it with brackets.
w = Qt::PushButton.new( "Hello Ruby" )
The small w means widget. All graphical elements in Qt are called widgets.
The fourth line is probably the most complicated one. The ruby class method connect of the object Object of the module Qt is used to bind the user action button-clicked with the action application-close. The signals and slots is a special concept of Qt. You can get a short overview and other ressources on Wikipedia.
The C++ equivalent you will find in the Qt documentation to :clicked would be "clicked()", a signal without an argument. In the case of no arguments you can always use a ruby symbol.
The fifth line let the created widget show. Don't forget this line. Maybe you want to think of a starting point of your application.
At last the application gets started by a.exec. Now the GUI takes over and manages the control flow. Any other command after this line will be applied after the GUI was closed.
class CustomApplication < Qt::Application
def doSomething puts "Do something else" Qt::Application.instance.quit end
a = CustomApplication.new ARGV w = Qt::PushButton.new( "Hello Ruby" ) Qt::Object.connect( w, SIGNAL( :clicked ), a, SLOT( :doSomething ) ) w.show a.exec
a = Qt::Application.new ARGV w = Qt::PushButton.new( "Hello Ruby" ) w.connect( SIGNAL :clicked ) do
puts "Do something else" Qt::Application.instance.quit
end w.show a.exec
a = Qt::Application.new ARGV w = Qt::PushButton.new( "Hello Ruby" ) do
connect( SIGNAL :clicked ) do puts "Do something else" Qt::Application.instance.quit end
end w.show a.exec