On 09/02/14 14:52, David Greaves wrote:
On 09/02/14 11:28, Putze Sven wrote:
As pointed out from others, it's not simply done with the Qt documentation.
The Sailfish OS is built upon many libraries, frameworks and layers. But
which one is to use?
Qt.
Seriously. You asked for "an API". Jolla supports the Qt API precisely because
it is a single, high level, app-suitable API that is well managed and open. It
provides a significant degree of platform independence by abstracting a large
amount of platform capability provided by those underlying layers; there is not
much 'limited' about it :)
Even the list of Qt libs at
https://github.com/sailfish-sdk/sdk-harbour-rpmvalidator/blob/master/allowed_libraries.conf
is fairly skimpy. Skimpy to the point that even all the Qt essential
modules are not covered. The fact that Qt itself is a bit, well,
optimistic when it says " They are available on all supported
development platforms and on the tested target platforms" is a different
matter. With the loss and current slow rebuilding of the mobility
functionally, feature-rich/low-level development is on the hard side.
Back in the Harmattan days this was the exact reason why there was the
QtSDK for the high-level app-developer and a Platform SDK for all the
people who didn't mind their hands getting dirty and getting an
incompatibility or two as things moved on.
Attila
_______________________________________________
SailfishOS.org Devel mailing list
