View allAll Photos Tagged html5
This is a desktop supporting HTML and branding MyModernWeb.com as a company who stands behind HTML5 completely.
scale3d() and .style.zoom tricks to make content fit a wide range of viewport sizes. It actually works pretty well.
See also, Building Flickr's new Hybrid Signed-out Homepage on the Flickr Code Blog.
"Timeline" view.
A few expensive image decodes and resize operations, but the page is quite smooth overall in terms of scroll performance.
Finally released as an experimental feature, a month or two in development: HTML5 Audio() support for my JavaScript Sound API, with SoundManager V2.96a.20100520. (Progress from the prior dev version.)
This is the first time this API has had the capability to be 100% Flash-free, and I have to say, it's a rather liberating thought. It's shown here working on the iPad; it may be playback or wifi that's a bit sluggish to get going. The Palm Pre also works, which is a good indication of where mobile devices are going with this stuff.
There are some bugs and inconsistencies in support across differing browsers and platforms, but I expect those to be ironed out over time. This is part of the reason why the feature is experimental, not to mention the fact that user testing in the real world is part of where I get some of the most, and best, bugs found and fixed. ;)
Also on the Githubs:
with HTML5 for Flash-less audio!
In the web app, select the gear icon at the top right and select Labs.
Since I took this screenshot they have added Chromecast Fireplace Visualizer.
I noticed in Safari that I was getting some pretty severe jank (lag) when firing the machine gun in this web-based game prototype, so I started digging.
It wasn't DOM manipulation, className changes or node removal - turned out it was cloned audio resources being freed from memory after playing, and garbage allocation interrupting the game animation pretty severely in Safari (and Webkit nightly) every so often.
Using standard HTML5 audio, you can't do "multi-shot" - each audio object is single-fire and monophonic. Thus when a machine gun fires, SM2 clones the Audio() instance to make a new object that can play independently, with its own timeline and events.
These screenshots are from Chrome DevTools. Interestingly, Chrome was less-affected by this issue despite having notably-larger GC events as well. I'm not sure how long Safari was taking, but it felt like up to 1 second in Safari 6 in some cases.
In the first case, the GC event is for 9.3 MB and takes 25 msec - blowing the 16 msec / 60fps ideal framerate budget.
In the case where audio is muted and inactive, the first GC event to happen is for 3.6 MB and takes 1.9 msec.
As Mythbusters' Adam Savage would say, "Well there's your problem!"
The solution to this is to simply create a pool of sound objects and rotate through them, if the play() rate is such that the sounds would need to overlap. While this will consume more memory (if not shared/reused by the browser) up front, it should prevent a lot of dynamic memory allocation and resulting expensive garbage collection events.
In fact, most sounds (like machine gun fire) are short enough that multi-shot is not even needed.
Maybe those guys were right about writing JavaScript more like C++ after all, static and all that.
To commemorate the fact that HTML5 has been renamed HTML and the HTML spec can now be considered a ‘living standard’
Another example from Ernest Delgado, a developer at Google who created this impressive example of image manipulation in a canvas. Note that canvas JavaScript objects can be nested.
www.ernestdelgado.com/public-tests/canvasphoto/demo/canva...
It’s been over 20 years since Tim Berners-Lee and Robert Cailliau specified HTML, which became the standard markup language used to build the Internet. Ever since then, the HTML development community and developers now at Trendism have begged for improvements to this language, but this cry was m...
The Sheridan Interactive Multimedia Open House was a success. The pictures are also on Facebook - so tag yourselves if you want:
imm.sheridanc.on.ca/go/openhouse2012pics
Thank you for all who attended (or attended in spirit).
Special thanks to:
Studio Huddle (www.elevatorartlab.com) for a super location (very hot!)
Demi Kandylis (splitelement.com) for friendship (and the tables!)
Open House Committee (Carla (venue, food), Caitlyn, Lindsay (org, site))
Loading Sub Committee (Diana+, Carla, Yohei, Jack, Mani, Joel, Zain, Yatharth, Westley)
Poster Sub Committee (Jack, Kevin)
Teachers (Andrew, David, Dan)
Sheridan Institute - and thanks to the President (Jeff Zabudsky) for the visit!
Tech folks (Bob and Robert - and the Mac folks for the cart)
Of course the industry for their support
And a very special thanks to the Alumni of IMM for keeping the family together.
The graduate portfolios are available from the invite page:
imm.sheridanc.on.ca/openhouse/2012/
Our IMM blog continues to report on exciting events for IMM:
interactivemultimedia.wordpress.com/
We are currently accepting applications for September.
imm.sheridanc.on.ca (new site, one day!)
All the best,
Dan Zen
For about two decades, Adobe Flash was the only means of creating motion graphics for digital signage. However, this has changed in the past few years due to the introduction of HTML5. One advantage of using HTML5 digital signage is that it offers creators a universal platform. It can run ads...
digitalsignagepress.com/blog/html5-digital-signage-solution/
Screenshots from the new Yahoo Mail, HTML5 versions for mobile browsers on tablets and smartphones, like the the iPad or iPhone.
This photo is licensed under a Creative Commons license. Please credit Rob Larsen with a link to Drunkenfist.com, if you use this photo anywhere. Thanks.
HTML5 APIs Will Change the Web… And Your Designs
Jen Simmons, Designer
For the last twenty years, we have been creating websites from inside of a certain set of constraints—inside the limits of the technology that runs the web. We became so used to those constraints, we stopped thinking about them. But HTML5 changes many of these limits. The new HTML specs define a lot more than markup—there’s a lot about databases, communication protocols, and how websites & browsers talk to each other. It’s radical stuff that will redefine the creature formerly known as the “web page.” In this talk, Jen will walk us through the new possibilities created by HTML5’s APIs and how they will shape the web of the future.
Murray Maloney hosted a lunch BOF around the theme of W3C's HTML5 work,
tooling and community. These are my notes from the discussion when I asked Ian Hickson what would help make his HTML5-editing life easier; photo by TimBL.
Corrections, clarifications from participants are welcomed via Flickr comments or email to danbri@danbri.org (ideally cc:'ing the public www-archive@w3.org archiving list).
Transcribing and slightly augmenting my notes from TimBL's photo of my lunch scribbles:
[[
Editors, more of them.
(there is a list of desired talents somewhere, from Ian).
Testing, QA infrastructure
(discussion of when this becomes most useful/urgent)
Tooling:
track every email, figure out its category, section, related posts, issues, links, ... feedback, ...
Volunteers to help at checkin point, ... documenting rational, links to wiki and issue tracker(s), when the document goes in. Or even when a change was
*not* made (and why).
(TimBL talked about issue/release tracking in Tabulator)
Mailing list discussion: Ian noted that things are split fairly evenly between the W3C HTML list and the WHATWG list. Ian tracks both without preference. There are slightly different cultures and expectations across each. The core HTML5 people tend to now initiate things on the W3C list.
'tool for +1-ing?' --dbaron
Ian: WHATWG has voting on whatwg / issues
Ian: also I'd like a more flexible license on the doc; people want (a) to be
able to copy from the spec into code (b) allow risk of a fork. The possibility
of this happening keeps people focussed. Re license, DanC has action to follow this up, and expressed some optimism.
]]