| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove references of resultReceiver parameter from a new
QtAndroid::startActivity() overload, as it has no such parameter.
Add a few dummy typedefs specific to documentation builds, to avoid
the Clang-parser from tripping over undefined types on non-Android
platforms.
Fixes: QTBUG-79813
Change-Id: I6972ae7d5b8d4ca7f338af8958ccf3cf43dce71c
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
|
|
|
|
|
|
| |
Task-number: QTBUG-74391
Change-Id: Ie2b5f498fa6f4effc27f07f3aab0061fa77e94c9
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
The use of QT_INSTALL_HEADERS caused documentation build failures
in certain configurations. Use an alternative method to pass the
required include paths to QDoc.
Task-number: QTBUG-67925
Change-Id: Ia8c25b0cfb950f43ec60a3768cd192588a5e5617
Reviewed-by: Martin Smith <martin.smith@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QDoc in Qt 5.11 uses Clang to parse the C++ source for documentation
comments. Unlike the old parser, Clang requires a module header to
be present as well as correct include paths to generate the docs
correctly. However, these are available from the build system only
when building for Android, not when generating the documentation
on a system with no Android-related assets.
To fix this, create a 'dummy' module header specific to doc builds,
add required relative include paths in .qdocconf, and fix the
documentation \fn commands to work with Clang.
Change-Id: Ia3d4e50ff8756cd8c8aae9cd3c3d1492eb7db328
Reviewed-by: Martin Smith <martin.smith@qt.io>
|
|
|
|
|
| |
Change-Id: Icfe3f6a712a8e457dd695b5f0f982760eb78f4f1
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
|
|
|
|
|
| |
Change-Id: Ia4fbd4718a698e0d4a0835869e51852c12b1442d
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
|
|
|
|
|
|
|
|
| |
Examples in binary packages now directly match the install path.
Change-Id: I7a98d68cbc0623e86bb9dcfb3cadd1adc9631ebf
Task-number: QTBUG-52953
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
|
|
|
|
|
|
|
|
| |
Subjects a *.png file that matched grep -law "sRGB" to:
pngcrush -ow -brute -rem allb -reduce -force
Change-Id: Ief67f8ca4dfc44655af62e70c10cb623acf83642
Reviewed-by: Topi Reiniö <topi.reinio@theqtcompany.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The examplesinstallpath variable in .qdocconf files defines the path
under QT_INSTALL_EXAMPLES where examples are found.
To match the way examples are packaged in Qt 5.6, prefix the
install path with the repository name.
Task-number: QTBUG-48736
Change-Id: I4bc22773d7528fa6ffbb128b70c6708eceffcced
Reviewed-by: Venugopal Shivashankar <venugopal.shivashankar@digia.com>
|
|
|
|
|
| |
Change-Id: I8fc57754926b441c8d6cb81e25ea09a5eb3029a5
Reviewed-by: Sergio Ahumada <sahumada@texla.cl>
|
|
|
|
|
|
|
|
|
| |
Qt copyrights are now in The Qt Company, so we could update the source
code headers accordingly. In the same go we should also fix the links to
point to qt.io.
Change-Id: Id0bb1fd5a9d695520753a280bb1ad5ba1ccc6026
Reviewed-by: Sergio Ahumada <sahumada@texla.cl>
|
|
|
|
|
|
|
| |
-url inherited from the url variable set in qtbase/doc/global
Change-Id: I2064a47e17a56636586f6c69b1630781cf6f0aaa
Reviewed-by: Martin Smith <martin.smith@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
There were no public APIs the user could use to get access to
their applications main activity, and thus far the only solution have
been to access undocumented and private APIs.
[ChangeLog][QtAndroidExtras] Added functionality to get the Android main
activity.
Change-Id: Ifd4121e8bc643360ed7a7038ffae9e872b59db71
Reviewed-by: Paul Olav Tvete <paul.tvete@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QDoc ignores the .java files without the following entry in the
qdocconf:
examples.fileextensions += *.java
Java files are not part of the default set of file types included
by Qdoc. So there must be an entry in the qdocconf to force Qdoc
to include additional file types such as the .java files.
Task-number: QTBUG-35568
Change-Id: Ic8b805e0dec937fb0e8b19f0b94883ced5eb6c04
Reviewed-by: Christian Stromme <christian.stromme@digia.com>
Reviewed-by: Nico Vertriest <nico.vertriest@digia.com>
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
|
|
|
|
|
| |
Change-Id: I0e5160f18f89ed25882741d93410ea1860ed659a
Reviewed-by: Christian Stromme <christian.stromme@digia.com>
|
|
|
|
|
|
|
|
| |
If we don't add examplesinstallpath the examples won't be shown in
Qt Creator's welcome page.
Change-Id: Ia1c0015262e4dd3c6de83d7d73231e3e3e0cf027
Reviewed-by: Paul Olav Tvete <paul.tvete@digia.com>
|
|
|
|
|
|
|
|
| |
We should set a good example by deleting local refs. as soon as we are
done with, also in our own examples...
Change-Id: Ib9b25b226d79532c137e1c404625840ffd3cdf6e
Reviewed-by: Yoann Lopes <yoann.lopes@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In 5.2, the HTML output is in a flatter structure and when they are
hosted in qt-project.org/doc, the documentation will be found at
http://qt-project.org/doc/qt-$QT_VER
The url variable is used by projects outside of Qt 5 which need
to link to Qt 5 documentation, such as Qt Creator.
Task-number: QTBUG-34584
Change-Id: If3b2ef1bec1805e5f6bf14c8468126e4160e0ed0
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com>
Reviewed-by: Venugopal Shivashankar <venugopal.shivashankar@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
- The list of examples was not showing in the index page.
- Added information about types, method signatures, J2N and GC.
- Fixed some typos.
Change-Id: Ibe66ddbc0b1cac323563d629ca82bfe54d69dfc1
Reviewed-by: Venugopal Shivashankar <venugopal.shivashankar@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>
|
|
|
|
|
|
|
|
|
| |
The old classes where not following the usual convention for acronyms
in class names.
Change-Id: I2fad72483c51ca95a2703d914d6a678c5f7cde98
Reviewed-by: Jake Petroules <jake.petroules@petroules.com>
Reviewed-by: Yoann Lopes <yoann.lopes@digia.com>
|
|
|
|
|
|
|
|
| |
Needed in order to link to the main Qt 5.2 documentation.
Change-Id: I451f4d60f165befe179cfe58904876c42211cfee
Reviewed-by: Venugopal Shivashankar <venugopal.shivashankar@digia.com>
Reviewed-by: Martin Smith <martin.smith@digia.com>
|
|
|
|
|
| |
Change-Id: Ia3999f853aa9b0ca1678f322419ddd200cae4b1a
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|
|
|
|
|
|
|
|
| |
This example adds a custom class to the project and calls into
it with JNI to set a notification message in the status area.
Change-Id: I74d7a87c0511b98608422788c1c282e9af57c074
Reviewed-by: Christian Stromme <christian.stromme@digia.com>
|
|
The QJNI API's provide an easy way to communicate with Java API's from
C++. The API consists of two classes, QJNIObject which acts as a wrapper
around Java classes and QJNIEnvironment which attaches the current
thread to the Java VM and exposes the Java Native Interface.
Change-Id: I9cdc395249de74f940b75eab9f2bd32347d5d432
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
|