View Single Post
Posts: 287 | Thanked: 862 times | Joined on Dec 2015
#14
Originally Posted by ruff View Post
Ehm, yes, if there's xml or just bullet-point call/descr. to avoid reverse-engineering it.
In org.rockwork, there's a core object registered then one for each pebble. The core one is /org/rockwork/Manager:
  • signal void org.rockwork.Manager.PebblesChanged()
  • method QList<QDBusObjectPath> org.rockwork.Manager.ListWatches()
  • method QString org.rockwork.Manager.Version()

then each watch by bluetooth address: e.g. for my watch /org/rockwork/B0_B4_48_80_B9_87

I've grouped these by function and importance

Connection management & discovery
  • signal void org.rockwork.Pebble.Connected()
  • signal void org.rockwork.Pebble.Disconnected()
  • method QString org.rockwork.Pebble.Address()
  • method QString org.rockwork.Pebble.HardwarePlatform()
  • method bool org.rockwork.Pebble.IsConnected()
  • method int org.rockwork.Pebble.Model()
  • method QString org.rockwork.Pebble.Name()
  • method QString org.rockwork.Pebble.SerialNumber()
  • method QString org.rockwork.Pebble.SoftwareVersion()


Watch app management
  • signal void org.rockwork.Pebble.InstalledAppsChanged()
  • method void org.rockwork.Pebble.ConfigurationClosed(QString uuid, QString result)
  • method void org.rockwork.Pebble.ConfigurationURL(QString uuid)
  • method void org.rockwork.Pebble.InstallApp(QString id)
  • method QStringList org.rockwork.Pebble.InstalledAppIds()
  • method QVariantList org.rockwork.Pebble.InstalledApps()
  • method void org.rockwork.Pebble.RemoveApp(QString id)
  • method void org.rockwork.Pebble.SetAppOrder(QStringList newList)
  • method void org.rockwork.Pebble.SideloadApp(QString packageFile)

Firmware upgrades
  • signal void org.rockwork.Pebble.FirmwareUpgradeAvailableChange d()
  • signal void org.rockwork.Pebble.UpgradingFirmwareChanged()
  • method QString org.rockwork.Pebble.CandidateFirmwareVersion()
  • method QString org.rockwork.Pebble.FirmwareReleaseNotes()
  • method bool org.rockwork.Pebble.FirmwareUpgradeAvailable()
  • method void org.rockwork.Pebble.PerformFirmwareUpgrade()
  • method bool org.rockwork.Pebble.Recovery()
  • method bool org.rockwork.Pebble.UpgradingFirmware()

Notification filtering
  • signal void org.rockwork.Pebble.NotificationFilterChanged(QStr ing sourceId, bool enabled)
  • method QVariantMap org.rockwork.Pebble.NotificationsFilter()
  • method void org.rockwork.Pebble.SetNotificationFilter(QString sourceId, bool enabled)

Screenshot management (who knew this was a thing...?)
  • signal void org.rockwork.Pebble.ScreenshotAdded(QString filename)
  • signal void org.rockwork.Pebble.ScreenshotRemoved(QString filename)
  • method void org.rockwork.Pebble.RemoveScreenshot(QString filename)
  • method void org.rockwork.Pebble.RequestScreenshot()
  • method QStringList org.rockwork.Pebble.Screenshots()

Misc config
  • signal void org.rockwork.Pebble.CalendarSyncEnabledChanged()
  • signal void org.rockwork.Pebble.HealthParamsChanged()
  • signal void org.rockwork.Pebble.ImperialUnitsChanged()
  • signal void org.rockwork.Pebble.LogsDumped(bool success)
  • signal void org.rockwork.Pebble.OpenURL(QString uuid, QString url) - I'm not sure this one is useful now, as RockWork used to launch a webbrowser for app config and associate itself with the pebblejs URL scheme to capture the return. I think this has been removed now.
  • method bool org.rockwork.Pebble.CalendarSyncEnabled()
  • method void org.rockwork.Pebble.DumpLogs(QString fileName)
  • method QVariantMap org.rockwork.Pebble.HealthParams()
  • method bool org.rockwork.Pebble.ImperialUnits()
  • method void org.rockwork.Pebble.LaunchApp(QString uuid)
  • method void org.rockwork.Pebble.SetCalendarSyncEnabled(bool enabled)
  • method void org.rockwork.Pebble.SetHealthParams(QVariantMap healthParams)
  • method void org.rockwork.Pebble.SetImperialUnits(bool imperialUnits)


Originally Posted by ruff View Post
I can of course, to VM, and even to the phone, but how would it work when generating harbour RPM - will it pull the dependency from some (hidden) repo? If not - should be statically linked (as smoku did).
Yes, it gets declared as a dependency in the RPM, then the lib just gets installed from the standard Sailfish repo during install, just like other libs. As for the harbour - I think this has about as much chance of getting in the Jolla store as Smoku's did - it just uses too many not-yet-approved APIs.

Last edited by abranson; 2016-03-13 at 15:09.
 

The Following 5 Users Say Thank You to abranson For This Useful Post: