Expose heading in the locations collection

[GoogleCodeExporter]

1) would be useful to get heading data in the location resource

2) would be useful to have a card rotate according to the users heading just 
like the map rotates and the easter egg rotates.

Original issue reported on code.google.com by dick.ha...@gmail.com on 26 Apr 2013 at 12:21

[GoogleCodeExporter]

Original comment by mimm...@google.com on 28 Apr 2013 at 9:49

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by mimm...@google.com on 4 May 2013 at 4:48

• Changed title: Expose heading in the locations collection

[GoogleCodeExporter]

Part 1 (compass bearing) is the piece I'm looking for, as it would help in a 
number of applications where context  within a location may depend on what 
direction the user is facing.

Original comment by trac...@gmail.com on 11 Jul 2013 at 12:52

[GoogleCodeExporter]

This seems to be a  key piece of missing functionality to really get developers 
excited about developing for glass. I know you are using this within the maps 
now, why not expose the API so developers can start to get creative with this 
API?

Original comment by WDPR...@gmail.com on 12 Jul 2013 at 3:56

[GoogleCodeExporter]

+1 on compass bearing.  Also would be very helpful to get head-tilt (like what 
is used for the head-wake feature).

Original comment by cdha...@google.com on 12 Jul 2013 at 4:01

[GoogleCodeExporter]

I'm trying hard to think of Mirror API use cases for this one, but I can't come 
up with any,  If you have some concrete use cases for this data on the Mirror 
API, please update this issue with it.

Real time use cases make a lot of sense, though, so I'm moving this to the GDK 
component and marking it as RevisitLater, since it already works for 
side-loaded APKs and we expect it to continue working for GDK.

Original comment by mimm...@google.com on 22 Jul 2013 at 8:55

• Changed state: RevisitLater
• Added labels: Component-GDK
• Removed labels: Component-Mirror-API

[GoogleCodeExporter]

The Locations Collection might not be the best place. Having a hook int he HTML 
sent to phone so that the image rotates as the user changes heading would be 
super useful (ie, you send the user a map of where they are which rotates as 
they move) This would not require a native app, just markup in the HTML.

Original comment by dick.ha...@gmail.com on 22 Jul 2013 at 9:01

[GoogleCodeExporter]

Information about where somebody was standing, and where they were looking, 
when they took a photo, for example, is my use case.  But, my idea has shifted 
more towards a GDK app, anyway.  It's much more powerful as a real-time 
application.

Original comment by heizu...@gmail.com on 22 Jul 2013 at 9:36

[GoogleCodeExporter]

@heizusan: Thanks for circling back.

@dick: Understood. It sounds like you're more interested in a photosphere 
viewer than in the raw data from the sensor. Does this sound correct?

Original comment by mimm...@google.com on 23 Jul 2013 at 12:49

[GoogleCodeExporter]

yes, thanks for following up

Any plans on letting JS run in the HTML in a card? If so, then getting
events on the heading would be super useful to let the card adjust. I
realize this might be more AR like than you are attending, but I can
imagine numerous use cases where it would be useful to show a floor plate
map that adjusts as you rotate. Allowing the HTML in the card to be dynamic
based on a heading event would be nice.

Original comment by dick.ha...@gmail.com on 23 Jul 2013 at 1:50

[GoogleCodeExporter]

@dick: JavaScript on cards? Probably not any time soon. GDK is our solution to 
that kind of use case.

Original comment by mimm...@google.com on 23 Jul 2013 at 1:52

[GoogleCodeExporter]

Issue 238 has been merged into this issue.

Original comment by ala...@google.com on 11 Nov 2013 at 4:36

[GoogleCodeExporter]

Issue 239 has been merged into this issue.

Original comment by ala...@google.com on 11 Nov 2013 at 4:36