Hi @abranson , So after the conversation over on Telegraph what are your thoughts. I'm willing to have a go at creating an extension to PebbleKitJS to let watch apps read phone state but it's hard to know what format Pebble would go with.
It's your project, I have no expectation that you will accept code just because someone has written it so before I spend time on this what are you likely to accept if anything.
ok, then first we probably need to define what do we need from the phone. If there's some existing phone object in android sdk we can get that as a baseline and just map jskit on it, finding corresponding items on the sailfish
i wasn't expecting michael to be interesting in the dbus thing, for me it's a good differentiator between what sailfish is and what ubuntu touch is trying to do. Sailfish is all about giving you the full potential of your device along with the risks that go along with it. They seem to be trying to create another consumer safe OS that just happens to use linux underneath.
it took mroe than 10years for enterprises to accept linux. Only as a server. Desktop is slowly leaking in, phones are on the way. btw desktops also started from some highly customized locked down thin clients.
i don't see why we have to limit what we do with our phones just because the average user would have trouble with it. i think there's a market for 'unreformed' geeks. put a warning on it, sure, but don't stop me messing around. that's why i have a jolla really.
I think there is a difference between Jolla and SFOS as well. Non technical users can really get along with Jolla and Harbour but will run away from downloading stuff from OpenRepos. Its one of the reasons I don't like to see Jolla having so many problems, it limits the audience.
as a result, when they ported cutespot over, it would stop playing when it lost focus. they're now designing some special background hook so things like that can run in the background in special circumstances just like in iOS. Same weak battery life arguments apply
from what i know, we share telepathy, mpris (though that's got some special QtMultimedia wrapper in Ubuntu). They use upstart of course instead of systemd.
I've tried setting up phone emulator - it lacks many things, not just bluetooth. on the other hand since you're going to work with daemon part - just check whether required dbus interfaces (or whatever you're going to use as data feed) is present there. to me emulator is still more convenient than phone - all in one place.