path: root/src/webchannel/doc/src/javascript.qdoc
diff options
authorTopi Reinio <>2014-08-13 14:14:49 +0200
committerMilian Wolff <>2014-08-13 14:43:24 +0200
commit62760f579b52fbd19d85d31fa90274f9b0dc5111 (patch)
treecb348241c606632ad9dbc575e28910e9302a2cc5 /src/webchannel/doc/src/javascript.qdoc
parent150fba9166d0cd63079d8ed15af5f80a759e9549 (diff)
Doc: Fix example documentation and paths
To fix issues related to example documentation and to follow Qt convention, do the following changes: - Rename examples/qwebchannel to examples/webchannel - Move example-specific documentation to correct location(s) - Include generic 'Running the Example' instructions - Add the module name to example title, fix links This ensures that example docs are built and the example manifest file generated correctly. Change-Id: I284e0b13db95a6738d72258735018b59156cc7da Reviewed-by: Milian Wolff <>
Diffstat (limited to 'src/webchannel/doc/src/javascript.qdoc')
1 files changed, 2 insertions, 1 deletions
diff --git a/src/webchannel/doc/src/javascript.qdoc b/src/webchannel/doc/src/javascript.qdoc
index de211d0..fa8edfe 100644
--- a/src/webchannel/doc/src/javascript.qdoc
+++ b/src/webchannel/doc/src/javascript.qdoc
@@ -49,7 +49,8 @@
Note that the JavaScript QWebChannel object should be constructed once the transport object is
fully operational. In case of a WebSocket, that means you should create the QWebChannel in the
- socket's \c onopen handler. Take a look at the \l{Standalone Example} to see how this is done.
+ socket's \c onopen handler. Take a look at the \l{Qt WebChannel Standalone Example} to see how
+ this is done.
\section1 Interacting with QObjects