Hello HTML5 2/19/2010 04:13:00 PMPosted by Ian Fette, Gears Team If you've wondered why there haven't been many Gears releases or posts on the Gears blog lately, it's because we've shifted our effort towards bringing all of the Gears capabilities into web standards like HTML5. We're not there yet, but we are getting closer. In January we shipped a new version of Google Chrome that natively supports a Database API similar to the Gears database API, workers (both local and shared, equivalent to workers and cross-origin wokers in Gears), and also new APIs like Local Storage and Web Sockets. Other facets of Gears, such as the LocalServer API and Geolocation, are also represented by similar APIs in new standards and will be included in Google Chrome shortly. We realize there is not yet a simple, comprehensive way to take your Gears-enabled application and move it (and your entire userbase) over to a standards-based approach.
HTML5 sectioning elements, headings, and document outlines A subject I have returned to a couple of times is how to use headings to make good document outlines in HTML documents. See Headings and document structure conclusions for a summary of my reasoning. Recently I’ve been taking a closer look at how HTML5 changes the way document outlines are created. I’m not entirely sure that I have understood the specification fully, but if I have, I think the new outline algorithm requires you to think carefully when using the new sectioning elements (article, section, nav, and aside) if you also want a coherent document outline without untitled sections. The HTML 4.01 outline To explain what I mean, let’s look at some examples. <body><div id="header">Site title etc. That creates the following document outline (you can use the Web Developer extension to check document outlines): Article title Article sub-heading Article sub-sub-heading Sidebar heading Sidebar sub-heading Footer heading The HTML5 outline <body><header> Site title etc. Say what?
Web Socket Server Introduction I've been hearing about HTML5 for quite some time now, and I especially liked the idea of web sockets. Giving us the ability to send data directly to the user, instead of doing something like polling with AJAX requests seems like a very neat idea. So the other day, I decided that I would try to make a small server and test it out on my localhost. This screenshot is an example of how web sockets could be used (the code is in the attached zip file). Naturally, I started the development with a Google search; this however didn't really help much. Background The server is heavily based on sockets. Using the Code The code is organized into a couple of classes in a class library, which could be included as a project in your solution or compiled into an assembly. The following is an example of how you could start the server: var wss = new WebSocketServer(8181, " " wss.Start(); The constructor takes three arguments: WebSocketServer: So!
HTML5 input placeholder= via YUI) HTML5 Canvas Demos and Applications To Make You Say WOW Our today’s post is on HTML5 Canvas Applications and Demos. Being the last day of this calender year, we were bit skeptical on topic to choose. After thinking for quite a while we chose HTML5 Canvas Applications over others as we wanted to portray a different subject. In this post, you will be able to check the power of HTML5. The Most astonishing facet of HTML5 is the HTML5 canvas. Advertisement DeviantART muro The tool can be used as a stand-alone web application as well as a lightweight drawing tool for adding pictures to forum comments. More Info on DeviantART muro Super Mario Kart Play JavaScript Super Mario Kart Online. More Info on Super Mario Kart Canvas Cartoon Animation that’s as good as Flash This short animation is as good as Flash, this is surely to amaze you. More Info on Canvas Cartoon Animation that’s as good as Flash Asteroid Belt sample Introducing hardware accelerated canvas, video and audio. More Info on Asteroid Belt sample Bert’s Breakdown More Info on Bert’s Breakdown Fishtank
A JSON event-based convention for WebSockets @ Bamboo Blog HTML5 WebSockets are cool. Given a compliant server - and browser -, all you need to do is instantiate your socket object and start listening to server-pushed data. How awesome is that?! 1 socket.send( "Thank you, Mr. server!" Think about it for a moment. 1 // Incoming messages 2 socket.onmessage = function(evt){ 3 // We use jQuery because life's too short for raw DOM scripting 4 $('#messages').prepend( "<li>" + evt.data + "</li>" ); 5 } 6 7 // Send message to chat server 8 $('form').submit(function(){ 9 socket.send( $(this).find('input.message').val() ); 10 return false; 11 }); We get a message from the server, we add it to the page. SEND destination:/some/channel hello everybody ^@ It's got a command name, a destination header (a channel, chat room, topic, etc) and a body (the "^@" at the end means "end of the message"). See where I'm going with this? But who would want to do such a thing? We might as well use JSON. JSON is Javascript, Javascript is JSON. WTF just happened?! ...
2 Common infrastructure — HTML5 1 Introduction 1.1 Where does this specification fit? This specification defines a big part of the web platform, in lots of detail. Its place in the web platform specification stack relative to other specifications can be best summed up as follows: 1.2 Is this HTML5? This section is non-normative. In short: Yes. In more length: the term "HTML5" is widely used as a buzzword to refer to modern web technologies, many of which (though by no means all) are developed at the WHATWG. 1.3 Background HTML is the World Wide Web's core markup language. 1.4 Audience This specification is intended for authors of documents and scripts that use the features defined in this specification, implementers of tools that operate on pages that use the features defined in this specification, and individuals wishing to establish the correctness of documents or implementations with respect to the requirements of this specification. 1.5 Scope The scope of this specification is not to describe an entire operating system. .
HTML5-Handbuch - Webkompetenz Wenn Sie den Inhalt der Site diskutieren möchten - dies ist der leichteste Weg dies zu tun. Klicken Sie hier um den Inhalt der Seite zu ändern. Klicken Sie hier um auf das Ändern von einzelnen Sektionen hin- und herzuschalten (wenn möglich). Achten Sie auf die Überschriften ob daneben ein "Bearbeiten" Link erscheint. Inhalt hinzufügen ohne den ganzen Seiteninhalt zu editieren Prüfen Sie, wie Sie diese Seite sich in der Vergangenheit entwickelt hat. Betrachten und Verwalten von Datei-Anhängen für diese Seite. Einige nützliche Werkzeuge zum Verwalten Ihrer Site Ändern des Namens der Seite (auch URL Adresse, eventuell die Kategorie). Ansicht des Seiten-Quelltextes ohne Änderung. Ansicht /Einsetzen "Eltern" Seite (benutzt um "Breadcrumbs" und Layout-Struktur zu erstellen). Benachrichtigen Sie die Administratoren, wenn Sie anstößige Inhalte auf dieser Seite finden. Einiges funktioniert nicht wie erwartet? Allgemeine Wikidot.com-Dokumentation und Hilfebereich. Wikdiot.com - Datenschutz