3 ms·

I'm a HTML5 game dev so not really positioned to comment on the main story, but I did try out the Big Picture browser: Mozilla/5.0 (Windows; U; Windows NT 6.1;

I'm a HTML5 game dev so not really positioned to comment on the main story, but I did try out the Big Picture browser: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; Valve Steam Tenfoot/2095; ) AppleWebKit/535.15 (KHTML, like Gecko) Chrome/18.0.989.0 Safari/535.11 So, Chrome 18. What is it with Chrome 18 given Chrome for Android is also stuck on that version? Maybe coincidence and slow release cycles... (Also, Tenfoot? Hmm) I also tried playing a HTML5 game with it, which could be awesome with gamepad support. It seemed to freeze the browser and kept playing sounds in a loop, even after I had exited Steam... had to reboot to get rid of it. Guess it needs some work.

54mf 14y ago
Don't get too hyped by "tenfoot": http://en.wikipedia.org/wiki/10-foot_user_interface http://en.wikipedia.org/wiki/10-foot_user_interface Just a clever reference to the UI paradigm.
xxbondsxx 14y ago
Re: Tenfoot, it's apparently a term used to describe TV-sized GUI's: http://en.wikipedia.org/wiki/10-foot_user_interface http://en.wikipedia.org/wiki/10-foot_user_interface Imagine a responsive web design that goes from 10-foot all the way down to mobile; now that would be impressive!
- Already__Taken 14y ago
  That would be easy the hard part is solving the responsive image problem. How can we know what quality image to send to a device? The problems are shifting from display/device types to network types. Great you've got a 1080p phone but we can't shove down our retina quality images on 3g. Nor would you want use to use your battery life for that.
mwill 14y ago
To add to the ten foot comments, since big picture hit the steam beta, there's been files and directories floating around in the steam install folder called tenfoot, so it is indeed just the internal name for big picture.
kevingadd 14y ago
Steam (and by extension, Big Picture) uses LIBCEF to embed Chromium. As of April 26, the newest supported build of Chrome for LIBCEF was 18: http://code.google.com/p/chromiumembedded/source/detail?r=607 http://code.google.com/p/chromiumembedded/source/detail?r=60... While they now support newer versions of Chromium (http://code.google.com/p/chromiumembedded/wiki/BranchesAndBuilding http://code.google.com/p/chromiumembedded/wiki/BranchesAndBu...) it is likely that Valve either didn't have the time to test everything against a new Chromium revision, or didn't want to take the risk. Every Chromium commit historically has a very high risk of breaking embedding use cases (I used to try and track Chromium for my own embedding purposes before finally giving up because it broke constantly). As far as Chrome on Android goes, I have no idea. In Google's case you would expect they would have the resources to keep up with changes to their own codebases.

54mf 14y ago

Don't get too hyped by "tenfoot": http://en.wikipedia.org/wiki/10-foot_user_interface http://en.wikipedia.org/wiki/10-foot_user_interface Just a clever reference to the UI paradigm.

xxbondsxx 14y ago

Re: Tenfoot, it's apparently a term used to describe TV-sized GUI's: http://en.wikipedia.org/wiki/10-foot_user_interface http://en.wikipedia.org/wiki/10-foot_user_interface Imagine a responsive web design that goes from 10-foot all the way down to mobile; now that would be impressive!

Already__Taken 14y ago
That would be easy the hard part is solving the responsive image problem. How can we know what quality image to send to a device? The problems are shifting from display/device types to network types. Great you've got a 1080p phone but we can't shove down our retina quality images on 3g. Nor would you want use to use your battery life for that.

mwill 14y ago

To add to the ten foot comments, since big picture hit the steam beta, there's been files and directories floating around in the steam install folder called tenfoot, so it is indeed just the internal name for big picture.

kevingadd 14y ago

Steam (and by extension, Big Picture) uses LIBCEF to embed Chromium. As of April 26, the newest supported build of Chrome for LIBCEF was 18: http://code.google.com/p/chromiumembedded/source/detail?r=607 http://code.google.com/p/chromiumembedded/source/detail?r=60... While they now support newer versions of Chromium (http://code.google.com/p/chromiumembedded/wiki/BranchesAndBuilding http://code.google.com/p/chromiumembedded/wiki/BranchesAndBu...) it is likely that Valve either didn't have the time to test everything against a new Chromium revision, or didn't want to take the risk. Every Chromium commit historically has a very high risk of breaking embedding use cases (I used to try and track Chromium for my own embedding purposes before finally giving up because it broke constantly). As far as Chrome on Android goes, I have no idea. In Google's case you would expect they would have the resources to keep up with changes to their own codebases.