Sophie

Sophie

distrib > Fedora > 18 > i386 > by-pkgid > 5ab010e37991249ab4adaa24d6e39c6e > files > 223

qt5-qtdoc-5.1.1-2.fc18.noarch.rpm

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en_US" lang="en_US">
<head>
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- core.qdoc -->
  <title>Core Internals | QtDoc 5.1</title>
  <link rel="stylesheet" type="text/css" href="style/offline.css" />
</head>
<body>
<div class="header" id="qtdocheader"></div>
<div class="content">
<div class="line">
<div class="content mainContent">
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#objects-properties-and-events">Objects, Properties, and Events</a></li>
<li class="level1"><a href="#container-classes">Container Classes</a></li>
<li class="level1"><a href="#internationalization">Internationalization</a></li>
<li class="level1"><a href="#inter-process-communication">Inter-Process Communication</a></li>
<li class="level1"><a href="#threading">Threading</a></li>
<li class="level1"><a href="#platform-support">Platform Support</a></li>
</ul>
</div>
<h1 class="title">Core Internals</h1>
<span class="subtitle"></span>
<!-- $$$topics-core.html-description -->
<div class="descr"> <a name="details"></a>
<p>Qt contains a rich set of fundamental enablers, mainly from the <a href="whatsnew51.html#qt-core">Qt Core</a> module. Qt uses these enablers to provide higher-level UI and application development components. The following topics explain the most important enablers and show how to use them to implement specialized functionality not already provided by Qt.</p>
<a name="objects-properties-and-events"></a>
<h2>Objects, Properties, and Events</h2>
<p>The QObject class forms the foundation of Qt's object model and is the parent class of many Qt classes. The object model introduces many mechanisms such as a meta-object system which allows run-time introspection, manipulation, and invocation of properties and methods in the object. It also serves as the basis for Qt's event system, which is a low-level way of communicating between QObject-based objects. Another high-level form of communication is provided in Qt's Signals &amp; Slots mechanism. These features can also be used in combination with The State Machine Framework which provides a formally defined and predictable way of managing the states of your application.</p>
<a name="container-classes"></a>
<h2>Container Classes</h2>
<p>A <i>container</i> is a data structure whose instances are collections of other objects. Some examples of containers are: dynamic arrays, queues, linked lists, and associative arrays. Qt provides a set of general purpose, template-based container classes for structuring data in memory. See the full list of <a href="#container-classes">Container Classes</a> for more details.</p>
<a name="internationalization"></a>
<h2>Internationalization</h2>
<p>Qt uses <a href="unicode.html">Unicode</a> for the encoding of displayable text strings. Unicode provides support for all commonly used writing systems in the world and is ideal for cross-platform development. Applications can also be written to support any number of different languages with one code base using Qt's powerful <a href="internationalization.html">internationalization system</a>.</p>
<a name="inter-process-communication"></a>
<h2>Inter-Process Communication</h2>
<p>Qt provides several classes to support <a href="ipc.html">communication between processes</a>. You can also launch and manage external processes using the <a href="ipc.html#qprocess">QProcess</a> class.</p>
<a name="threading"></a>
<h2>Threading</h2>
<p>Qt supports primitives and convenience functionality to manage threads and parallelized code in a safe and platform-independent way.</p>
<a name="platform-support"></a>
<h2>Platform Support</h2>
<p>Qt allows you to write platform-independent code, where the same code base can be compiled for and deployed on different platforms without any changes. In cases where you need to use platform-specific features and integrate with system libraries, Qt also provides solutions for this.</p>
<p>Qt integrates with the windowing system on the target platform using <a href="qpa.html">Qt Platform Abstraction</a> (QPA). QPA is an abstraction of a windowing system which makes porting Qt to new platforms simple and quick. One such system is the Wayland protocol. Qt can be used together with <a href="wayland-introduction.html"> Wayland</a> as light-weight windowing system on embedded hardware to support a multi-process graphical user interface.</p>
<p>The Qt Platform Abstraction uses Qt's plugin system. This system provides APIs to extend Qt in specific areas (such as adding support for new image formats, database drivers, and so on) and also for writing your own extensible Qt applications which support third-party plugins.</p>
</div>
<!-- @@@topics-core.html -->
</div>
</div>
</div>
<div class="footer">
    <p>
      <acronym title="Copyright">&copy;</acronym> 2013 Digia Plc and/or its
      subsidiaries. Documentation contributions included herein are the copyrights of
      their respective owners.</p>
    <br />
    <p>
      The documentation provided herein is licensed under the terms of the
      <a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation
      License version 1.3</a> as published by the Free Software Foundation.</p>
    <p>
      Documentation sources may be obtained from <a href="http://www.qt-project.org">
      www.qt-project.org</a>.</p>
    <br />
    <p>
      Digia, Qt and their respective logos are trademarks of Digia Plc 
      in Finland and/or other countries worldwide. All other trademarks are property
      of their respective owners. <a title="Privacy Policy"
      href="http://en.gitorious.org/privacy_policy/">Privacy Policy</a></p>
</div>
</body>
</html>