[SailfishDevel] Full Emulator and/or APIs

[Robin Burchell]

Hi,

I can’t cover the SDK part of this because I’m not intimately familiar
with the SDK releasing process/plans, but some comments on APIs:

We cannot provide full store support on every single aspect of the
device from day one. It would be nice if we could, but we haven’t had
the time to do the full “vetting” to make sure that everything is high
quality and future-proof for store applications. So we are going to be
limiting APIs that store applications can use. These limits will
expand (hopefully quickly) over time (with feedback & help from you
guys), but initially, the list is quite small.

More information on this will be coming soon, I hope. I know this is a
bit frustrating to hear, but it’d be even more frustrating if we
didn’t apply any such limits and then broke all your applications on
the first update, right? :) - rest assured, we know it’s frustrating
and are busy nailing down the loose ends so we can give you a clear
picture very soon.

On to your specific examples:
For call, the supported “API” will be tel: URIs. For messaging, we
will likewise support the sms: URI.

BR,
Robin

On Thu, Nov 21, 2013 at 1:02 AM, Joseph Crowell
<joseph.w.crowell at gmail.com> wrote:
> What about the accounts/messaging api that Jolla will actually use? A common
> HAL that we can use to make generic calls to device hardware? Everyone
> always wants to make a nifty flashlight app. NFT integration. If base rpms
> are going to be on the released devices, shouldn't they all be in the SDK
> emulator as well?
>
>
> On 11/20/2013 01:20 PM, Andrey Kozhevnikov wrote:
>
> you wrong again :)
> install qt5-qttools-qdbus
>
> and transfer api also here, just not integrated to emulator ui.
>
> On 20.11.2013 19:17, Tone Kastlunger wrote:
>
> coderus, dbus is, but handfull tools like qdbus is not :)
> Ofc you could always build & deploy them by yourself as well :)
> Same goes for the transfer UI, which is completely absent.
>
>
> On Wed, Nov 20, 2013 at 2:55 PM, Andrey Kozhevnikov <coderusinbox at gmail.com>
> wrote:
>>
>> dbus is here and fully functional :)
>>
>>
>> On 20.11.2013 18:54, wsvries wrote:
>>>
>>> Same question from me about "Qt Serial Port".
>>> And, I also need QDBus.
>>> Cannot port my app until it is supported.
>>> wim
>>>
>>> Gabriel Boehme schreef op 2013-11-20 12:36:
>>>>
>>>> Hi sailors,
>>>>
>>>> @JollaHQ told me on Twitter to discuss the following question on the
>>>> mailing list, but is more or less a question to some official Jolla
>>>> member.
>>>>
>>>> Is there any plan to release with the next updates an emulator, with all
>>>> standard apps/APIs integrated? This would be very helpful to create/port
>>>> (better) apps. At the moment I'm missing some dbus service/API related
>>>> to the camera. Also I'm not sure at the moment, how to share results
>>>> from my app with the common Sailfish calendar, also social service
>>>> integration would be a big benefit - share options for example.
>>>>
>>>> I guess you are very busy at the moment, but would be nice to hear some
>>>> details. And in a week the first real devices are sold, so it would be
>>>> nice to offer some native stuff for all these sailors.
>>>>
>>>> Thank you very much.
>>>>
>>>> Gabriel.
>>>>
>>>> _______________________________________________
>>>> SailfishOS.org Devel mailing list
>>>
>>> _______________________________________________
>>> SailfishOS.org Devel mailing list
>>
>>
>> _______________________________________________
>> SailfishOS.org Devel mailing list
>
>
>
>
> _______________________________________________
> SailfishOS.org Devel mailing list
>
>
>
>
> _______________________________________________
> SailfishOS.org Devel mailing list
>
>
>
> _______________________________________________
> SailfishOS.org Devel mailing list