<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<!-- /home/gvatteka/dev/qt-4.3/doc/src/paintsystem.qdoc -->
<head>
<title>The Paint System</title>
<link href="classic.css" rel="stylesheet" type="text/css" />
</head>
<body>
<h1 align="center">The Paint System<br /><small></small></h1>
<p>Qt's paint system enables painting on screen and print devices using the same API, and is primarily based on the <a href="gui/QPainter.html"><tt>QPainter</tt></a>, <a href="gui/QPaintDevice.html"><tt>QPaintDevice</tt></a>, and <a href="gui/QPaintEngine.html"><tt>QPaintEngine</tt></a> classes.</p>
<p><a href="gui/QPainter.html"><tt>QPainter</tt></a> is used to perform drawing operations, <a href="gui/QPaintDevice.html"><tt>QPaintDevice</tt></a> is an abstraction of a two-dimensional space that can be painted on using a <a href="gui/QPainter.html"><tt>QPainter</tt></a>, and <a href="gui/QPaintEngine.html"><tt>QPaintEngine</tt></a> provides the interface that the painter uses to draw onto different types of devices. The <a href="gui/QPaintEngine.html"><tt>QPaintEngine</tt></a> class is used internally by <a href="gui/QPainter.html"><tt>QPainter</tt></a> and <a href="gui/QPaintDevice.html"><tt>QPaintDevice</tt></a>, and is hidden from application programmers unless they create their own device type.</p>
<p align="center"><img src="images/paintsystem-core.png" /></p><p>The main benefit of this approach is that all painting follows the same painting pipeline making it easy to add support for new features and providing default implementations for unsupported ones.</p>
<p>Alternatively, Qt provides the QtOpenGL module, offering classes that makes it easy to use OpenGL in Qt applications. Among others, the module provides an OpenGL widget class that can be used just like any other Qt widget, except that it opens an OpenGL display buffer where the OpenGL API can be used to render the contents.</p>
<ul><li><a href="#drawing">Drawing</a></li>
<li><a href="#filling">Filling</a></li>
<li><a href="#creating-a-paint-device">Creating a Paint Device</a></li>
<li><a href="#reading-and-writing-image-files">Reading and Writing Image Files</a></li>
<li><a href="#styling">Styling</a></li>
</ul>
<a name="drawing"></a>
<h2>Drawing</h2>
<p><a href="gui/QPainter.html"><tt>QPainter</tt></a> provides highly optimized functions to do most of the drawing GUI programs require. It can draw everything from simple graphical primitives (represented by the <a href="core/QPoint.html"><tt>QPoint</tt></a>, <a href="gui/QLine.html"><tt>QLine</tt></a>, <a href="core/QRect.html"><tt>QRect</tt></a>, <a href="gui/QRegion.html"><tt>QRegion</tt></a> and <a href="gui/QPolygon.html"><tt>QPolygon</tt></a> classes) to complex shapes like vector paths. In Qt vector paths are represented by the <a href="gui/QPainterPath.html"><tt>QPainterPath</tt></a> class. <a href="gui/QPainterPath.html"><tt>QPainterPath</tt></a> provides a container for painting operations, enabling graphical shapes to be constructed and reused.</p>
<p><table width="100%" align="center" cellpadding="2" cellspacing="1" border="0">
<tr valign="top" class="odd"><td><p align="center"><img src="images/paintsystem-painterpath.png" /></p></td><td><b>QPainterPath</b><p>A painter path is an object composed of lines and curves. For example, a rectangle is composed by lines and an ellipse is composed by curves.</p>
<p>The main advantage of painter paths over normal drawing operations is that complex shapes only need to be created once; then they can be drawn many times using only calls to the QPainter::drawPath() function.</p>
<p>A <a href="gui/QPainterPath.html"><tt>QPainterPath</tt></a> object can be used for filling, outlining, and clipping. To generate fillable outlines for a given painter path, use the <a href="gui/QPainterPathStroker.html"><tt>QPainterPathStroker</tt></a> class.</p>
</td></tr>
</table></p>
<p>Lines and outlines are drawn using the <a href="gui/QPen.html"><tt>QPen</tt></a> class. A pen is defined by its style (i.e. its line-type), width, brush, how the endpoints are drawn (cap-style) and how joins between two connected lines are drawn (join-style). The pen's brush is a <a href="gui/QBrush.html"><tt>QBrush</tt></a> object used to fill strokes generated with the pen, i.e. the <a href="gui/QBrush.html"><tt>QBrush</tt></a> class defines the fill pattern.</p>
<p><a href="gui/QPainter.html"><tt>QPainter</tt></a> can also draw aligned text and pixmaps.</p>
<p>When drawing text, the font is specified using the <a href="gui/QFont.html"><tt>QFont</tt></a> class. Qt will use the font with the specified attributes, or if no matching font exists, Qt will use the closest matching installed font. The attributes of the font that is actually used can be retrieved using the <a href="gui/QFontInfo.html"><tt>QFontInfo</tt></a> class. In addition, the <a href="gui/QFontMetrics.html"><tt>QFontMetrics</tt></a> class provides the font measurements, and the <a href="gui/QFontDatabase.html"><tt>QFontDatabase</tt></a> class provides information about the fonts available in the underlying window system.</p>
<p>Normally, <a href="gui/QPainter.html"><tt>QPainter</tt></a> draws in a "natural" coordinate system, but it is able to perform view and world transformations using the <a href="gui/QMatrix.html"><tt>QMatrix</tt></a> class. For more information, see <a href="coordsys.html">The Coordinate System</tt></a> documentation which also describes the rendering process, i.e. the relation between the logical representation and the rendered pixels, and the benefits of anti-aliased painting.</p>
<p><table width="100%" align="center" cellpadding="2" cellspacing="1" border="0">
<tr valign="top" class="odd"><td><b>Anti-Aliased Painting</b><p>When drawing, the pixel rendering is controlled by the QPainter::Antialiasing render hint. The QPainter::RenderHint enum is used to specify flags to <a href="gui/QPainter.html"><tt>QPainter</tt></a> that may or may not be respected by any given engine.</p>
<p>The QPainter::Antialiasing value indicates that the engine should antialias edges of primitives if possible, i.e. smoothing the edges by using different color intensities.</p>
</td><td><p align="center"><img src="images/paintsystem-antialiasing.png" /></p></td></tr>
</table></p>
<a name="filling"></a>
<h2>Filling</h2>
<p>Shapes are filled using the <a href="gui/QBrush.html"><tt>QBrush</tt></a> class. A brush is defined by its color and its style (i.e. its fill pattern).</p>
<p>Any color in Qt is represented by the <a href="gui/QColor.html"><tt>QColor</tt></a> class which supports the RGB, HSV and CMYK color models. <a href="gui/QColor.html"><tt>QColor</tt></a> also support alpha-blended outlining and filling (specifying the transparency effect), and the class is platform and device independent (the colors are mapped to hardware using the <a href="gui/QColormap.html"><tt>QColormap</tt></a> class). For more information, see the <a href="gui/QColor.html"><tt>QColor</tt></a> class documentation.</p>
<p>When creating a new widget, it is recommend to use the colors in the widget's palette rather than hard-coding specific colors. All widgets in Qt contain a palette and use their palette to draw themselves. A widget's palette is represented by the <a href="gui/QPalette.html"><tt>QPalette</tt></a> class which contains color groups for each widget state.</p>
<p>The available fill patterns are described by the Qt::BrushStyle enum. These include basic patterns spanning from uniform color to very sparse pattern, various line combinations, gradient fills and textures. Qt provides the <a href="gui/QGradient.html"><tt>QGradient</tt></a> class to define custom gradient fills, while texture patterns are specified using the <a href="gui/QPixmap.html"><tt>QPixmap</tt></a> class.</p>
<p><table width="100%" align="center" cellpadding="2" cellspacing="1" border="0">
<tr valign="top" class="odd"><td><p align="center"><img src="images/paintsystem-fancygradient.png" /></p></td><td><b>QGradient</b><p>The <a href="gui/QGradient.html"><tt>QGradient</tt></a> class is used in combination with <a href="gui/QBrush.html"><tt>QBrush</tt></a> to specify gradient fills.</p>
<p align="center"><img src="images/paintsystem-gradients.png" /></p><p>Qt currently supports three types of gradient fills: Linear gradients interpolate colors between start and end points, radial gradients interpolate colors between a focal point and end points on a circle surrounding it, and conical gradients interpolate colors around a center point.</p>
</td></tr>
</table></p>
<a name="creating-a-paint-device"></a>
<h2>Creating a Paint Device</h2>
<p>The <a href="gui/QPaintDevice.html"><tt>QPaintDevice</tt></a> class is the base class of objects that can be painted, i.e. <a href="gui/QPainter.html"><tt>QPainter</tt></a> can draw on any <a href="gui/QPaintDevice.html"><tt>QPaintDevice</tt></a> subclass. <a href="gui/QPaintDevice.html"><tt>QPaintDevice</tt></a>'s drawing capabilities are currently implemented by the <a href="gui/QWidget.html"><tt>QWidget</tt></a>, <a href="gui/QImage.html"><tt>QImage</tt></a>, <a href="gui/QPixmap.html"><tt>QPixmap</tt></a>, <a href="opengl/QGLWidget.html"><tt>QGLWidget</tt></a>, <a href="opengl/QGLPixelBuffer.html"><tt>QGLPixelBuffer</tt></a>, <a href="gui/QPicture.html"><tt>QPicture</tt></a> and <a href="gui/QPrinter.html"><tt>QPrinter</tt></a> subclasses.</p>
<p align="center"><img src="images/paintsystem-devices.png" /></p><p><table width="100%" align="center" cellpadding="2" cellspacing="1" border="0">
<tr valign="top" class="odd"><td><b>Custom Backends</b><p>Support for a new backend can be implemented by deriving from the <a href="gui/QPaintDevice.html"><tt>QPaintDevice</tt></a> class and reimplementing the virtual QPaintDevice::paintEngine() function to tell <a href="gui/QPainter.html"><tt>QPainter</tt></a> which paint engine should be used to draw on this particular device. To actually be able to draw on the device, this paint engine must be a custom paint engine created by deriving from the <a href="gui/QPaintEngine.html"><tt>QPaintEngine</tt></a> class.</p>
</td></tr>
</table></p>
<a name="widget"></a>
<h3>Widget</h3>
<p>The <a href="gui/QWidget.html"><tt>QWidget</tt></a> class is the base class of all user interface objects. The widget is the atom of the user interface: it receives mouse, keyboard and other events from the window system, and paints a representation of itself on the screen.</p>
<a name="image"></a>
<h3>Image</h3>
<p>The <a href="gui/QImage.html"><tt>QImage</tt></a> class provides a hardware-independent image representation which is designed and optimized for I/O, and for direct pixel access and manipulation. <a href="gui/QImage.html"><tt>QImage</tt></a> supports several image formats including monochrome, 8-bit, 32-bit and alpha-blended images.</p>
<p>One advantage of using <a href="gui/QImage.html"><tt>QImage</tt></a> as a paint device is that it is possible to guarantee the pixel exactness of any drawing operation in a platform-independent way. Another benefit is that the painting can be performed in another thread than the current GUI thread.</p>
<a name="pixmap"></a>
<h3>Pixmap</h3>
<p>The <a href="gui/QPixmap.html"><tt>QPixmap</tt></a> class is an off-screen image representation which is designed and optimized for showing images on screen. Unlike <a href="gui/QImage.html"><tt>QImage</tt></a>, the pixel data in a pixmap is internal and is managed by the underlying window system, i.e. pixels can only be accessed through <a href="gui/QPainter.html"><tt>QPainter</tt></a> functions or by converting the <a href="gui/QPixmap.html"><tt>QPixmap</tt></a> to a <a href="gui/QImage.html"><tt>QImage</tt></a>.</p>
<p>To optimize drawing with <a href="gui/QPixmap.html"><tt>QPixmap</tt></a>, Qt provides the <a href="gui/QPixmapCache.html"><tt>QPixmapCache</tt></a> class which can be used to store temporary pixmaps that are expensive to generate without using more storage space than the cache limit.</p>
<p>Qt also provides the <a href="gui/QBitmap.html"><tt>QBitmap</tt></a> convenience class, inheriting <a href="gui/QPixmap.html"><tt>QPixmap</tt></a>. <a href="gui/QBitmap.html"><tt>QBitmap</tt></a> guarantees monochrome (1-bit depth) pixmaps, and is mainly used for creating custom <a href="gui/QCursor.html"><tt>QCursor</tt></a> and <a href="gui/QBrush.html"><tt>QBrush</tt></a> objects, constructing <a href="gui/QRegion.html"><tt>QRegion</tt></a> objects, and for setting masks for pixmaps and widgets.</p>
<a name="opengl-widget"></a>
<h3>OpenGL Widget</h3>
<p>As mentioned above, Qt provides the QtOpenGL module offering classes that makes it easy to use OpenGL in Qt applications. For example, the <a href="opengl/QGLWidget.html"><tt>QGLWidget</tt></a> enables the OpenGL API for rendering.</p>
<p>But <a href="opengl/QGLWidget.html"><tt>QGLWidget</tt></a> is also a <a href="gui/QWidget.html"><tt>QWidget</tt></a> subclass, and can be used by <a href="gui/QPainter.html"><tt>QPainter</tt></a> as any other paint device. One huge benefit from this is that it enables Qt to utilize the high performance of OpenGL for most drawing operations, such as transformations and pixmap drawing.</p>
<a name="pixel-buffer"></a>
<h3>Pixel Buffer</h3>
<p>The QtOpenGL module also provides the <a href="opengl/QGLPixelBuffer.html"><tt>QGLPixelBuffer</tt></a> class which inherits <a href="gui/QPaintDevice.html"><tt>QPaintDevice</tt></a> directly.</p>
<p><a href="opengl/QGLPixelBuffer.html"><tt>QGLPixelBuffer</tt></a> encapsulates an OpenGL pbuffer. Rendering into a pbuffer is normally done using full hardware acceleration which can be significantly faster than rendering into a <a href="gui/QPixmap.html"><tt>QPixmap</tt></a>.</p>
<a name="framebuffer-object"></a>
<h3>Framebuffer Object</h3>
<p>The QtOpenGL module also provides the <a href="opengl/QGLFramebufferObject.html"><tt>QGLFramebufferObject</tt></a> class which inherits <a href="gui/QPaintDevice.html"><tt>QPaintDevice</tt></a> directly.</p>
<p><a href="opengl/QGLFramebufferObject.html"><tt>QGLFramebufferObject</tt></a> encapsulates an OpenGL framebuffer object. Framebuffer objects can also be used for off-screen rendering, and offer several advantages over pixel buffers for this purpose. These are described in the <a href="opengl/QGLFramebufferObject.html"><tt>QGLFramebufferObject</tt></a> class documentation.</p>
<a name="picture"></a>
<h3>Picture</h3>
<p>The <a href="gui/QPicture.html"><tt>QPicture</tt></a> class is a paint device that records and replays <a href="gui/QPainter.html"><tt>QPainter</tt></a> commands. A picture serializes painter commands to an IO device in a platform-independent format. <a href="gui/QPicture.html"><tt>QPicture</tt></a> is also resolution independent, i.e. a <a href="gui/QPicture.html"><tt>QPicture</tt></a> can be displayed on different devices (for example svg, pdf, ps, printer and screen) looking the same.</p>
<p>Qt provides the QPicture::load() and QPicture::save() functions for loading and saving pictures. But in addition the <a href="gui/QPictureIO.html"><tt>QPictureIO</tt></a> class is provided to enable the programmer to install new picture file formats in addition to those that Qt provides.</p>
<a name="printer"></a>
<h3>Printer</h3>
<p>The <a href="gui/QPrinter.html"><tt>QPrinter</tt></a> class is a paint device that paints on a printer. On Windows or Mac OS X, <a href="gui/QPrinter.html"><tt>QPrinter</tt></a> uses the built-in printer drivers. On X11, <a href="gui/QPrinter.html"><tt>QPrinter</tt></a> generates postscript and sends that to lpr, lp, or another print program. <a href="gui/QPrinter.html"><tt>QPrinter</tt></a> can also print to any other <a href="gui/QPrintEngine.html"><tt>QPrintEngine</tt></a> object.</p>
<p>The <a href="gui/QPrintEngine.html"><tt>QPrintEngine</tt></a> class defines an interface for how <a href="gui/QPrinter.html"><tt>QPrinter</tt></a> interacts with a given printing subsystem. The common case when creating your own print engine, is to derive from both <a href="gui/QPaintEngine.html"><tt>QPaintEngine</tt></a> and <a href="gui/QPrintEngine.html"><tt>QPrintEngine</tt></a>.</p>
<p>The output format is by default determined by the platform the printer is running on, but by explicitly setting the output format to QPrinter::PdfFormat, <a href="gui/QPrinter.html"><tt>QPrinter</tt></a> will generate its output as a PDF file.</p>
<a name="reading-and-writing-image-files"></a>
<h2>Reading and Writing Image Files</h2>
<p>The most common way to read images is through <a href="gui/QImage.html"><tt>QImage</tt></a> and <a href="gui/QPixmap.html"><tt>QPixmap</tt></a>'s constructors, or by calling the QImage::load() and QPixmap::load() functions. In addition, Qt provides the <a href="gui/QImageReader.html"><tt>QImageReader</tt></a> class which gives more control over the process. Depending on the underlying support in the image format, the functions provided by the class can save memory and speed up loading of images.</p>
<p>Likewise, Qt provides the <a href="gui/QImageWriter.html"><tt>QImageWriter</tt></a> class which supports setting format specific options, such as the gamma level, compression level and quality, prior to storing the image. If you do not need such options, you can use QImage::save() or QPixmap::save() instead.</p>
<p><table width="100%" align="center" cellpadding="2" cellspacing="1" border="0">
<tr valign="top" class="odd"><td><b>QMovie</b><p><a href="gui/QMovie.html"><tt>QMovie</tt></a> is a convenience class for displaying animations, using the <a href="gui/QImageReader.html"><tt>QImageReader</tt></a> class internally. Once created, the <a href="gui/QMovie.html"><tt>QMovie</tt></a> class provides various functions for both running and controlling the given animation.</p>
</td><td><p align="center"><img src="images/paintsystem-movie.png" /></p></td></tr>
</table></p>
<p>The <a href="gui/QImageReader.html"><tt>QImageReader</tt></a> and <a href="gui/QImageWriter.html"><tt>QImageWriter</tt></a> classes rely on the <a href="gui/QImageIOHandler.html"><tt>QImageIOHandler</tt></a> class which is the common image I/O interface for all image formats in Qt. <a href="gui/QImageIOHandler.html"><tt>QImageIOHandler</tt></a> objects are used internally by <a href="gui/QImageReader.html"><tt>QImageReader</tt></a> and <a href="gui/QImageWriter.html"><tt>QImageWriter</tt></a> to add support for different image formats to Qt.</p>
<p>A list of the supported file formats are available through the QImageReader::supportedImageFormats() and QImageWriter::supportedImageFormats() functions. Qt supports several file formats by default, and in addition new formats can be added as plugins. The currently supported formats are listed in the <a href="gui/QImageReader.html"><tt>QImageReader</tt></a> and <a href="gui/QImageWriter.html"><tt>QImageWriter</tt></a> class documentation.</p>
<p>Qt's plugin mechanism can also be used to write a custom image format handler. This is done by deriving from the <a href="gui/QImageIOHandler.html"><tt>QImageIOHandler</tt></a> class, and creating a QImageIOPlugin object which is a factory for creating <a href="gui/QImageIOHandler.html"><tt>QImageIOHandler</tt></a> objects. When the plugin is installed, <a href="gui/QImageReader.html"><tt>QImageReader</tt></a> and <a href="gui/QImageWriter.html"><tt>QImageWriter</tt></a> will automatically load the plugin and start using it.</p>
<p><table width="100%" align="center" cellpadding="2" cellspacing="1" border="0">
<tr valign="top" class="odd"><td><p align="center"><img src="images/paintsystem-svg.png" /></p></td><td><b>SVG Rendering</b><p>Scalable Vector Graphics (SVG) is an language for describing both static and animated two-dimensional vector graphics. Qt includes support for the static features of SVG 1.2 Tiny.</p>
<p>SVG drawings can be rendered onto any <a href="gui/QPaintDevice.html"><tt>QPaintDevice</tt></a> subclass. This approach gives developers the flexibility to experiment, in order to find the best solution for each application.</p>
<p>The easiest way to render SVG files is to construct a <a href="svg/QSvgWidget.html"><tt>QSvgWidget</tt></a> and load an SVG file using one of the QSvgWidget::load() functions. The rendering is performed by the <a href="svg/QSvgRenderer.html"><tt>QSvgRenderer</tt></a> class which also can be used directly to provide SVG support for custom widgets.</p>
<p>For more information, see the QtSvg module documentation.</p>
</td></tr>
</table></p>
<a name="styling"></a>
<h2>Styling</h2>
<p>Qt's built-in widgets use the <a href="gui/QStyle.html"><tt>QStyle</tt></a> class to perform nearly all of their drawing. <a href="gui/QStyle.html"><tt>QStyle</tt></a> is an abstract base class that encapsulates the look and feel of a GUI, and can be used to make the widgets look exactly like the equivalent native widgets or to give the widgets a custom look.</p>
<p>Qt provides a set of <a href="gui/QStyle.html"><tt>QStyle</tt></a> subclasses that emulate the native look of the different platforms supported by Qt (<a href="gui/QWindowsStyle.html"><tt>QWindowsStyle</tt></a>, QMacStyle, <a href="gui/QMotifStyle.html"><tt>QMotifStyle</tt></a>, etc.). These styles are built into the QtGui library, other styles can be made available using Qt's plugin mechansim.</p>
<p>Most functions for drawing style elements take four arguments:</p>
<ul>
<li>an enum value specifying which graphical element to draw</li>
<li>a <a href="gui/QStyleOption.html"><tt>QStyleOption</tt></a> object specifying how and where to render that element</li>
<li>a <a href="gui/QPainter.html"><tt>QPainter</tt></a> object that should be used to draw the element</li>
<li>a <a href="gui/QWidget.html"><tt>QWidget</tt></a> object on which the drawing is performed (optional)</li>
</ul>
<p>The style gets all the information it needs to render the graphical element from the <a href="gui/QStyleOption.html"><tt>QStyleOption</tt></a> class. The widget is passed as the last argument in case the style needs it to perform special effects (such as animated default buttons on Mac OS X), but it isn't mandatory. In fact, <a href="gui/QStyle.html"><tt>QStyle</tt></a> can be used to draw on any paint device (not just widgets), in which case the widget argument is a zero pointer.</p>
<p align="center"><img src="images/paintsystem-stylepainter.png" /></p><p>The paint system also provides the <a href="gui/QStylePainter.html"><tt>QStylePainter</tt></a> class inheriting from <a href="gui/QPainter.html"><tt>QPainter</tt></a>. <a href="gui/QStylePainter.html"><tt>QStylePainter</tt></a> is a convenience class for drawing <a href="gui/QStyle.html"><tt>QStyle</tt></a> elements inside a widget, and extends <a href="gui/QPainter.html"><tt>QPainter</tt></a> with a set of high-level drawing functions implemented on top of <a href="gui/QStyle.html"><tt>QStyle</tt></a>'s API. The advantage of using <a href="gui/QStylePainter.html"><tt>QStylePainter</tt></a> is that the parameter lists get considerably shorter.</p>
<p><table width="100%" align="center" cellpadding="2" cellspacing="1" border="0">
<tr valign="top" class="odd"><td><img src="images/paintsystem-icon.png" /></td><td><b>QIcon</b><p>The <a href="gui/QIcon.html"><tt>QIcon</tt></a> class provides scalable icons in different modes and states.</p>
<p><a href="gui/QIcon.html"><tt>QIcon</tt></a> can generate pixmaps reflecting an icon's state, mode and size. These pixmaps are generated from the set of pixmaps made available to the icon, and are used by Qt widgets to show an icon representing a particular action.</p>
<p>The rendering of a <a href="gui/QIcon.html"><tt>QIcon</tt></a> object is handled by the <a href="gui/QIconEngine.html"><tt>QIconEngine</tt></a> class. Each icon has a corresponding icon engine that is responsible for drawing the icon with a requested size, mode and state.</p>
</td></tr>
</table></p>
<p /><address><hr /><div align="center">
<table width="100%" cellspacing="0" border="0"><tr class="address">
<td width="30%">Copyright © 2007 <a href="trolltech.html">Trolltech</a></td>
<td width="40%" align="center"><a href="trademarks.html">Trademarks</a></td>
<td width="30%" align="right"><div align="right">Qt Jambi </div></td>
</tr></table></div></address></body>
</html>
