Windows Vista - Shut down
Although I still found myself hunting the 'shut down' option and inadvertently selecting the globally recognised symbol for stand-by.
]]>
Although I still found myself hunting the 'shut down' option and inadvertently selecting the globally recognised symbol for stand-by.
]]>
]]>
The article describes how to create an array of onload (window.onload) events in order to queue each event and enable the browser to perform onload sequentially. However this can all be forgotten in preference to the Prototype Javascript Framework and the useful Event Observe method.
Use Event.observe instead of using <body onload="return myFunction()"> or DOM Level-0 event property window.onload = myFunction;
]]> ExampleEvent.observe(window, 'load', function() { myFunction.init() });Event.observe(window, 'load', function() { myFunction2.init() });
Here we compare slider controls used on Windows XP, Vista, Apple Mac OSX, and the native Java user interface
It has really only been since the introduction of Web 2.0 and AJAX that the Slider control has been successfully implemented within web design.
Not only is it technically possible to create such an interface but the use of implementation enriches the user experience. Just as with the other slider controls shown above, when the user adjusts the control an immediate response is expected, and it is this response that can now be achieved through AJAX.
Popular and successful implementations of the slider are largely based around filtering search results.
Other popular uses include controlling the scale of a map and selecting the time line of a video.
Lastly we can see the slider control in use within both mobile UI and handset design.
The mobile UI is designed using UIQ, a stylus allows the user to control the slider directly from the handset screen.
]]>Google state that the application design can be segmented into 6 layers:
Mobile users can be divided into three behavior groups:
Repetitive now
A mobile user who checks for the same information over and over again.
Bored now
A user with time on their hands.
Urgent now
User with a need to fulfill an immediate task.
Maintain a consistent look-n-feel across all Google applications.
Drive mobile content through localisation - This is a key advantage for Mobile applications, especially with the recent introduction of readily available Location Enabled Devices (Nokia N95 - with GPS Mapping).
]]>In the mobile world developers have to be prepared to optimize for different devices, browsers, languages, carriers, countries and cultures.
]]> This year could really mark a milestone in website redesign geared to Web Accessibility.
| Method/Property | Description |
|---|---|
| abort() | Stops the current request. |
| getAllResponseHeaders() | Returns the response headers as a string. |
| getResponseHeader("headerLabel") | Returns a single response header as a string. |
| open("method", "URL"[, asyncFlag[, "userName"[, "password"]]]) | Initializes the request parameters. |
| send(content) | Performs the HTTP request. |
| setRequestHeader("label", "value") | Sets a label/value pair to the request header. |
| onreadystatechange | Used to set the callback function that handles request state changes. |
| readyState | Returns the status of the request: |
| 0 = uninitialised | |
| 1 = loading | |
| 2 = loaded | |
| 3 = interactive | |
| 4 = complete | |
| responseText | Returns the server response as a string. |
| responseXML | Returns the server response as an XML document. |
| Status | Returns the status code of the request. |
| statusText | Returns the status message of the request. |
If your webpage does use images with transparency, then the performance difference will depend on how many of those images are present, what size they are, and how they are drawn". (Quoted from the IEBlog).
Take a look at challenger.se the site uses a number of Alpha transparent images, including the ability for the users to drag images around the page.
The author of the site has noticed a few issues when supported Internet Explorer.
]]>I have noticed that IE doesn't free up the memory usage of a filter allocates, even though the element/object its attached to is "deleted"/removed dynamically. This should be taken care of. Otherwise, single-page-navigation-pages allocates very much memory fast.
A change of css-properties will cause IE to re-download any background-images it has attached to the element, event though the background property isn't affected. The "event" bubbles to parent elements as well, which causes additional download. I think this has to be fixed soon, obtain a high priority. (Quote from the Swedish author).