Changeset 769 for trunk/doc/src/platforms

Timestamp:

Aug 2, 2010, 9:27:30 PM (15 years ago)

Author:

Dmitry A. Kuminov

Message:

trunk: Merged in qt 4.6.3 sources from branches/vendor/nokia/qt.

Location:

trunk

Files:

• . (modified) (1 prop)
• doc/src/platforms/emb-directfb-EmbLinux.qdoc (modified) (2 diffs)
• doc/src/platforms/emb-features.qdoc (modified) (1 diff)
• doc/src/platforms/emb-install.qdoc (modified) (2 diffs)
• doc/src/platforms/emb-openvg.qdocinc (modified) (2 diffs)
• doc/src/platforms/platform-notes.qdoc (modified) (3 diffs)
• doc/src/platforms/supported-platforms.qdoc (modified) (1 diff)
• doc/src/platforms/symbian-introduction.qdoc (modified) (1 diff)
• doc/src/platforms/wince-customization.qdoc (modified) (2 diffs)

trunk/doc/src/platforms/emb-directfb-EmbLinux.qdoc

@@ -268 +268 @@
     \o By default Qt will use DirectFB to load QPixmaps from disk/memory. If
 your DirectFB implementation does not support this it might make sense to
-define this.
+define this. If you see strange rendering issues with pixmaps that have an
+alpha channel defining this could solve the problem.
 
  \row
@@ -328 +329 @@
 defines should only be used when optimizing the application. 
 
+\section2 Top level transparency
+\note DirectFB supports partially or fully transparent top level windows,
+either through QWidget::setWindowOpacity or through setting a non-opaque
+background brush. Note that for the latter it is not supported to change an
+opaque window to be transparent at runtime.
 */

trunk/doc/src/platforms/emb-features.qdoc

@@ -106 +106 @@
     desktop platforms.
 
-    \bold{Windows CE:} The Qt for Windows CE package contains a \c qconfig
-    executable that you can run on a Windows desktop to configure the build.
-
     \image qt-embedded-qconfigtool.png
 

trunk/doc/src/platforms/emb-install.qdoc

@@ -85 +85 @@
     ./configure script to configure the library for your development
     architecture. You can list all of the configuration system's
-    options by typing \c {./configure -help}.
+    options by typing
+
+    \snippet doc/src/snippets/code/doc_src_emb-install.qdoc embedded help
 
     Note that by default, \l{Qt for Embedded Linux} is configured for
-    installation in the \c{/usr/local/Trolltech/QtEmbedded-4.6.2}
+    installation in the \c{/usr/local/Trolltech/QtEmbedded-4.6.3}
     directory, but this can be changed by using the \c{-prefix}
     option. Alternatively, the \c{-prefix-install} option can be used
@@ -148 +150 @@
     For compilers that do not support \c rpath you must also extend
     the \c LD_LIBRARY_PATH environment variable to include
-    \c /usr/local/Trolltech/QtEmbedded-4.6.2/lib. Note that on Linux
+    \c /usr/local/Trolltech/QtEmbedded-4.6.3/lib. Note that on Linux
     with GCC, this step is not needed.
 

trunk/doc/src/platforms/emb-openvg.qdocinc

@@ -136 +136 @@
 
 The other members of QPainter::CompositionMode are not supported
-because OpenVG 1.1 does not have an equivalent in its \c VGBlendMode
-enumeration.  Any attempt to set an unsupported mode will result in
+unless the \c{VG_KHR_advanced_blending} extension is present,
+in which case the following additional modes are supported:
+
+\list
+\o QPainter::CompositionMode_Overlay
+\o QPainter::CompositionMode_ColorDodge
+\o QPainter::CompositionMode_ColorBurn
+\o QPainter::CompositionMode_HardLight
+\o QPainter::CompositionMode_SoftLight
+\o QPainter::CompositionMode_Difference
+\o QPainter::CompositionMode_Exclusion
+\o QPainter::CompositionMode_SourceOut
+\o QPainter::CompositionMode_DestinationOut
+\o QPainter::CompositionMode_SourceAtop
+\o QPainter::CompositionMode_DestinationAtop
+\o QPainter::CompositionMode_Xor
+\endlist
+
+Any attempt to set an unsupported mode will result in
 the actual mode being set to QPainter::CompositionMode_SourceOver.
 Client applications should avoid using unsupported modes.
