<page xmlns="http://projectmallard.org/1.0/" xmlns:its="http://www.w3.org/2005/11/its" type="topic" id="image-viewer.cpp" xml:lang="de">

  <info>

    <link type="guide" xref="cpp#examples"/>

    <desc>A little bit more than a simple "Hello world" GTKmm application.</desc>

    <revision pkgversion="0.1" version="0.1" date="2011-03-18" status="review"/>

    <credit type="author">

      <name>GNOME-Dokumentationsprojekt</name>

      <email its:translate="no">gnome-doc-list@gnome.org</email>

    </credit>

    <credit type="author">

      <name>Johannes Schmid</name>

      <email its:translate="no">jhs@gnome.org</email>

    </credit>

    <credit type="editor">

      <name>Marta Maria Casetti</name>

      <email its:translate="no">mmcasetti@gmail.com</email>

      <years>2013</years>

    </credit>

    <mal:credit xmlns:mal="http://projectmallard.org/1.0/" type="translator copyright">

      <mal:name>Mario Blättermann</mal:name>

      <mal:email>mario.blaettermann@gmail.com</mal:email>

      <mal:years>2011, 2013</mal:years>

    </mal:credit>

  </info>

<title>Bildbetrachter</title>

<synopsis>

  
In diesem Tutorial lernen Sie, wie:

  <list>

    <item>
Some basic concepts of C++/GObject programming
</item>

    <item>
Schreiben einer Gtk-Anwendung in C++
</item>

  </list>

</synopsis>

<media type="image" mime="image/png" src="media/image-viewer.png"/>

<section id="anjuta">

  <title>Erstellen eines Projekts in Anjuta</title>

  
Before you start coding, you'll need to set up a new project in Anjuta. This will create all of the files you need to build and run the code later on. It's also useful for keeping everything together.

  <steps>

    <item>

    
Start Anjuta and click <guiseq><gui>File</gui><gui>New</gui><gui>Project</gui></guiseq> to open the project wizard.

    </item>

    <item>

    
Choose <gui>GTKmm (Simple)</gui> from the <gui>C++</gui> tab, click <gui>Forward</gui>, and fill out your details on the next few pages. Use <file>image-viewer</file> as project name and directory.

   	</item>

    <item>

    
Make sure that <gui>Use GtkBuilder for user interface</gui> is disabled as we will

    create the UI manually in this tutorial. Check the <link xref="guitar-tuner.cpp">Guitar-Tuner</link>

    tutorial if you want to learn how to use the interface builder.

    </item>

    <item>

    
Click <gui>Apply</gui> and the project will be created for you. Open <file>src/main.cc</file> from the <gui>Project</gui> or <gui>File</gui> tabs. You should see some code which starts with the lines:

#include <gtkmm.h>

#include <iostream>

#include "config.h">

    </item>

  </steps>

</section>

<section id="build">

  <title>Build the code for the first time</title>

  
This is a very basic C++ code setting up GTKmm. More details are given below; skip this list if you understand the basics:

  <list>

  <item>

    
The three #include lines at the top include the config (useful autoconf build defines), gtkmm (user interface) and iostream (C++-STL) libraries. Functions from these libraries are used in the rest of the code.

   </item>

   <item>

    
The main function creates a new (empty) window and sets the window title.

   </item>

   <item>

    
The kit::run() call starts the GTKmm main loop, which runs the user interface and starts listening for events (like clicks and key presses). As we give the window

    as an argument to that function, the application will automatically exit when

    that window is closed.

   </item>

  </list>

  
This code is ready to be used, so you can compile it by clicking <guiseq><gui>Build</gui><gui>Build Project</gui></guiseq> (or press <keyseq><key>Shift</key><key>F7</key></keyseq>).

  
Press <gui>Execute</gui> on the next window that appears to configure a debug build. You only need to do this once, for the first build.

</section>

<section id="ui">

<title>Erstellen der Benutzeroberfläche</title>

Now we will bring life into the empty window. GTKmm organizes the user interface

with Gtk::Containers that can contain other widgets and even other containers. Here we

will use the simplest available container, a Gtk::Box:

int

main (int argc, char *argv[])

{

	Gtk::Main kit(argc, argv);

	Gtk::Window main_win;

	main_win.set_title ("image-viewer-cpp");

	Gtk::Box* box = Gtk::manage(new Gtk::Box());

	box->set_orientation (Gtk::ORIENTATION_VERTICAL);

	box->set_spacing(6);

	main_win.add(*box);

	image = Gtk::manage(new Gtk::Image());

	box->pack_start (*image, true, true);

	Gtk::Button* button = Gtk::manage(new Gtk::Button("Open Image…"));

	button->signal_clicked().connect (

		sigc::ptr_fun(&on_open_image));

	box->pack_start (*button, false, false);

	main_win.show_all_children();

	kit.run(main_win);

	return 0;

}

  <steps>

    <item>

    
The first lines create the widgets we want to use: a button for opening up an image, the image view widget itself and the box we will use as a container. 

    </item>

    <item>

    
