Archive for the ‘HTML5’ Category
The pure HTML5/CSS skin ensures a consistent look between HTML5 browsers, and easy custom skinning if you want to give it a specific look, or brand it with your own colors. See the skins page for examples of custom skins.
The focus is on simple usage (all settings are optional), attractive looks and interactive features like zooming and mouse tracking.
Read the rest of this entry »
<canvas> implementations which we will see later in this tutorial.
<canvas> was first introduced by Apple for the Mac OS X Dashboard and later implemented in Safari and Google Chrome. Gecko 1.8-based browsers, such as Firefox 1.5, also support this element. The
<canvas> element is part of the WhatWG Web applications 1.0 specification also known as HTML 5.
I list some some place to find comprehensive tutorials samples on html5 canvas.
1. https://developer.mozilla.org/en/Canvas_tutorial. In this tutorial you will find topics on
- Basic usage
- Drawing shapes
- Using images
- Applying styles and colors
- Basic animations
Sencha Touch is the first HTML5 mobile web app framework.Sencha Touch allows you to develop mobile web apps that look and feel native on iPhone and Android touch devices.If you are building a complex enterprise application with a lot of visual interactions, Sencha Touch may be the best choice. it is heavily documented, with a strong professional team providing support.
Read the rest of this entry »
Ample SDK consists of a Ample Runtime (or Core), User Interface Markup Language implementations and a set of plugins. Ample Runtime implements DOM (Level 3), XML languages, objects facilitating work with XML, XSL-T, and a whole range of UI services. Every UI Markup Language implementation is included separately depending on your needs and specifics of the User Interface you build. Have a closer look at the Ample SDK Technologies.
What’s an HTML5 Video Player?
Why use an HTML5 Video Player?
Knowing that HTML5 browsers have a built in player, you might wonder why you’d need an additional library like VideoJS at all. There’s actually a number of reasons.
- Browser Version Compatibility. As the specification grows and changes, browser developers add new functionality to their players, and may even change the way an existing functionality is used. An example of this is when the spec changed from
preload, as the video tag attribute used to preload the video before the user hits play. Older versions of Firefox still use
autobuffer, while newer versions require
preload. VideoJS fixes this by checking for either attribute and triggering the one the browser needs.
- Additional Features. Not all built-in players support all the features you might expect from a video player, like volume control and fullscreen mode. Many HTML5 browsers, including older versions of webkit, don’t support Fullscreen Mode, so an HTML5 Video Player can simulate Fullscreen Mode by filling the browser window with the video.
- Consistent Design & Controls. Each browser has a different look & and feel to their built-in controls. If you want to present the same controls to every visitor you need an HTML5 Video Player.
- Cross Browser compatibility fixes. Sometimes a feature of one browser breaks another. For instance, if you only include one video source for your video tag, and the browser doesn’t support it, it won’t fallback to the Flash player like you might expect. It will just stop and your video won’t play. VideoJS is able to get around this by forcing the browser to fallback to Flash. This is great if you want to only encode your video to the H.264 format (Safari, Chrome, iPad, iPhone, and Flash).