View allAll Photos Tagged html5
This is a desktop supporting HTML and branding MyModernWeb.com as a company who stands behind HTML5 completely.
This video shows the synchronization of video playback with JS/CSS/HTML-driven effects. As the video plays and its currentTime property reaches given values, JS functions are fired that do the work of applying overlays with filtered background images.
See also, Building Flickr's new Hybrid Signed-out Homepage on the Flickr Code Blog.
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.
... to code!
And HTML5 + CSS3 to boot.
RISD doesn't require scripting, code, or software design. Earth to Maeda. It's the real world calling.
First thing out of Dawa's mouth:
"This is exciting!"
Second thing:
"OMG, Lorem Ipsum in the tutorial. Yuk.
And he even recommended an auto-content filling service. Double gross."
Go Dawa!!
"Timeline" view.
A few expensive image decodes and resize operations, but the page is quite smooth overall in terms of scroll performance.
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.
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...
To commemorate the fact that HTML5 has been renamed HTML and the HTML spec can now be considered a ‘living standard’
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/
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:
Designing iPad Apps Monday, 02/14/2011
Jennifer Brook (The New York Times), William Couch (USA TODAY), Craig Mod (PREPOST / Flipboard)
The iPad and its emerging entourage of Android tablets have introduced a new style of computing, confronting designers with new challenges. Explore practical techniques and eye-opening gotchas of tablet interface design, all grounded in the ergonomics, context, psychology, and nascent culture of these new devices.
____________________________________________________________________________________
Jennifer Brook, Information Architect for the New York Times
The challenge of building the NYTimes iPad app: How do we design something new that feels familiar? Designed for the device, but maintained typography and branding.
Remember that apps are distinct from web and print.
Great apps:
Understand the platform
Start small and improve over time
Require collaboration to build
Crafted crafted with the human eye and touch in mind
Killer apps do 1-3 things well. They are specific, useful, and easy to use.
A complex system that works is invariably found to have evolved from a simple system that worked. The inverse proposition also appears to be true: A complex system designed from scratch never works and cannot be made to work. You have to start over, beginning with a working simple system.
—p. 71
The waterfall model of development is like a factory and it ends up being too heavy. You need a lighter-weight process to develop simple apps.
When developing, you should put your work on a device as soon as possible. Wireframes and designs should go on a device and stakeholders should view every stage on the device.
Apps should be useful tools for human beings.
William Couch, USA Today | Designing for Distraction
Device | Interaction | Content
Consider the device
-> Device Environment
indoor/outdoor
stationary/moving
focused/distracted
Consider an object's habit field
Windows Phone "Be Here Now"
Kindle is "comfortable in the world" (Tom Armitage)
-> Device Culture
Platforms as cultures
population | customs | governance | styles | beliefs
Consider physical interactions
Device interaction is touch, there's no intermediary
Consider the content
You should have a content API that feeds where you publish
web | mobile | tablets | TV | print
Content can be long form and text online can be a rich experience
Craig Mod, Flipboard | Content Formats & Tablets
HTML5 is the future of books and content
Screens will be paper density (300/dpi)
Great typography will prevail
Ownership is dissolving
The value of marginalia is increasing
The physical is not going away
Skeuomorphism is manifest in the publishing ethos. We're making apps to look like physical books.
When a magazine is replicated on an iPad:
How do you let the user know what they can and can't touch? (Bullet points, touch targets, something more subtle?)
The iPad interaction model isn't fully fleshed out.
As an app designer, you need to teach the user.
Types of Content
Formless (epub) | Definite/semantic/physical (PDF, epub) | Interactive/non-linear HTML5, epub3
ePub doesn't have to be ugly (Virginia Quarterly Review and A Book Apart are good examples).
ePub3 is basically a wrapper for HTML5/CSS3 (so it's very flexible/capable)
Magazine apps can use PDF, that's better than using images, like was previously done on the web and is being done now on apps. PDF is better because it's real text (machine-readable, resizable, copyable).
iOS/Android Native is good for interactive content, because it gives you extreme control over a non-linear flow.
Publishers should make compelling "steal-worthy" content.
This fascinating 10-second clip (sarcasm) shows an example of SoundManager 2 + HTML5 audio stress test pages running side-by-side on an iPad and iPhone. I'm trying to figure out when and what may cause the dreaded "cannot play movie" error dialog sometimes shown.
The process roughly involves new Audio().src = 'foo.mp3?rnd='+Math.random() being assigned, and then at onfinish(), the process is repeated until the browser (or device) barfs with "cannot play movie" after running out of memory(?) or other resources.
The buttons are provided as a way of starting the sound create-play loop again, should it stop for some reason. On iOS4, sound playback must be user initiated and if new sounds are to be created and/or played, they must be chained via the prior sound's finish event.
The point is to try to determine what kind of limits (RAM, number of objects, amount of requests/loads) are eventually being hit and causing the strange error.
The iPad made it to 135 plays in this case, and the iPhone (a 3GS with iOS 4.1) has finally appeared to have crapped out (albeit the sound stopped, but no error dialog) at 279. Starting playback again via tapping a button gave out at 291, no dialog.
With the iPad, once failed, subsequent reloads of the page immediately fail to play audio and show the modal error dialog. The iPhone seemed to clean up after itself and was responsive after a reload of the page.
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.
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.
]]
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.
"For many out there HTML5 is nothing more than an acronym to use during some geek conversation in order to show off some pretending modern knowledge. This is probably what happened here as well at the very beginning of our recent web challenge: "...come on guys, let's buzz!!!"
Mobile HTML5 Development is extremely challenging and exciting but it can also be frustrating if we don't keep in mind problems and solutions never faced in the Desktop Web. Dealing with standards not complete yet, fragmented builds of the same product, facing both weakness and potentials of these portable devices, this is just a slice of what we are doing on daily basis in Nokia R&D.
This talk is about main technical problems, solutions, and goals achieved while we were building our online Maps application and we hope to inspire and give useful tips to anybody that is dealing with building HTML5 apps for iOS and Android."