Closed GoogleCodeExporter closed 9 years ago
Original comment by allev...@google.com
on 2 Dec 2013 at 5:09
Original comment by ala...@google.com
on 3 Dec 2013 at 12:17
So the typical way this is going to be used is when loading data for a card.
So you want to have a way to turn progress on and off based on the loading
status. I've tried the standard android progress:
requestWindowFeature(Window.FEATURE_PROGRESS);
setProgressBarIndeterminate(true);
setProgressBarVisibility(true);
However this appears to have no effect.
Original comment by johnarle...@gmail.com
on 19 Jan 2014 at 4:53
Also, the 0-100 progress indicator would be useful for building our own
confirmation cards.
Like Glass does with "Sending (swipe down to cancel)".
Original comment by IamTheFij
on 21 Jan 2014 at 7:32
I've extracted Google Glass Progress Bar from GlassHome.apk and created a
library project based on that: https://github.com/pif/glass-progress-bar
http://i.stack.imgur.com/aQeD6.gif
- supports indeterminate
- supports default progress
Usage is described in README in the repository.
That's for exploratory purposes only. Not for any production apps. Everyone is
still waiting for a full-featured set of Glass Views.
Original comment by pifos...@gmail.com
on 26 Jan 2014 at 9:42
Attachments:
I want to explicitly request that any GDK implementation of a progress bar be
compatible with LiveCards. This isn't a given, because low-frequency LiveCards
use RemoteViews, and high-frequency use a Surface - neither of which is
compatible with a simple widget like the SliderView so helpfully extracted in
#5 above.
Ideally, a progress indicator would be something that a GDK app could invoke
directly on a LiveCard (which would then render the progress bar itself),
rather than an add-on component like this. Similar to how the Activity class
has the setProgress* methods in the conventional Android SDK.
Original comment by sterling...@googlemail.com
on 4 Apr 2014 at 10:20
This has been fixed with XE22:
https://developers.google.com/glass/develop/gdk/slider
Original comment by ala...@google.com
on 4 Nov 2014 at 1:41
Original issue reported on code.google.com by
gila...@gmail.com
on 28 Nov 2013 at 9:17