cpfeiffer
234beace29
Some fixes for the background webview
2017-02-25 21:50:05 +01:00
cpfeiffer
711800f3d0
Collaborative attempt to initialize the background webview on startup
2017-02-25 18:01:08 +01:00
Daniele Gobbetti
a4ac108287
Pebble: merge master moving the location override to WebViewSingleton
2017-02-25 15:44:37 +01:00
Daniele Gobbetti
d6dd03a065
Pebble: webview add safety check
2017-01-28 17:45:23 +01:00
Daniele Gobbetti
c9cfaa9bd8
Pebble: webview. Implement two way communication with JS.
...
The support within JS is a bit hacky and sometimes conflicts with the configuration page.
2017-01-03 15:04:51 +01:00
Daniele Gobbetti
0efacfbad5
Pebble: webview ensure the webview works no matter which the order of loading the components is.
2017-01-02 12:32:52 +01:00
Daniele Gobbetti
7ab74fb11b
Pebble: webview. Use the main thread explicitly again and log XHR requests at least on Lollipop and up
2017-01-02 12:07:57 +01:00
Daniele Gobbetti
4ef0415da2
Pebble: webview. Ensure we are on the main thread for disposing the webview and implement sending messages to the webview.
2017-01-01 21:01:58 +01:00
Daniele Gobbetti
d22c78e8f7
Pebble: webview, simplify the code since finals are not required anymore
2017-01-01 18:37:42 +01:00
Daniele Gobbetti
eaaa940637
Pebble: refactor the background webview
...
Now native controls seem to work (including datepicker), still the webview is not started upon watchapp start, but when long-pressing each app in the app manager. After the webview is started it will live in the background until device disconnect.
2017-01-01 18:33:39 +01:00
Daniele Gobbetti
dbf88bab5f
Outdated TODO removed
2016-12-29 20:44:04 +01:00
Daniele Gobbetti
53d8f88670
Pebble: first steps towards background JS execution.
...
Progress so far:
- webview is created upon watchapp launch
- webview is destroyed after disconnect
- ready event is fired in the background
- showConfiguration is fired upon webview display
2016-12-28 20:53:17 +01:00