The calls to pack_start add the two widgets to the box and define their behaviour. The image will

    expand into any available space while the button will just be as big as needed. You will notice that we don't set

    explicit sizes on the widgets. In GTKmm this is usually not needed as it makes it much easier to have a layout that

    looks good in different window sizes. Next, the box is added to the window.

    </item>

    <item>

    
We need to define what happens when the user clicks on the button. GTKmm uses the concept of signals. When the button is clicked, it fires the clicked signal, which we can connect to some action. This is done using the signal_clicked().connect

    method which tells GTKmm to call the on_open_image function when the button is clicked. We will define the callback in the next section.

    </item>

    <item>

    
The last step is to show all widgets in the window using

    show_all_children(). This is equivalent to using the show()

    method on all our child widgets.

    </item>

  </steps>

</section>

<section id="show">

<title>Bildanzeige</title>

We will now define the signal handler for the clicked signal or the

button we mentioned before. Add this code before the main

method.

Gtk::Image* image = 0;

static void

on_open_image ()

{

	Gtk::FileChooserDialog dialog("Open image",

	                              Gtk::FILE_CHOOSER_ACTION_OPEN);

	dialog.add_button (Gtk::Stock::OPEN,

	                   Gtk::RESPONSE_ACCEPT);

	dialog.add_button (Gtk::Stock::CANCEL,

	                   Gtk::RESPONSE_CANCEL);

	Glib::RefPtr<Gtk::FileFilter> filter =

		Gtk::FileFilter::create();

	filter->add_pixbuf_formats();

	filter->set_name("Images");

	dialog.add_filter (filter);

	const int response = dialog.run();

	dialog.hide();

	switch (response)

	{

		case Gtk::RESPONSE_ACCEPT:

			image->set(dialog.get_filename());

			break;

		default:

			break;

	}

}

  
This is a bit more complicated than anything we've attempted so far, so let's break it down:

  <list>

      <item>

      
The dialog for choosing the file is created using the

      Gtk::FileChooserDialog constructor. This takes the title and type of the dialog. In our case, it is an Open dialog.

    </item>

    <item>

    
The next two lines add an Open and a Close button to the dialog.

    
Notice that we are using stock button names from Gtk, instead of manually typing "Cancel" or "Open". The advantage of using stock names is that the button labels will already be translated into the user's language.

    
The second argument to the add_button() method is a value to identify

    the clicked button. We use predefined values provided by GTKmm here, too.

    </item>

    <item>

    
The next two lines restrict the <gui>Open</gui> dialog to only display files which can be opened by Gtk::Image. A filter object is created first; we then add all kinds of files supported by Gdk::Pixbuf (which includes most image formats like PNG and JPEG) to the filter. Finally, we set this filter to be the <gui>Open</gui> dialog's filter.

    
Glib::RefPtr is a smart pointer used here, that makes sure that the filter is

    destroyed when there is no reference to it anymore.

    </item>

    <item>

    
dialog.run displays the <gui>Open</gui> dialog. The dialog will wait for the user to choose an image; when they do, dialog.run will return the value Gtk::RESPONSE_ACCEPT (it would return Gtk::RESPONSE_CANCEL if the user clicked <gui>Cancel</gui>). The switch statement tests for this.

    </item>

    <item>

    
We hide the <gui>Open</gui> dialog because we don't need it any more. The dialog would be hidden later anyway, as it is only a local variable and is

    destroyed (and therefore hidden) when the scope ends.

    </item>

    <item>
Assuming that the user did click <gui>Open</gui>, the next line loads the

    file into the Gtk::Image so that it is displayed.

    </item>

  </list>

</section>

<section id="build2">

  <title>Build and run the application</title>

  
All of the code should now be ready to go. Click <guiseq><gui>Build</gui><gui>Build Project</gui></guiseq> to build everything again, and then <guiseq><gui>Run</gui><gui>Execute</gui></guiseq> to start the application.

  
If you haven't already done so, choose the <file>Debug/src/image-viewer</file> application in the dialog that appears. Finally, hit <gui>Run</gui> and enjoy!

</section>

<section id="impl">

 <title>Referenz-Implementierung</title>

 
If you run into problems with the tutorial, compare your code with this <link href="image-viewer/image-viewer.cc">reference code</link>.

</section>

<section id="next">

  <title>Nächste Schritte</title>

  
Here are some ideas for how you can extend this simple demonstration:

  <list>

   <item>

   
Have the user select a directory rather than a file, and provide controls to cycle through all of the images in a directory.

   </item>

   <item>

   
Apply random filters and effects to the image when it is loaded and allow the user to save the modified image.

   
<link href="http://www.gegl.org/api.html">GEGL</link> provides powerful image manipulation capabilities.

   </item>

   <item>

   
Allow the user to load images from network shares, scanners, and other more complicated sources.

   
You can use <link href="http://library.gnome.org/devel/gio/unstable/">GIO</link> to handle network file transfers and the like, and <link href="http://library.gnome.org/devel/gnome-scan/unstable/">GNOME Scan</link> to handle scanning.

   </item>

  </list>

</section>

</page>