You can do this with MiniKube for development and testing, or Google Cloud's GKE for the real thing.
# Make sure you have MiniKube installed and it's the latest
const DATA_HND = 0x002d; | |
const parseData = (data) => { | |
const rawTemp = data.readInt16LE(0); | |
const rawHum = data.readInt16LE(2); | |
return { | |
temperature: rawTemp / 100, | |
humidity: rawHum / 100 | |
} | |
} |
function Set-WindowStyle { | |
param( | |
[Parameter()] | |
[ValidateSet('FORCEMINIMIZE', 'HIDE', 'MAXIMIZE', 'MINIMIZE', 'RESTORE', | |
'SHOW', 'SHOWDEFAULT', 'SHOWMAXIMIZED', 'SHOWMINIMIZED', | |
'SHOWMINNOACTIVE', 'SHOWNA', 'SHOWNOACTIVATE', 'SHOWNORMAL')] | |
$Style = 'SHOW', | |
[Parameter()] | |
$MainWindowHandle = (Get-Process –id $pid).MainWindowHandle |
@echo off | |
REM use this file to run the powershell script bypassing the policy restrictions | |
PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& '%~dpn0.ps1'" | |
pause |
This short code will show how to sync database file using Realm, but can be used for any file that you need to send to Wear (using Data API
). It just takes any file, change it to Asset
object and send it over to Wear device. Also it can be used Mobile->Wear, and Wear->Mobile.
When you need to sync database just call FileSender.syncRealm(context);
, that is it!
DISCLAIMER
"Proper" way would be to synchronize each transaction to DB, but it in most cases Wear is used very rarely comparing to mobile, so it would most likely cause a battery drain. My idea was to synchronize it only whene it is needed (so for example when app closes). If you want to make sure that you are using latest DB, just send trigger data using MessageAPI
from Wear to Phone with ask of syncing over its database, or keep some timestapm of last edit and check it.
<service android:name=".ListenerServiceFromWear"> | |
<intent-filter> | |
<action android:name="com.google.android.gms.wearable.BIND_LISTENER" /> | |
</intent-filter> | |
</service> |