Monthly Archives: December 2010

iWebKit, jQTouch and iUI

Posted on by

iWebKit is a file package designed to help you create your own iPhone, iPod Touch and iPad compatible website or webapp.

iWebKit has been specially made for Apple mobile devices. Specific iphone css and html rules compatible with safari’s engine called “webkit” are used. Most browsers won’t be able to open an iWebKit site correctly, currently only chrome and safari do on a desktop PC ( http://demo.iwebkit.net).

iUI and jQTouch are frameworks that include all the css, javascript and images needed to build native looking apps.

jQTouch is a jQuery library, it’s functionality is currently comparable to  jQuery UI.

Manipulating HTTP Headers with .htaccess

Posted on by

Last update : July 25, 2013

.htaccess is a very ancient configuration file that controls the Web Server running your website, and is a very powerful configuration file. htaccess is sometimes called “HyperText Access” because of its ability to control access of the WWW’s HyperText Transfer Protocol (HTTP) using Password Protection, 301 Redirects, and much much more.

The AskApache website offers a lot of tutorials, tricks and hacks for webmaster and online tools related to .htaccess.

.htaccess tips and tricks are available at the corz.org website.

!DOCTYPE HTML

Posted on by

The declaration <!DOCTYPE HTML> must be the very first thing in an HTML5 document, before the tag. The doctype declaration is not an HTML tag; it is an instruction to the web browser about what version of the markup language the page is written in.

The doctype in HTML 4.01 required a reference to a DTD, because HTML 4.01 was based on SGML. HTML5 is not based on SGML, and does not require a reference to a DTD, but need the doctype for browsers to behave as they should.

Spoon virtualization

Posted on by

On November 8th, 2010, Spoon announced the immediate availability of the world’s first free cloud hosting service for desktop applications. Spoon allows software developers to make their existing desktop applications available in the cloud, with no installs. Spoon applications can be accessed from the Spoon.net library or embedded into any website, blog, or social edia service as a “Spoon Feed” with a single line of HTML.

Unlike other forms of cloud computing, Spoon completely preserves the richness and responsiveness of traditional desktop applications. Users can save files to local folders, print, and even migrate offline to continue working while disconnected. Spoon’s unique virtualization technology completely eliminates dependencies and conflicts, and seamlessly handles patches and upgrades.

Today I created an account at spoon.net and installed the spoon plugin. I was able to succesfully  run different browser versions of Firefox and Safari in the cloud (without insallting these browsers on my laptop)  to test the compliance of a current web design project with these browsers. I am impressed by this new cloud technology.

Google Body and Biodigital Human

Posted on by

Last update : August 9, 2012

Google Body

Google Bodybrowser

On December 15th, 2010, Google announced the launch in Google Labs of an interesting WebGL application called Body Browser, which lets you explore the human body just like you can explore the world in Google Earth.

Google Body (Google Human) is a detailed 3D model of the human body. You can peel back anatomical layers, zoom in, click to identify anatomy, or search for muscles, organs, bones and more. You can also share the exact scene you are viewing by copying and pasting the URL.

To view the body application, you need a Web browser that supports WebGL. I use Google Chrome.

The 3D body data was provided by the Zygote Media Group, Inc., a leading company in the development of Bio-Medical 3D content (since 1994).

Zygote offers stock 3D models, images and animation of the Human Anatomy Collections through the website 3DScience.com. These collections are the best and most comprehensive available. The artistic and illustrative value is unquestionable while remaining medically accurate.

3D anatomy collection of Zygote

Late 2011, the Google Body application was disabled. A commercial 3D platform BioDigital Human that simplifies the understanding of anatomy, disease and treatments has been launched in the meantime by Biodigital. Founded in 2002, BioDigital is the leading developer of state of the art biomedical visualization systems.

HTML5 Test website

Posted on by

screen snap of the test results

A very useful HTML5 test tool has been created by Niels Leenheer. The goal is to show an indication of how well a browser supports the upcoming HTML5 standard and related specifications. The test tool was upgraded in June 2010 (see the blog).

The maximum score of the test is 300 points. The support of one or more codecs provides additional bonus points.

The results for my installed browsers are :

  • Chrome Canari (beta 10.0.614.0) : 244 points + 13 bonus points
  • Chrome 8.0.552.224 : 231 points + 13 bonus points
  • Safari 5.0.3 : 207 points + 7 bonus points
  • Firefox 4 beta 8 : 197 points + 9 bonus points
  • iPod Touch 4 (version 4.2.1  8C148) : 196 points + 7 bonus points
  • Firefox 3.6.13 : 139 points + 4 bonus points (no H264 support)
  • IE 9.0.7930 : 96 points + 5 bonus points
  • IE 8.0.6001 : 27 points, no bonus points
  • BlackBerry Bold 9000 (version 4.6.0.126) : 14 points, no bonus points

Niels Leenheer stated on his blog that there are problems with the HTML5 video codec detection in most browsers. Safari and Chrome report an answer “probably” with the javascript  canPlayType() command even if the codec indicated is a dummy. I experienced the same behavior in my test environment. Today it’s not possible to check what profile is supported in browsers implementing the MIME video/mp4.

The Web Standards Project’s operates also a test website called Acid Tests site.

W3C provides the mobileOK Checker (version 1.4.2). This work is part of the MobiWeb 2.0 project supported by the European Union’s 7th Research Framework Programme (FP7). The checker is based on the open source mobileOK checker library developed by the Mobile Web Best Practices working group.

Disable Flash in web browsers

Posted on by

To test new web applications, it’s sometimes useful to disable the Flash Plugin in web browsers. The procedures to do this are quite different in the latest versions of the common browsers :

  • IE 8 : Menu Tools > manage external modules > disable Flash
  • Firefox 3.6 : Menu Tools > Modules > Plugins > disable Flash
  • Safari 5 :  Menu Settings > Preferences > Security > disable external modules
  • Chrome 8 : enter about:plugins in address bar > disable Flash in plugin list

WebGL – OpenGL for the Web

Posted on by

WebGL brings plugin-free 3D to the web, implemented right into the browser. Major browser developpers Apple (Safari), Google (Chrome), Mozilla (Firefox), and Opera (Opera) are members of the WebGL Working Group.

WebGL is a cross-platform, royalty-free web standard for a low-level 3D graphics API based on OpenGL ES 2.0, exposed through the HTML5 Canvas element as Document Object Model interfaces.  It stays very close to the OpenGL ES 2.0 specification, with some concessions made for what developers expect out of memory-managed languages such as JavaScript.

WebGL  is developped by the Khronos Group, a not for profit, member-funded consortium focused on the creation of royalty-free open standards for parallel computing, graphics and dynamic media on a wide variety of platforms and devices. The Khronos Group was founded in January 2000 by a number of leading media-centric companies, including 3Dlabs, ATI, Discreet, Evans & Sutherland, Intel, NVIDIA, SGI and Sun Microsystems.

A guide how to get a WebGL implementation is available at the Khronos wiki website.

The current stable version of the Google Chrome 8 browser can be WebGL enabled by entering about:flags in the address bar and enabling the feature. A better (default) support of WebGL is provided with the Google Chrome Canari browser (the development version 10.0.614.0).

The following links point to websites with useful informations, tutorials, tools and ressources about WebGL :

Trackbacks and Pingbacks

Posted on by

Trackbacks were originally developed by SixApart, creators of the MovableType blog package. It’s a notification method between websites working as follows :

  • Person A writes something on their blog.
  • Person B wants to comment on Person A’s blog, but wants her own readers to see what she had to say, and be able to comment on her own blog
  • Person B posts on her own blog and sends a trackback to Person A’s blog
  • Person A’s blog receives the trackback, and displays it as a comment to the original post. This comment contains a link to Person B’s post

Most trackbacks send to Person A only a small portion (a teaser called an “excerpt”) of what Person B had to say. One problem is that there is no actual verification performed on the incoming trackback, and indeed they can even be faked.

Pingbacks were designed to solve some of the problems of trackbacks. The official pingback documentation is available on the website www.hixie.ch.

The best way to think about pingbacks is as remote comments:

  • Person A posts something on his blog.
  • Person B posts on her own blog, linking to Person A’s post. This automatically sends a pingback to Person A when both have pingback enabled blogs.
  • Person A’s blog receives the pingback, then automatically goes to Person B’s post to confirm that the pingback did, in fact, originate there.

There are two significant differences between pingbacks and trackbacks : pingbacks and trackbacks use drastically different communication technologies (XML-RPC and HTTP POST, respectively) and pingbacks do not send any content.

A useful guide “Introduction to Blogging” with more details about trackbacks and pingbacks is published by WordPress.