Doc: Ensured that code snippets have appropriate file names.

This helps them to be marked up correctly in cases where code
markers are available.

13 files changed, 25 insertions, 25 deletions

diff --git a/doc/src/examples/arrowpad.qdoc b/doc/src/examples/arrowpad.qdoc
index bb22f83..5e9cc9a 100644
--- a/doc/src/examples/arrowpad.qdoc
+++ b/doc/src/examples/arrowpad.qdoc
@@ -66,7 +66,7 @@
     context: it is the context of the texts in the \c ArrowPad class. 
     The \c Q_OBJECT macro defines \c tr(x) in \c ArrowPad like this:
 
-    \snippet doc/src/snippets/code/doc_src_examples_arrowpad.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_arrowpad.cpp 0
 
     Knowing which class each source text appears in enables \e {Qt
     Linguist} to group texts that are logically related together, e.g.
diff --git a/doc/src/examples/containerextension.qdoc b/doc/src/examples/containerextension.qdoc
index 818547c..57295de 100644
--- a/doc/src/examples/containerextension.qdoc
+++ b/doc/src/examples/containerextension.qdoc
@@ -138,7 +138,7 @@
     target path for the project and adding it to the list of items to
     install:
 
-    \snippet doc/src/snippets/code/doc_src_examples_containerextension.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_containerextension.pro 0
 
     The container extension is created as a library, and will be
     installed alongside the other \QD plugins when the project is
diff --git a/doc/src/examples/customwidgetplugin.qdoc b/doc/src/examples/customwidgetplugin.qdoc
index f972500..5b6aab6 100644
--- a/doc/src/examples/customwidgetplugin.qdoc
+++ b/doc/src/examples/customwidgetplugin.qdoc
@@ -89,7 +89,7 @@
     target path for the project and adding it to the list of items to
     install:
 
-    \snippet doc/src/snippets/code/doc_src_examples_customwidgetplugin.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_customwidgetplugin.pro 0
 
     The custom widget is created as a library, and will be installed
     alongside the other \QD plugins when the project is installed
diff --git a/doc/src/examples/editabletreemodel.qdoc b/doc/src/examples/editabletreemodel.qdoc
index 042b745..5edc91b 100644
--- a/doc/src/examples/editabletreemodel.qdoc
+++ b/doc/src/examples/editabletreemodel.qdoc
@@ -131,14 +131,14 @@
     In the case shown in the diagram, the piece of information represented
     by \bold{a} can be obtained using the standard model/view API:
 
-    \snippet doc/src/snippets/code/doc_src_examples_editabletreemodel.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_editabletreemodel.cpp 0
 
     Since each items holds pieces of data for each column in a given row,
     there can be many model indexes that map to the same \c TreeItem object.
     For example, the information represented by \bold{b} can be obtained
     using the following code:
 
-    \snippet doc/src/snippets/code/doc_src_examples_editabletreemodel.qdoc 1
+    \snippet doc/src/snippets/code/doc_src_examples_editabletreemodel.cpp 1
 
     The same underlying \c TreeItem would be accessed to obtain information
     for the other model indexes in the same row as \bold{b}.
