| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
- Renamed LICENSE.LGPL to LICENSE.LGPLv21
- Added LICENSE.LGPLv3 & LICENSE.GPLv2
- Removed LICENSE.GPL
Change-Id: Iad800f28f4e85e3f00512400ed9c5ed196c5097a
Reviewed-by: Antti Kokko <antti.kokko@digia.com>
Reviewed-by: Tony Sarajärvi <tony.sarajarvi@digia.com>
|
|
|
|
|
| |
Change-Id: Id9eac4df2651d8f53288071526740e127116ad0f
Reviewed-by: Yoann Lopes <yoann.lopes@digia.com>
|
|
|
|
|
|
|
|
| |
In many cases we just want the jobject, this removes the need
to add the template type.
Change-Id: Iac5d8eab2b784908201baa8a05b126b4e7e5c86f
Reviewed-by: BogDan Vatra <bogdan@kde.org>
|
|
|
|
|
|
|
|
|
|
| |
Ideally the getStaticObjectField() and getObjectField() methods, that
take a signature, should never have been templated. Removing the
templated versions now will cause ABI breakage, so the only solution
is to add new non-templated versions.
Change-Id: I2f6e9f259b7bc511ef5bcaeb8a2077b0f267b8c8
Reviewed-by: BogDan Vatra <bogdan@kde.org>
|
|
|
|
|
|
|
|
|
|
|
| |
The Android SDK version, or API level, is commonly used to determine
what APIs are available at runtime.
[ChangeLog][QtAndroidExtras] Added convenience method for getting the
Android SDK version.
Change-Id: Ic20322f68bc9680aec9e1c8404583462063904db
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@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>
|
|
|
|
|
| |
Change-Id: I568576b0ec5d9c81a59dca21f43a8c7ce8f6bef1
Reviewed-by: Yoann Lopes <yoann.lopes@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>
|
|
|
|
|
| |
Change-Id: I4eafa7366a36d8444392b476d6262e54d67893bf
Reviewed-by: Christian Stromme <christian.stromme@digia.com>
|
|
|
|
|
| |
Change-Id: If1a72842165f20b84589d61885e5dc1902a8d171
Reviewed-by: Christian Stromme <christian.stromme@digia.com>
|
|
|
|
|
| |
Change-Id: I19aa638668ac8b4f263047d1e636d86abb73b91e
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@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>
|