<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<STYLE>
BLOCKQUOTE {
MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em; MARGIN-TOP: 0px
}
OL {
MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px
}
UL {
MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px
}
P {
MARGIN-BOTTOM: 0px; MARGIN-TOP: 0px
}
BODY {
FONT-SIZE: 10.5pt; FONT-FAMILY: 微软雅黑; COLOR: #000000; LINE-HEIGHT: 1.5
}
</STYLE>
<META name=GENERATOR content="MSHTML 11.00.9600.16384"></HEAD>
<BODY style="MARGIN: 10px">
<DIV style="MARGIN-RIGHT: 0px" dir=ltr><SPAN><FONT size=2
face=Verdana></FONT></SPAN> </DIV>
<DIV style="MARGIN-RIGHT: 0px" dir=ltr><SPAN><FONT size=2
face=Verdana>+111111111111111111</FONT></DIV></SPAN>
<DIV> </DIV>
<DIV
style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0cm; PADDING-TOP: 3pt; PADDING-LEFT: 0cm; BORDER-LEFT: medium none; PADDING-RIGHT: 0cm">
<DIV
style="FONT-SIZE: 12px; FONT-FAMILY: tahoma; BACKGROUND: #efefef; COLOR: #000000; PADDING-BOTTOM: 8px; PADDING-TOP: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px">
<DIV><B>From:</B> <A href="mailto:mikelima@gmail.com">Luciano
Montanaro</A></DIV>
<DIV><B>Date:</B> 2014-02-04 01:10</DIV>
<DIV><B>To:</B> <A href="mailto:devel@lists.sailfishos.org">Sailfish OS
Developers</A></DIV>
<DIV><B>CC:</B> <A href="mailto:david.greaves@jolla.com">David
Greaves</A></DIV>
<DIV><B>Subject:</B> Re: [SailfishDevel] When does Jolla give us an
API?</DIV></DIV></DIV>
<DIV>
<DIV>Hi everybody,</DIV>
<DIV> </DIV>
<DIV>I too find documentation a bit missing...</DIV>
<DIV>But it is not much about APIs, but system level documentation.</DIV>
<DIV>Qt documentation is good, at least for the parts that are still</DIV>
<DIV>actively maintained.</DIV>
<DIV> </DIV>
<DIV>But SailfishOS uses Qt, on top of wayland, systemd, pulse,gstreamer</DIV>
<DIV>and telepathy, and a bunch of other services.</DIV>
<DIV> </DIV>
<DIV>Open source package documentation can be very good, or completely
missing.</DIV>
<DIV> </DIV>
<DIV>Moreover, to achjeve the same thing I may use a Qt based API, or,
say,</DIV>
<DIV>DBUS messages.</DIV>
<DIV> </DIV>
<DIV>So I think that more than the APIs, it is the list of "allowed" or</DIV>
<DIV>preferred services that is needed.</DIV>
<DIV> </DIV>
<DIV>SailfishOS as a Linux distribution is quite modern, and it would help</DIV>
<DIV>to know more about its plumbing.</DIV>
<DIV> </DIV>
<DIV>Just my 2 cents.</DIV>
<DIV> </DIV>
<DIV>Best regards,</DIV>
<DIV> </DIV>
<DIV>Luciano</DIV>
<DIV> </DIV>
<DIV>On Mon, Feb 3, 2014 at 5:59 PM, <christopher.lamb@thurweb.ch>
wrote:</DIV>
<DIV>> Hi all</DIV>
<DIV>></DIV>
<DIV>> my experience is that are a vast amount of apis out there: There is
all the</DIV>
<DIV>> Qt stuff, the Qt add-ons, Nemo packages, and lower-level stuff
like</DIV>
<DIV>> telepathy and GST. The problem is not the lack of APIs, but the choice
of</DIV>
<DIV>> APIs. Which is the best one to use?.</DIV>
<DIV>></DIV>
<DIV>> Then if you hit on a likely API, and find some good examples on
the</DIV>
<DIV>> interweb, then it is not sure that that API will fully work on the
Jolla</DIV>
<DIV>> (although this is likely to improve with every update as the Jolla
matures).</DIV>
<DIV>></DIV>
<DIV>> And if the chosen API works from a technical point of view, then that
does</DIV>
<DIV>> not mean that harbour will permit it ... although this too should
improve</DIV>
<DIV>> with time.</DIV>
<DIV>></DIV>
<DIV>> On the whole I have found the Qt documentation to be very good. Where
things</DIV>
<DIV>> get a bit shaky is using esoteric things like gaining device
resource</DIV>
<DIV>> permissions (e.g permission to use the LED, or to access the
phones</DIV>
<DIV>> contacts). For this sort of thing I often have to resort to the source
code</DIV>
<DIV>> ....(which at work we call the ultimate documentation .8-) )</DIV>
<DIV>></DIV>
<DIV>> mfg</DIV>
<DIV>></DIV>
<DIV>> Chris</DIV>
<DIV>></DIV>
<DIV>> Zitat von "David Greaves" <david.greaves@jolla.com>:</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>>> On 03/02/14 15:29, Putze Sven wrote:</DIV>
<DIV>>>></DIV>
<DIV>>>> Hi there,</DIV>
<DIV>>>></DIV>
<DIV>>>> during Fosdem I spoke to some people about this, even to
Carsten Munk</DIV>
<DIV>>>> from</DIV>
<DIV>>>> Jolla itself (not in the depth and detail of this mail, I must
admit) and</DIV>
<DIV>>>> he</DIV>
<DIV>>>> suggested to write this in the mailing list, so those of Jolla
who should</DIV>
<DIV>>>> be</DIV>
<DIV>>>> concerned have a chance to answer this question and I really
would like</DIV>
<DIV>>>> to</DIV>
<DIV>>>> hear some official statements here.</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> Did you manage to get to the round-table event? - we spent a fair
bit of</DIV>
<DIV>>> time</DIV>
<DIV>>> talking about APIs there; we also openly discussed the issues we
face.</DIV>
<DIV>>></DIV>
<DIV>>> I know that the community people there wanted to continue the
discussion.</DIV>
<DIV>>></DIV>
<DIV>>>> What does a developer need to write quality apps? An API and
a</DIV>
<DIV>>>> documentation</DIV>
<DIV>>>> of such.</DIV>
<DIV>>>></DIV>
<DIV>>>> So far there is a quite limited API available and therefore we
don't see</DIV>
<DIV>>>> too</DIV>
<DIV>>>> many apps out there. How will you write a sophisticated app,
if the API</DIV>
<DIV>>>> is</DIV>
<DIV>>>> not available or it is not allowed to use or is only known to
those with</DIV>
<DIV>>>> Maemo/Meego history?</DIV>
<DIV>>></DIV>
<DIV>>></DIV>
<DIV>>> A quick response: we support the Qt API and rather than developing
our own</DIV>
<DIV>>> proprietary one we're working hard to support the open one as it
grows.</DIV>
<DIV>>></DIV>
<DIV>>> The Qt documentation is extensive and superb :)</DIV>
<DIV>>> Using it in Sailfish Silica apps is less well documented but is
improving</DIV>
<DIV>>> (and</DIV>
<DIV>>> honestly is mainly a tutorial issue for new developers - not an
API docs</DIV>
<DIV>>> issue).</DIV>
<DIV>>></DIV>
<DIV>>> Yes there are some APIs in the mobile space that are not part of
the Qt</DIV>
<DIV>>> release</DIV>
<DIV>>> yet - Qt 5.2 will introduce more.</DIV>
<DIV>>></DIV>
<DIV>>> David</DIV>
<DIV>>></DIV>
<DIV>>> _______________________________________________</DIV>
<DIV>>> SailfishOS.org Devel mailing list</DIV>
<DIV>>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> SailfishOS.org Devel mailing list</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>-- </DIV>
<DIV>Luciano Montanaro</DIV>
<DIV> </DIV>
<DIV>Anyone who is capable of getting themselves made President should on</DIV>
<DIV>no account be allowed to do the job. -- Douglas Adams</DIV>
<DIV>_______________________________________________</DIV>
<DIV>SailfishOS.org Devel mailing list</DIV></DIV></BODY></HTML>