| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I238604bec632fe15791d29955ef57de943a5e334
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
|
|
|
| |
Change-Id: Ie3d304c684e9db86aede0c2f8a80d18ec77ab9ba
|
|
|
|
| |
Change-Id: I4dd19ca2588a7fdb2eea378e4c5598408f609799
|
|
|
|
| |
Change-Id: Ibcb3c61d72122e656e59cc7d9b139d58d2d45ad4
|
|
|
|
| |
Change-Id: Ib4886cbae2238a923807f79afa0cf1267fa03d29
|
|
|
|
|
|
| |
Change-Id: Ic8f41f1f365ded474668c1ec8658bd75239269a9
Reviewed-by: Sergio Ahumada <sahumada@blackberry.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
|
|
|
| |
Change-Id: I6b9ba773a3ac4e650e008d5af11a2be1d19aaf8a
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>
|