Testing this on the device brings up somethings I never thought about initially. We may need to patch existing cards vs. insert a new card for each workout because the timeline gets littered with old cards that are done. The user doesn't need to see those anymore.

invalid_grant
Traceback (most recent call last):
File "/python27_runtime/python27_lib/versions/third_party/webapp2-2.5.2/webapp2.py", line 1535, in call
rv = self.handle_exception(request, response, e)
File "/python27_runtime/python27_lib/versions/third_party/webapp2-2.5.2/webapp2.py", line 1529, in call
rv = self.router.dispatch(request, response)
File "/python27_runtime/python27_lib/versions/third_party/webapp2-2.5.2/webapp2.py", line 1278, in default_dispatcher
return route.handler_adapter(request, response)
File "/python27_runtime/python27_lib/versions/third_party/webapp2-2.5.2/webapp2.py", line 1102, in call
return handler.dispatch()
File "/python27_runtime/python27_lib/versions/third_party/webapp2-2.5.2/webapp2.py", line 572, in dispatch
return self.handle_exception(e, self.app.debug)
File "/python27_runtime/python27_lib/versions/third_party/webapp2-2.5.2/webapp2.py", line 570, in dispatch
return method(_args, *_kwargs)
File "/base/data/home/apps/s~xglassfit/1.368491947830689972/glassfit/tasks.py", line 68, in post
self.mirror_service.timeline().insert(body=card_body).execute()
File "lib/oauth2client/util.py", line 131, in positional_wrapper
return wrapped(_args, *_kwargs)
File "lib/apiclient/http.py", line 675, in execute
body=self.body, headers=self.headers)
File "lib/oauth2client/util.py", line 131, in positional_wrapper
return wrapped(_args, *_kwargs)
File "lib/oauth2client/client.py", line 496, in new_request
self._refresh(request_orig)
File "lib/oauth2client/client.py", line 665, in _refresh
self._do_refresh_request(http_request)
File "lib/oauth2client/client.py", line 712, in _do_refresh_request
raise AccessTokenRefreshError(error_msg)
AccessTokenRefreshError: invalid_grant

Need to figure out how to keep the screen from timing out (going to sleep) during a 30 second workout. When user wakes screen, countdown animated assets starts over, which artificially throws off queue timer

See screenshot in step 7:
https://developers.google.com/glass/quickstart/python

Ours should read:
http://localhost:11081

What we have right now is localhost without the port number.

Regarding Templates

Mockup templates

Welcome Splash - http://glassfit.org/promo/14%20-%201.png
Upcoming workout list (bundled with instructions etc) - http://glassfit.org/promo/14%20-%202.png
Warmup menu item - http://glassfit.org/promo/14-%204.png
Situp workout - http://glassfit.org/promo/glassfit-proto-situp.png
Taking a break - http://glassfit.org/promo/glassfit-proto-rest.png
Heart Rate/Stats (*mockup)- http://glassfit.org/promo/glassfit-proto-hr.png
Pushup workout - http://glassfit.org/promo/glassfit-proto-pushup.png
Tricep workout - http://glassfit.org/promo/glassfit-proto-tri-kicks.png
Pullup workout - http://glassfit.org/promo/glassfit-proto-pullup.png
Share achievements to G+ (future feature) - http://glassfit.org/promo/glassfit-proto-gplus-appactivity.png

Regarding TaskQueues on Glass

• https://gist.github.com/Scarygami/5539534

From G+ conversation with other glass devs

• https://github.com/Scarygami/mirror-api/blob/master/examples/colours-of-the-world/tasks.py then does all the processing and card creation "in the background".
• https://github.com/Scarygami/mirror-api/blob/master/examples/colours-of-the-world/notify.py just checks the validity of the notification and returns a 200 after sending the important information to a task for processing.

Regarding allowed HTML tags

Allowed HTML elements: Use these elements in your timeline cards.

Headers: h1, h2, h3, h4, h5, h6
Images: img
Lists: li, ol, ul
HTML5 semantic: article, aside, details, figure, figcaption, footer, header, nav, section, summary, time
Structural: blockquote, br, div, hr, p, span
Style: b, big, center, em, i, u, s, small, strike, strong, style, sub, sup
Tables: table, tbody, td, tfoot, th, thead, tr

Blocked HTML elements: These elements, and their contents, are removed from html payloads.

Document headers: head, title
Embeds: audio, embed, object, source, video
Frames: frame, frameset
Scripting: applet, script

Other elements: Any elements not listed above are removed, but their contents are preserved.

our service keeps loading the old Rest.json payload. Look at code, then logs you'll notice the weirdness. Do you know what might be causing it?

Just creating this issue to brainstorm some ideas.

• My googleapi credentials for any project cannot be used since my account hasn't been vetted to access the mirror api.
• Playground is very limited. It's not clear whether I can interact it with using a python gae app.

We can look into:

• keep banging on playground
• somehow sharing your credentials with me safely. Actually having the glass device doesn't seem to be that important if I can see cards in any browser.
• Somebody put in a lot of work into emulating the mirror api over here: https://github.com/Scarygami/mirror-api
  not sure if this is worth pursuing however.

See if this is more useful or at least can be useful for our dev needs https://github.com/jasonsalas/Glass-echo-service/blob/master/main.py

Something to think about when we go into post-prototype development
Patch https://developers.google.com/glass/performance#patch
{
"title": "New title"
}

for better performance when there's no need to resend uneeded data

I think I may have found something that may help check out the deliveryTime property https://developers.google.com/glass/v1/reference/timeline/insert#notification.deliveryTime

Other methods discussed:
taskqueue/worker
...

Google hasn't really thought through how notifications/subscriptions can be tested in the local environment. Looks like we have to resort to ugly workarounds like:

http://stackoverflow.com/questions/16907280/how-to-test-mirror-api-subscriptions

That said, I did get subscriptions calls to be successful but it seems like clicking in the glass playground will generate a notification that I will have to manually curl into local dev server every time.

Immediate need: Explore if the built in Share target to see how we can share a snapshot of finish card.

Our direction with GlassFit user profiles/acheivements (feel free to add/edit/amend)
Ability to share user workout stats via Google+ interactive posts (see: https://developers.google.com/+/web/share/interactive):

Google+ Profile Photo/Name
Name of Workout
Difficulty
Workout Time
Total workout time
Calories burned
Background Image

Note that while you work on these backend requests, I'm going to start working on a user frontend so that when the interactive post is shared viewers land on a public profile for the user.

Right now it's a mess. The main issue is to combine our own notification handlers with the existing handlers from the the quickstart project.

It's considered to be bad practice to include images (or any binary files) in a git repo.
We should probably host the files elsewhere or have someone deploy them to GAE manually.

Worst case I can host them on my vps which has a static IP for development only.

they are eating up glassfit's subscribtions.

I'm trying to use the correct datetime format here but google complains about a bad request.

See glassfitworkout.py:47

Right now its quickstart but it should be something else. We only have quickstart in the code for now since its useful to learn from.