Since this blog introduced the invention of the HTML5 car you might expect that we stress this analogy again. Imagine you bought a new car. In the users manual you find the following hint: “In case you are interested in the power but don’t want to drive you can easily isolate the engine and use it for whatever purpose you like.” You might be surprised. Not only that the pure power might be dangerous. In order to make it useful you will need to have something that you can drive with this power.
If HTML5 (based on HTTP) is the car then TCP/IP can be seen as the engine. And HTML5 provides you access to the engine. It allows using TCP plain – without the HTTP around it. And as with the car engine you can only make use of it if there is a counterpart that can consume and react on what is produced. The API that provides this to you is called WebSockets. [read more]
In this post we will investigate a bit on who has the say with HTML5. We will start with another demo called the towers of Hanoi – often implemented in wood or plastics as a child’s game. This game was also used by our computer science teachers to introduce the principles of recursion. We will use it to introduce HTML5 drag and drop. (In the end it could also serve as a demo for CSS3 because it accomplishes quite some graphical tasks just by using some simple CSS3). Try it: [read and play]
Yes, design principles for HTML5 do exist. At least as a W3C Working Draft. As this working draft tells, the plan was to publish them as W3C Working Group Note. Well this obviously didn’t happen up to now. Never the less reading the “HTML Design Principles” helps to understand much better why HTML5 is like it is. [read more]
The following paragraph is special. You may edit it. And with some luck – meaning
localStorage working and enabled – you will find your edits again when you return next time. To be true: it has to be using the same browser on the same computer with the same userid. [read, play and quiz]
Unbeschwert entspannen, unbeschwert wandern? Wandern in Europa!