background preloader

HTML5

Facebook Twitter

Google logo gets bouncy for birthday | Technology. For its 12th birthday, the Google logo shows off what programmers can do with a few lines of code, in the latest of its long line of attention-getting "doodles". The logo on Google's homepage is made out of a set of bouncing "balls" that swirl around the page in modern browsers such as its own Chrome, Firefox, Apple's Safari and some versions of Opera – but not in older versions of Microsoft's Internet Explorer (though the most recent version, IE8, does).

Google officially opened its doors – or rather door – 12 years ago in Menlo Park California. As the company history explains: "On September 7, 1998, Google Inc. opened its door in Menlo Park, California. The door came with a remote control, as it was attached to the garage of a friend who sublet space to the new corporation's staff of three. The office offered several big advantages, including a washer and dryer and a hot tub. "Already Google.com, still in beta, was answering 10,000 search queries each day. Use of Ogg formats in HTML5. Motivation[edit] Users affiliated with the free software movement claimed the following advantages: The potential for universal adoption of Theora and Vorbis, no matter the computer or the user, would ease "codec hell" by eliminating an unnecessary amount of codecs required to view and publish videos to a select few.

[citation needed]Browser plugins needed to accommodate the many different codecs would then become a thing of the past: Browsers could handle the playback of Theora and Vorbis and allow the user to customize the manner in which that was done.Bugs and exploits in obsolete versions of those plugins would affect the user less, as they are phased out; the loss of multiple attack vectors would happen once browser plugins were ultimately removed. CTO at Opera Software, Håkon Wium Lie explained in a Google tech talk entitled "The <video> element" the proposal of Theora as the video format for HTML5:[2] Support[edit] Opposition[edit] Recommendation retracted[edit] Adoption[edit] HTML 5: Ogg Theora Vs H.264 In The Battle For A Web Video Standa.

With YouTube and other video sites serving up over a billion streams a day, it’s beyond contention that web-based video is not only mainstream, but has become fundamental to the web experience. Why, then, is a huge majority of web video in a wrapped in a proprietary Flash candy coating — essentially making Adobe the gatekeeper of video content? It’s worked okay so far, but it’s hardly a fertile ground for innovation, not to mention the fact that Flash is a real dog on OS X and any kind mobile browser (if it’s even supported).

The next iteration of HTML standards is poised to introduce a <video> standard, putting moving images in the same natively-viewed category as images and text. Unfortunate, it seems that the powers that be (heavyweights Apple, Mozilla, Microsoft, Google, &c.) can’t agree on what format the <video> tag will indicate. The battle is between the reigning champ, H.264, and the open-source alternative, Ogg Theora. Whatever, let the format geeks work it out, right? You Too Can Experience HTML5 on YouTube - PCWorld.

Adobe Flash killer

Introduction to HTML 5. HTML 5 Tutorial. Will HTML5 Have an Impact on Adobe? - With the recent announcements that YouTube (GOOG) and Vimeo are both releasing HTML5-based video players, one has to wonder about the impact of those moves on Adobe (ADBE). Adobe’s Flash had been (and is) THE standard for delivering multimedia content over the web, capturing something like 99% of internet users. HTML5 allows many Flash-like animations/videos/experiences without the need for a seperate plugin or buffering (that’s right – skip to a different point in that YouTube video without waiting for it to load!).

Adobe doesn’t derive much revenue from Flash – so this isn’t going to crimp their cashflow necessarily – but it is a major part of their broader brand recognition. (For the curious, Flash and other platforms generate about 6% of Adobe’s revenue, but half of that comes from Mobile solutions that likely don’t include Flash.

Creative software is the bulk of the revenue stream, forming about 60% of the total.). Receive future articles by this author via email: (15 followers) New! Sketchpad in HTML5: Why Flash is no longer relevant. HTML5. HTML5 is a markup language used for structuring and presenting content for the World Wide Web and a core technology of the Internet. It is the fifth revision of the HTML standard (created in 1990 and standardized as HTML 4 as of 1997)[2] and, as of December 2012[update], is a candidate recommendation of the World Wide Web Consortium (W3C).[3] Its core aims have been to improve the language with support for the latest multimedia while keeping it easily readable by humans and consistently understood by computers and devices (web browsers, parsers, etc.).

HTML5 is intended to subsume not only HTML 4, but also XHTML 1 and DOM Level 2 HTML.[2] History[edit] The Web Hypertext Application Technology Working Group (WHATWG) began work on the new standard in 2004. While HTML5 is often compared to Flash, the two technologies are very different. Standardization process[edit] 2008 – First Public Working Draft 2011 – Last Call 2012 – Candidate Recommendation Plan 2014[edit] Core HTML specification. Elements and Attributes. HTML 5. B.3 Acknowledgments This section is non-normative. At the time of publication, the members of the RDF Web Applications Working Group were: Ivan Herman (staff contact), Shane McCarron, Gregg Kellogg, Niklas Lindström, Knud Möller, Steven Pemberton, Manu Sporny (chair), Stéphane Corlosquet and Thomas Steiner.

At the time of publication, the members of the HTML Working Group were: Canvas element. History[edit] Usage[edit] Canvas consists of a drawable region defined in HTML code with height and width attributes. JavaScript code may access the area through a full set of drawing functions similar to those of other common 2D APIs, thus allowing for dynamically generated graphics. Some anticipated uses of canvas include building graphs, animations, games, and image composition.

Example[edit] The following code creates a Canvas element in an HTML page: <canvas id="example" width="200" height="200"> This text is displayed if your browser does not support HTML5 Canvas. Using JavaScript, you can draw on the canvas: var example = document.getElementById('example');var context = example.getContext('2d'); context.fillStyle = 'red'; context.fillRect(30, 30, 50, 50); This code draws a red rectangle on the screen.

Canvas Element Size versus Drawing Surface Size[edit] By default, both the canvas element’s size and the size of its drawing surface is 300 screen pixels wide and 150 screen pixels high. HTML 5 Demos and Examples. HTML Drag and Drop. HTML5 drag and drop in Firefox 3.5 Oh hey, look! It's another blog post—and this one is cross-posted on hacks.mozilla.com.

I won't say this is the start of a renewed blogging habit, but let's see what happens. Drag and drop is one of the most fundamental interactions afforded by graphical user interfaces. In one gesture, it allows users to pair the selection of an object with the execution of an action, often including a second object in the operation. It's a simple yet powerful UI concept used to support copying, list reordering, deletion (ala the Trash / Recycle Bin), and even the creation of link relationships.

Since it's so fundamental, offering drag and drop in web applications has been a no-brainer ever since browsers first offered mouse events in DHTML. Of course, that doesn't prevent most modern JavaScript frameworks from abstracting away most of the problems and throwing in some flourishes while they're at it. The New Drag and Drop Events dragstart drag dragenter dragover dragleave all.