Closed scottopell closed 10 years ago
I haven't committed the code to fix this issue. My fault as I decided not to commit the entire clean up branch since it was really unorganized.
So whats the status of this? Can we not embed the html in the pbw access it locally? Do we really need to host it externally?
It is the only method supported by Pebble. There are hacks to get around it but I'd really prefer it be hosted externally. The users have to connect to the internet anyways to share answers so it isn't a big deal.
One way we could ease the issue is to allow users to pick common channels within the watch app itself.
Fixed by 9a5af4a. Just run firebase deploy.
Another possibility is to embed the html page inside the pbw. This isn't endorsed by pebble, but its not a bad option. Basically you encode the html file into base64 and then say pebble open url data:test/html+ encoded html.
I have mixed feelings about this.
I think we should leave this as is, since it's endorsed by Pebble. I also like the fact that we're storing everything (including assets like this) on Firebase.
Also, I don’t even think you can use the Pebble application (iOS or Android) if you don’t have an internet connection, which would mean that a user can’t even access the offline pbw embedded local config page if he doesn’t have internet.
On Apr 21, 2014, at 3:10 PM, kirbyk notifications@github.com wrote:
I think we should leave this as is, since it's endorsed by Pebble. I also like the fact that we're storing everything (including assets like this) on Firebase.
— Reply to this email directly or view it on GitHub.
Kirby's CS account will not scale.