/usr/share/qt5/doc/qtdoc/mobiledevelopment.html is in qt5-doc-html 5.9.5-0ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 | <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- mobile.qdoc -->
<title>Mobile APIs | Qt 5.9</title>
<link rel="stylesheet" type="text/css" href="style/offline-simple.css" />
<script type="text/javascript">
document.getElementsByTagName("link").item(0).setAttribute("href", "style/offline.css");
// loading style sheet breaks anchors that were jumped to before
// so force jumping to anchor again
setTimeout(function() {
var anchor = location.hash;
// need to jump to different anchor first (e.g. none)
location.hash = "#";
setTimeout(function() {
location.hash = anchor;
}, 0);
}, 0);
</script>
</head>
<body>
<div class="header" id="qtdocheader">
<div class="main">
<div class="main-rounded">
<div class="navigationbar">
<table><tr>
<td ><a href="index.html">Qt 5.9</a></td><td >Mobile APIs</td></tr></table><table class="buildversion"><tr>
<td id="buildversion" width="100%" align="right">Qt 5.9.5 Reference Documentation</td>
</tr></table>
</div>
</div>
<div class="content">
<div class="line">
<div class="content mainContent">
<div class="sidebar">
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level2"><a href="#supported-mobile-platforms">Supported Mobile Platforms</a></li>
<li class="level1"><a href="#sensors">Sensors</a></li>
<li class="level1"><a href="#positioning">Positioning</a></li>
<li class="level1"><a href="#location">Location</a></li>
<li class="level1"><a href="#bluetooth">Bluetooth</a></li>
<li class="level1"><a href="#nfc">NFC</a></li>
<li class="level1"><a href="#in-app-purchasing">In-App Purchasing</a></li>
</ul>
</div>
<div class="sidebar-content" id="sidebar-content"></div></div>
<h1 class="title">Mobile APIs</h1>
<span class="subtitle"></span>
<!-- $$$mobiledevelopment.html-description -->
<div class="descr"> <a name="details"></a>
<p>New in Qt 5 are APIs for mobile platforms. These APIs access various hardware and mobile features. There are also APIs for extending support to other devices and platforms.</p>
<a name="supported-mobile-platforms"></a>
<h3 >Supported Mobile Platforms</h3>
<p>The following pages contain information about setting up Qt Creator and how to get started with the mobile platforms:</p>
<ul>
<li><a href="android-support.html">Android</a></li>
<li><a href="ios-support.html">iOS</a></li>
</ul>
<a name="sensors"></a>
<h2 id="sensors">Sensors</h2>
<p>The Qt Sensors module's APIs allow access to various hardware sensors. Accelerometers, light sensors, compass, and gyroscope sensors are one of the many types of sensors supported by the QML and C++ APIs.</p>
<ul>
<li><a href="../qtsensors/qtsensors-index.html">Qt Sensors</a></li>
</ul>
<a name="positioning"></a>
<h2 id="positioning">Positioning</h2>
<p>Accessing location information through Global Positioning System (GPS) or Cell ID positioning is available through the positioning APIs from the Qt Positioning module. Additionally, devices which use NMEA protocols can be used as a source.</p>
<ul>
<li><a href="../qtpositioning/qtpositioning-index.html">Qt Positioning</a></li>
</ul>
<a name="location"></a>
<h2 id="location">Location</h2>
<p>The Qt Location module's API allows access to map, navigation, and place data. It is possible to interact with tile maps using gestures to pan, flick, and zoom. Additional information such as routes or places may be displayed on the map.</p>
<ul>
<li><a href="../qtlocation/qtlocation-index.html">Qt Location</a></li>
</ul>
<a name="bluetooth"></a>
<h2 id="bluetooth">Bluetooth</h2>
<p>The Qt Bluetooth module's APIs allows access to Bluetooth-enabled devices. There are APIs for scanning Bluetooth devices and sharing data among devices. The APIs have support for radio-frequency communication (RFCOMM) and OBEX Object Push Profile (OPP) protocols.</p>
<ul>
<li><a href="../qtbluetooth/qtbluetooth-index.html">Qt Bluetooth</a></li>
</ul>
<a name="nfc"></a>
<h2 id="nfc">NFC</h2>
<p>Near field communication (NFC) support is provided by the Qt NFC module. The QML and C++ APIs sets up communication between NFC Forum Tags and NFC Forum Devices through the of NFC Logical Link Control Protocol (LLCP).</p>
<ul>
<li><a href="../qtnfc/qtnfc-index.html">Qt NFC</a></li>
</ul>
<a name="in-app-purchasing"></a>
<h2 id="in-app-purchasing">In-App Purchasing</h2>
<p>The Qt Purchasing module enables mobile developers to generate revenue from their applications on Android and iOS platforms. The module provides C++ and QML alternatives to support the In-App purchasing use case in Qt applications.</p>
<ul>
<li>Qt Purchasing</li>
</ul>
</div>
<!-- @@@mobiledevelopment.html -->
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<p>
<acronym title="Copyright">©</acronym> 2017 The Qt Company Ltd.
Documentation contributions included herein are the copyrights of
their respective owners.<br> The documentation provided herein is licensed under the terms of the <a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License version 1.3</a> as published by the Free Software Foundation.<br> Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property
of their respective owners. </p>
</div>
</body>
</html>
|