Development/Tutorials/Qt4 Ruby Tutorial/Chapter 01: Difference between revisions

From KDE TechBase
No edit summary
No edit summary
 
(17 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== Hello World! ==
<languages />
=== Overview ===


{{<translate><!--T:1-->
TutorialBrowser</translate>|
series=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial|<translate><!--T:2-->
Qt4 Ruby Tutorial</translate>]]|
name=<translate><!--T:3-->
Hello World!</translate>|
pre=<translate><!--T:4-->
[http://www.ruby-lang.org Ruby]</translate>|
next=[[Special:myLanguage/Development/Tutorials/Qt4_Ruby_Tutorial/Chapter_2|<translate><!--T:5-->
Tutorial 2 - Calling it Quits</translate>]]
}}
<translate>
== Hello World! == <!--T:6-->
</translate>
<translate>
<!--T:7-->
[[Image:Qt4_Ruby_Tutorial_Screenshot_1.png|center]]
</translate>
<translate>
<!--T:8-->
Files:
</translate>
* [http://www.darshancomputing.com/qt4-qtruby-tutorial/tutorial/t1/t1.rb t1.rb]
<translate>
=== Overview === <!--T:9-->
<!--T:10-->
This first program is a simple "Hello world" example.  
This first program is a simple "Hello world" example.  
It contains only the bare minimum you need to get a Qt application up and running.  
It contains only the bare minimum you need to get a Qt application up and running.  
The picture above is a screenshot of this program.
The picture above is a screenshot of this program.


<!--T:11-->
Here's the complete source code for the application:
Here's the complete source code for the application:
</translate>


<code ruby>
<syntaxhighlight lang="ruby">
require 'Qt4'
require 'Qt4'


app = Qt::Application.new(ARGV)
app = Qt::Application.new(ARGV)


hello = Qt::PushButton.new('Hello World!')
<translate><!--T:37-->
hello = Qt::PushButton.new('Hello World!')</translate>
hello.resize(100, 30)
hello.resize(100, 30)
hello.show()
hello.show()


app.exec()
app.exec()
</code>
</syntaxhighlight>


=== Intro ===
<translate>
=== Intro === <!--T:16-->


<!--T:17-->
The top level in a QtRuby application usually only needs to perform some kind of initialization and then pass control to the Qt library,
The top level in a QtRuby application usually only needs to perform some kind of initialization and then pass control to the Qt library,
which then tells the program about the user's actions via events.
which then tells the program about the user's actions via events.


There has to be exactly one [http://doc.trolltech.com/4.2/qapplication.html Qt::Application] object in every GUI application that uses Qt.  
<!--T:18-->
[http://doc.trolltech.com/4.2/qapplication.html Qt::Application] manages various application-wide resources, such as the default font and cursor.
There has to be exactly one [http://doc.qt.nokia.com/latest/qapplication.html Qt::Application] object in every GUI application that uses Qt.  
[http://doc.qt.nokia.com/latest/qapplication.html Qt::Application] manages various application-wide resources, such as the default font and cursor.


[http://doc.trolltech.com/4.2/qpushbutton.html Qt::PushButton] is a GUI push button that the user can press and release.  
<!--T:19-->
It manages its own look and feel, like every other [http://doc.trolltech.com/4.2/qwidget.html Qt::Widget].
[http://doc.qt.nokia.com/latest/qpushbutton.html Qt::PushButton] is a GUI push button that the user can press and release.  
It manages its own look and feel, like every other [http://doc.qt.nokia.com/latest/qwidget.html Qt::Widget].
A widget is a user interface object that can process user input and draw graphics.  
A widget is a user interface object that can process user input and draw graphics.  
The programmer can change both the overall look and feel and  
The programmer can change both the overall look and feel and  
many minor properties of it (such as color), as well as the widget's content.  
many minor properties of it (such as color), as well as the widget's content.  
A [http://doc.trolltech.com/4.2/qpushbutton.html Qt::PushButton] can show either text or a [http://doc.trolltech.com/4.2/qicon.html Qt::Icon].
A [http://doc.qt.nokia.com/latest/qpushbutton.html Qt::PushButton] can show either text or a [http://doc.qt.nokia.com/latest/qicon.html Qt::Icon].
</translate>


=== Line by Line Walkthrough ===
<translate>
=== Line by Line Walkthrough === <!--T:20-->
</translate>


<code ruby>
<syntaxhighlight lang="ruby">
require 'Qt4'
require 'Qt4'
</code>
</syntaxhighlight>


<translate>
<!--T:21-->
This line loads the QtRuby extension.
This line loads the QtRuby extension.
</translate>


<code ruby>
<syntaxhighlight lang="ruby">
app = Qt::Application.new(ARGV)
app = Qt::Application.new(ARGV)
</code>
</syntaxhighlight>


'''<tt>app</tt>''' is this program's [http://doc.trolltech.com/4.2/qapplication.html Qt::Application] instance. It is created here.  
<translate>
We pass '''<tt>ARGV</tt>''' to the [http://doc.trolltech.com/4.2/qapplication.html Qt::Application] constructor
<!--T:22-->
'''<tt>app</tt>''' is this program's [http://doc.qt.nokia.com/latest/qapplication.html Qt::Application] instance. It is created here.  
We pass '''<tt>ARGV</tt>''' to the [http://doc.qt.nokia.com/latest/qapplication.html Qt::Application] constructor
so that it can process certain standard command-line arguments (such as '''<tt>-display</tt>''' under X11).  
so that it can process certain standard command-line arguments (such as '''<tt>-display</tt>''' under X11).  
All command-line arguments recognized by Qt are removed from '''<tt>ARGV</tt>'''.  
All command-line arguments recognized by Qt are removed from '''<tt>ARGV</tt>'''.  


<strong>Note:</strong> It is essential that the [http://doc.trolltech.com/4.2/qapplication.html Qt::Application] object be created before any window-system parts of Qt are used.
<!--T:23-->
<strong>Note:</strong> It is essential that the [http://doc.qt.nokia.com/latest/qapplication.html Qt::Application] object be created before any window-system parts of Qt are used.
</translate>


<code ruby>
<syntaxhighlight lang="ruby">
<translate>
<!--T:24-->
hello = Qt::PushButton.new('Hello World!')
hello = Qt::PushButton.new('Hello World!')
</code>
</translate>
</syntaxhighlight>


Here, after the [http://doc.trolltech.com/4.2/qapplication.html Qt::Application], comes the first window-system code: A push button is created.
<translate>
<!--T:25-->
Here, after the [http://doc.qt.nokia.com/latest/qapplication.html Qt::Application], comes the first window-system code: A push button is created.


<!--T:26-->
The button is set up to display the text "Hello world!".  
The button is set up to display the text "Hello world!".  
Because we don't specify a parent window (as second argument to the  
Because we don't specify a parent window (as second argument to the  
[http://doc.trolltech.com/4.2/qpushbutton.html Qt::PushButton] constructor),  
[http://doc.qt.nokia.com/latest/qpushbutton.html Qt::PushButton] constructor),  
the button will be a window of its own, with its own window frame and title bar.
the button will be a window of its own, with its own window frame and title bar.
</translate>


<code ruby>
<syntaxhighlight lang="ruby">
hello.resize(100, 30)
hello.resize(100, 30)
</code>
</syntaxhighlight>


<translate>
<!--T:27-->
The button is set up to be 100 pixels wide and 30 pixels high  
The button is set up to be 100 pixels wide and 30 pixels high  
(excluding the window frame, which is provided by the windowing system).  
(excluding the window frame, which is provided by the windowing system).  
We could call [http://doc.trolltech.com/4.2/qwidget.html#pos-prop Qt::Widget::move()] to assign a specific screen position to the widget,  
We could call [http://doc.qt.nokia.com/latest/qwidget.html#pos-prop Qt::Widget::move()] to assign a specific screen position to the widget,  
but instead we let the windowing system choose a position.
but instead we let the windowing system choose a position.
</translate>


<code ruby>
<syntaxhighlight lang="ruby">
hello.show()
hello.show()
</code>
</syntaxhighlight>


A widget is never visible when you create it. You must call [http://doc.trolltech.com/4.2/qwidget.html#show Qt::Widget::show()] to make it visible.
<translate>
<!--T:28-->
A widget is never visible when you create it. You must call [http://doc.qt.nokia.com/latest/qwidget.html#show Qt::Widget::show()] to make it visible.
</translate>


<code ruby>
<syntaxhighlight lang="ruby">
app.exec()
app.exec()
</code>
</syntaxhighlight>


<translate>
<!--T:29-->
This is where our program passes control to Qt.  
This is where our program passes control to Qt.  
[http://doc.trolltech.com/4.2/qcoreapplication.html#exec Qt::CoreApplication::exec()] will return when the application exits.  
[http://doc.qt.nokia.com/latest/qcoreapplication.html#exec Qt::CoreApplication::exec()] will return when the application exits.  
([http://doc.trolltech.com/4.2/qcoreapplication.html Qt::CoreApplication] is [http://doc.trolltech.com/4.2/qapplication.html Qt::Application]'s base class.  
([http://doc.qt.nokia.com/latest/qcoreapplication.html Qt::CoreApplication] is [http://doc.qt.nokia.com/latest/qapplication.html Qt::Application]'s base class.  
It implements [http://doc.trolltech.com/4.2/qapplication.html Qt::Application]'s core, non-GUI functionality and can be used when developing non-GUI applications.)
It implements [http://doc.qt.nokia.com/latest/qapplication.html Qt::Application]'s core, non-GUI functionality and can be used when developing non-GUI applications.)


In [http://doc.trolltech.com/4.2/qcoreapplication.html#exec Qt::CoreApplication::exec()], Qt receives and processes user and system events and passes these on to the appropriate widgets.
<!--T:30-->
In [http://doc.qt.nokia.com/latest/qcoreapplication.html#exec Qt::CoreApplication::exec()], Qt receives and processes user and system events and passes these on to the appropriate widgets.


<!--T:31-->
You should now try to run this program.
You should now try to run this program.
</translate>


=== Running the Application ===
<translate>
=== Running the Application === <!--T:32-->


<!--T:33-->
When you run the application, you will see a small window filled with a single button, and on it you can read the famous words: "Hello world!"
When you run the application, you will see a small window filled with a single button, and on it you can read the famous words: "Hello world!"


=== Exercises ===
=== Exercises === <!--T:34-->


<!--T:35-->
Try to resize the window. Click the button. If you're running X11,  
Try to resize the window. Click the button. If you're running X11,  
try running the program with the '''<tt>-geometry</tt>''' option (for example, '''<tt>-geometry 100x200+10+20</tt>''').
try running the program with the '''<tt>-geometry</tt>''' option (for example, '''<tt>-geometry 100x200+10+20</tt>''').


Next: [[../Chapter_2|Calling it Quits]]
<!--T:36-->
[[Category:Ruby]]
</translate>

Latest revision as of 12:30, 13 July 2012

Other languages:
Hello World!
Tutorial Series   Qt4 Ruby Tutorial
Previous   Ruby
What's Next   Tutorial 2 - Calling it Quits
Further Reading   n/a

Hello World!

Files:

Overview

This first program is a simple "Hello world" example. It contains only the bare minimum you need to get a Qt application up and running. The picture above is a screenshot of this program.

Here's the complete source code for the application:

require 'Qt4'

app = Qt::Application.new(ARGV)

hello = Qt::PushButton.new('Hello World!')
hello.resize(100, 30)
hello.show()

app.exec()

Intro

The top level in a QtRuby application usually only needs to perform some kind of initialization and then pass control to the Qt library, which then tells the program about the user's actions via events.

There has to be exactly one Qt::Application object in every GUI application that uses Qt. Qt::Application manages various application-wide resources, such as the default font and cursor.

Qt::PushButton is a GUI push button that the user can press and release. It manages its own look and feel, like every other Qt::Widget. A widget is a user interface object that can process user input and draw graphics. The programmer can change both the overall look and feel and many minor properties of it (such as color), as well as the widget's content. A Qt::PushButton can show either text or a Qt::Icon.

Line by Line Walkthrough

require 'Qt4'

This line loads the QtRuby extension.

app = Qt::Application.new(ARGV)

app is this program's Qt::Application instance. It is created here. We pass ARGV to the Qt::Application constructor so that it can process certain standard command-line arguments (such as -display under X11). All command-line arguments recognized by Qt are removed from ARGV.

Note: It is essential that the Qt::Application object be created before any window-system parts of Qt are used.

hello = Qt::PushButton.new('Hello World!')

Here, after the Qt::Application, comes the first window-system code: A push button is created.

The button is set up to display the text "Hello world!". Because we don't specify a parent window (as second argument to the Qt::PushButton constructor), the button will be a window of its own, with its own window frame and title bar.

hello.resize(100, 30)

The button is set up to be 100 pixels wide and 30 pixels high (excluding the window frame, which is provided by the windowing system). We could call Qt::Widget::move() to assign a specific screen position to the widget, but instead we let the windowing system choose a position.

hello.show()

A widget is never visible when you create it. You must call Qt::Widget::show() to make it visible.

app.exec()

This is where our program passes control to Qt. Qt::CoreApplication::exec() will return when the application exits. (Qt::CoreApplication is Qt::Application's base class. It implements Qt::Application's core, non-GUI functionality and can be used when developing non-GUI applications.)

In Qt::CoreApplication::exec(), Qt receives and processes user and system events and passes these on to the appropriate widgets.

You should now try to run this program.

Running the Application

When you run the application, you will see a small window filled with a single button, and on it you can read the famous words: "Hello world!"

Exercises

Try to resize the window. Click the button. If you're running X11, try running the program with the -geometry option (for example, -geometry 100x200+10+20).