@@ -260 +277 @@
 accelerated using OpenVG operations.
 
+    \row
+        \o Scrolling
+        \o Accelerated scrolling is implemented but disabled by default
+unless QVG_BUFFER_SCROLLING is defined. This should only be enabled on
+OpenVG engines where vgCopyPixels() is known to be efficient.
+
 \endtable
 

trunk/doc/src/platforms/platform-notes.qdoc

@@ -251 +251 @@
     \section1 Windows Vista
 
-    At the time Qt 4.6.2 was released, there were no known Vista-specific issues.
+    At the time Qt 4.6.3 was released, there were no known Vista-specific issues.
 
     \target Windows NT
@@ -420 +420 @@
 
     Qt for Symbian provides the same level of source compatibility guarantee as
-    given for other platforms. Â That is, a program which compiles against a given
+    given for other platforms. That is, a program which compiles against a given
     version of Qt for Symbian will also compile against all future versions of the
     same major release.
@@ -503 +503 @@
     \l{Exception Safety with Symbian}.
 
+    \section1 Required Capabilities
+
+    The Qt libraries are typically signed with \c{All -TCB} capabilites, but
+    that does not mean your Qt application needs to be signed with the same
+    capabilities to function properly. The capabilities your application needs
+    to function properly depends on which parts of Qt you use, here is an
+    overview:
+
+    \table
+    \header \o Module
+            \o Required Symbian Capability
+    \row    \o QtCore
+            \o \c PowerMgmt if QProcess::kill(...) or QProcess::terminate(...) is called.
+    \row    \o QtCore
+            \o \c AllFiles when \l{http://developer.symbian.org/wiki/index.php/Capabilities_%28Symbian_Signed%29/AllFiles_Capability}{accessing specific areas.}
+    \row    \o QtNetwork
+            \o \c NetworkServices is basically always required for this module.
+    \row    \o QtMultiMedia
+            \o \c UserEnvironment if QAudioInput is used.
+    \endtable
+
+    Note that some modules rely on other modules. If your application uses
+    QtXmlPatterns, QtWebkit or QtScript it may still require \c NetworkServices
+    \o as these modules rely on QtNetwork to go online.
+
+    For more information see the documentation of the individual Qt classes. If
+    a class does not mention Symbian capabilities, it requires none.
+
     \section1 Multimedia and Phonon Support
 

trunk/doc/src/platforms/supported-platforms.qdoc

@@ -117 +117 @@
     \row    \o HPUXi 11.23
                                      \o aCC 6.10
-    \row    \o Solaris 10 UltraSparc
+    \row    \o Solaris 10 (UltraSparc, x86)
                                      \o Sun Studio 12
     \row    \o AIX 6

trunk/doc/src/platforms/symbian-introduction.qdoc

@@ -133 +133 @@
                                 missing dependencies in addition to
                                 just installing the application.
+    \row \o \c stub_sis      \o Create a stub sis to allow upgradability of projects
+                                that are deployed in ROM
     \endtable
 

trunk/doc/src/platforms/wince-customization.qdoc

@@ -214 +214 @@
     \o The shadow build directory must be on the same level as the Qt source
         package.\br
-    If the Qt package is in \c{C:\Qt\4.6.2} the shadow build directory
+    If the Qt package is in \c{C:\Qt\4.6.3} the shadow build directory
     could be \c{C:\Qt\shadowbuild}. A shadow build from a directory like
     \c{C:\shadowbuild} will not compile.
@@ -225 +225 @@
     \endlist
 
-    So lets assume you have installed Qt in \c{C:\Qt\4.6.2} and you want
+    So lets assume you have installed Qt in \c{C:\Qt\4.6.3} and you want
     to create a shadow build in \c{C:\Qt\mobile5-shadow}: