On Dec 20, 2006, at 2:20 PM, Justin Gallardo wrote:

> Hey Folks,
> I have recently started to work on making a helix player work with  
> the helix dna client. One of the large tasks is designing and  
> implementing a GUI that not only works, but satisfies OLPC's unique  
> HIG[1]. I started working on a few mockups for the player, and  
> thought I would get the communities opinion on things.
>
> You can find the first mockup at http://staff.osuosl.org/~jirwin/ 
> helixMockup2.png. If you feel so inclined, I also posted a SVG of  
> the mockup at http://staff.osuosl.org/~jirwin/helixMockup.svg.
>
> Any input would be greatly appreciated. Thanks in advance

Hi Justin.

First, did you resolve all the python questions you had? I am really  
interested
in any application of this work to a general Python interface (shim  
layer) over
the Helix media engine.

Second, I will have to read up on the OLPC HIG, but I have some  
general observations
and questions:


o Is the player seekable via clicking on the time bar?
o Are those arrows fast forward/reverse or skip track?
o Do you envision a full screen mode where the controls are not visible?
o does the play button turn into a pause button?
o do you envision the use of the hardware volume key exclusively.
o The Helix media engine also has the notion of a TiVo like rewind
   buffer. This provides time shifting capabilities for live and on
   demand streams. We call it Super Buffer. I think for this first
   player we don't need to worry about it though. This functionality
   can take up a lot of client side resources. But, we should keep it
   in mind for the future.

More later after I read the HIG.

--greg.


>
> [1] http://wiki.laptop.org/go/OLPC_Human_Interface_Guidelines
>
> -- 
> Justin Gallardo
> _______________________________________________
> Player-dev mailing list
> Player-dev at helixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/player-dev