diff --git a/doc/src/examples/fancybrowser.qdoc b/doc/src/examples/fancybrowser.qdoc
index b46903d..bc30988 100644
--- a/doc/src/examples/fancybrowser.qdoc
+++ b/doc/src/examples/fancybrowser.qdoc
@@ -26,8 +26,8 @@
 ****************************************************************************/
 
 /*!
-   \example webkit/fancybrowser
-  \title Fancy Browser Example
+    \example webkit/fancybrowser
+    \title Fancy Browser Example
 
     The Fancy Browser example shows how to use jQuery with QtWebKit to
     create a web browser with special effects and content
diff --git a/doc/src/examples/icons.qdoc b/doc/src/examples/icons.qdoc
index 4210859..1f959f9 100644
--- a/doc/src/examples/icons.qdoc
+++ b/doc/src/examples/icons.qdoc
@@ -278,7 +278,7 @@
     If the application is built in debug mode, the \c Q_ASSERT()
     macro will expand to
 
-    \snippet doc/src/snippets/code/doc_src_examples_icons.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_icons.cpp 0
 
     In release mode, the macro simply disappear. The mode can be set
     in the application's \c .pro file. One way to do so is to add an
diff --git a/doc/src/examples/imageviewer.qdoc b/doc/src/examples/imageviewer.qdoc
index 70f71c8..f1d02c3 100644
--- a/doc/src/examples/imageviewer.qdoc
+++ b/doc/src/examples/imageviewer.qdoc
@@ -149,7 +149,7 @@
     \{QWidget::adjustSize()}{adjustSize()} to achieve this, which is
     essentially the same as
 
-    \snippet doc/src/snippets/code/doc_src_examples_imageviewer.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_imageviewer.cpp 0
 
     In the \c print() slot, we first make sure that an image has been
     loaded into the application:
@@ -160,7 +160,7 @@
     If the application is built in debug mode, the \c Q_ASSERT() macro
     will expand to
 
-    \snippet doc/src/snippets/code/doc_src_examples_imageviewer.qdoc 1
+    \snippet doc/src/snippets/code/doc_src_examples_imageviewer.cpp 1
 
     In release mode, the macro simply disappear. The mode can be set
     in the application's \c .pro file. One way to do so is to add an
@@ -318,7 +318,7 @@
     Whenever we zoom in or out, we need to adjust the scroll bars in
     consequence. It would have been tempting to simply call
 
-    \snippet doc/src/snippets/code/doc_src_examples_imageviewer.qdoc 4
+    \snippet doc/src/snippets/code/doc_src_examples_imageviewer.cpp 4
 
     but this would make the top-left corner the focal point, not the
     center. Therefore we need to take into account the scroll bar
diff --git a/doc/src/examples/qtscriptcustomclass.qdoc b/doc/src/examples/qtscriptcustomclass.qdoc
index f2b4f36..3ee6c95 100644
--- a/doc/src/examples/qtscriptcustomclass.qdoc
+++ b/doc/src/examples/qtscriptcustomclass.qdoc
@@ -46,7 +46,7 @@
     scripting environment, \c{ByteArray} objects can be constructed like
     so:
 
-    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.cpp 0
 
     \c{ByteArray} objects behave similar to normal \c{Array} objects. Every \c{ByteArray} object has
     a \c{length} property, that holds the length of the array. If a new value is assigned to the \c{length}
@@ -55,22 +55,22 @@
     Use normal array operations to read or write bytes in the array. The following code sets all the
     bytes of an array to a certain value:
 
-    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.qdoc 1
+    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.cpp 1
 
     When assigning a value to an array element, the value is truncated to eight bits:
 
-    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.qdoc 2
+    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.cpp 2
 
     Like normal \c{Array} objects, if the array index is greater than the current length
     of the array, the array is resized accordingly:
 
-    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.qdoc 3
+    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.cpp 3
 
     Property names that aren't valid array indexes are treated
     like normal object properties (again, the same is the case for normal \c{Array} objects);
     in other words, it's perfectly fine to do something like this:
 
-    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.qdoc 4
+    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.cpp 4
 
     The above assignment won't affect the contents of the array, but will rather assign a value
     to the object property named "foo".
@@ -78,7 +78,7 @@
     \c{ByteArray} objects have a set of methods: chop(), equals(), left(), mid(), toBase64() and so on.
     These map directly onto the corresponding methods in QByteArray.
 
-    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.qdoc 5
+    \snippet doc/src/snippets/code/doc_src_examples_qtscriptcustomclass.cpp 5
 
     \section1 ByteArray Class Implementation
 
diff --git a/doc/src/examples/simpledommodel.qdoc b/doc/src/examples/simpledommodel.qdoc
index ea380bd..9b4d80e 100644
--- a/doc/src/examples/simpledommodel.qdoc
+++ b/doc/src/examples/simpledommodel.qdoc
@@ -53,7 +53,7 @@
     snippet reads the contents of a file into a QDomDocument object and traverses the
     document, reading all the plain text that can be found:
 
-    \snippet doc/src/snippets/code/doc_src_examples_simpledommodel.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_simpledommodel.cpp 0
 
     In principle, the functions provided by QDomNode can be used to navigate from any
     given starting point in a document to the piece of data requested by another component.
diff --git a/doc/src/examples/taskmenuextension.qdoc b/doc/src/examples/taskmenuextension.qdoc
index 0200c2f..b557b8b 100644
--- a/doc/src/examples/taskmenuextension.qdoc
+++ b/doc/src/examples/taskmenuextension.qdoc
@@ -139,7 +139,7 @@
     target path for the project and adding it to the list of items to
     install:
 
-    \snippet doc/src/snippets/code/doc_src_examples_taskmenuextension.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_taskmenuextension.pro 0
 
     The task menu extension is created as a library, and will be
     installed alongside the other \QD plugins when the project is
diff --git a/doc/src/examples/textfinder.qdoc b/doc/src/examples/textfinder.qdoc
index e92bb98..f5f41d7 100644
--- a/doc/src/examples/textfinder.qdoc
+++ b/doc/src/examples/textfinder.qdoc
@@ -70,7 +70,7 @@
     QtUiTools module library. This is done in the \c{textfinder.pro} file
     that contains the following lines:
 
-    \snippet doc/src/snippets/code/doc_src_examples_textfinder.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_textfinder.pro 0
 
     \section1 TextFinder Class Definition
 
diff --git a/doc/src/examples/trollprint.qdoc b/doc/src/examples/trollprint.qdoc
index 3a77a71..a93811e 100644
--- a/doc/src/examples/trollprint.qdoc
+++ b/doc/src/examples/trollprint.qdoc
@@ -132,12 +132,12 @@
     second argument "two-sided" in the appropriate \c tr() calls to the
     first pair of radio buttons:
 
-    \snippet doc/src/snippets/code/doc_src_examples_trollprint.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_trollprint.cpp 0
 
     and add the second argument "colors" in the appropriate \c tr() calls
     for the second pair of radio buttons:
 
-    \snippet doc/src/snippets/code/doc_src_examples_trollprint.qdoc 1
+    \snippet doc/src/snippets/code/doc_src_examples_trollprint.cpp 1
 
     Now run \c lupdate and open \c trollprint_pt.ts with \e {Qt Linguist}. You
     should now see two changes.
@@ -177,7 +177,7 @@
     the translations. This can be achieved by using a \c TRANSLATOR comment
     in the source code:
 
-    \snippet doc/src/snippets/code/doc_src_examples_trollprint.qdoc 2
+    \snippet doc/src/snippets/code/doc_src_examples_trollprint.cpp 2
 
     Try adding these comments to some source files, particularly to
     dialog classes, describing the navigation necessary to reach the
@@ -192,7 +192,7 @@
     correct. Comments that provide good navigation information can save
     them time:
 
-    \snippet doc/src/snippets/code/doc_src_examples_trollprint.qdoc 3
+    \snippet doc/src/snippets/code/doc_src_examples_trollprint.cpp 3
 
     \section1 Troll Print 1.1
 
diff --git a/doc/src/examples/worldtimeclockplugin.qdoc b/doc/src/examples/worldtimeclockplugin.qdoc
index 61a214c..8a17004 100644
--- a/doc/src/examples/worldtimeclockplugin.qdoc
+++ b/doc/src/examples/worldtimeclockplugin.qdoc
@@ -176,7 +176,7 @@
     is searched by \QD. We do this by specifying a target path for the project
     and adding it to the list of items to install:
 
-    \snippet doc/src/snippets/code/doc_src_examples_worldtimeclockplugin.qdoc 0
+    \snippet doc/src/snippets/code/doc_src_examples_worldtimeclockplugin.pro 0
 
     The custom widget is created as a library, and will be installed
     alongside the other \QD plugins when the project is installed