Group items tagged

In the last edition we learnt that user experience (UX) defines the manner in which an individual responds when interacting and interfacing with a system. These systems encompass a wide range and they include websites, web applications and desktop software. All of this has been classified as coming under the ambit of human-computer interaction (HCI).

Welcome to the home of Jx, a javascript library for creating graphical user interaces based on the fabulous MooTools library. This site provides access to the library as well as extensive documentation and examples. We've tried to provide a complete set of documentation and examples but there are surely some areas that are lacking. Please contact us on the mailing list if you find errors, omissions, or something you think could be done better.

Creating complex web applications demands organization and modularization. Modularization introduces a new problem - the comunication pipes between components. This is a serious challenge for developers, as more components and widgets mean more pipelines and more dependencies. In this article, we'll look at a technique to mitigate these issues: Creating an abstraction layer to moderate the comunication between the components and widgets in a web application. This technique is based on YUI and makes use of my Bubbling Library, which is a BSD-licensed superset of functionality that builds on top of the YUI foundation.

External JavaScript files block downloads and hurt your page performance, but there is an easy way to work around this problem: use dynamic scripts tags and load scripts in parallel, improving the page loading speed and the user experience.

Response to marbux comments.

# See also my comment on the same web page that explains why HTML 5 is NOT it for document exchange between web editing applications. . - comment by marbux # Response to marbux supporting the WebKit layout/document model. Marbux argues that HTML5 is not interoperable, and CSS2 near useless. HTML5 fails regarding the the interop web appplications need. I respond by arguing that the only way to look at web applications is to consider that the browser layout engine is the web application layout engine! Web applications are actually written to the browser layout/document model, OR, to take advantage of browser plug-in capabilities. The interoperability marbux seeks is tied directly to the browser layout engine. In this context, the web format is simply a reflection of that layout engine. If there's an interop problem, it comes from browser madness differentials. The good news is that there are all kinds of efforts to close the browser gap: including WHATWG - HTML5, CSS3, W3C DOM, JavaScript Libraries, Google GWT (Java to JavaScript), Yahoo GUI, and the my favorite; WebKit. The bad news is that the clock is ticking. Microsoft has pulled the trigger and the great migration of MSOffice client/server systems to the MS WebSTack-Mesh architecture has begun. Key to this transition are the WPF-.NET proprietary formats, protocols and interfaces such as XAML, Silverlight, LINQ, and Smart Tags. New business processes are being written, and old legacy desktop bound processes are being transitioned to this emerging platform. The fight for the Open Web is on, with Microsoft threatening to transtion their entire business desktop monopoly to a Web platform they own. The Web is going to be broken. There is no way of stopping Microsoft at this point. What we can do though is focus on Open Web solutions that are worthy alternatives to Microsoft's proprietary push. For me, this means the WebKit layout/document model supported by Apple, Adobe and Google. ~ge~

A CMS expert argues for HTML over XHTML, explaining his reasons for switching. Excellent read! He nails the basics. for similar reasons, we moved from ODF to ePUB and then to CDf and finally to the advanced WebKit document model, where wikiWORD will make it's stand.

A pattern library for interaction design

very nice fish eye image gallery system based on mootools

article about events in web application design

Referred from http://www.diigo.com/bookmark/http%3A%2F%2Fmarypcb.livejournal.com%2F351403.html?f=m&tab=people&uname=grahamperrin

@ Diigo Let's make best use of the Faviki Save/Edit API.

The bookmarklet for Faviki is compelling.

"Community features are spreading from 'Web 2.0' to 'Enterprise 2.0.' Research across 14 companies found that many are making productive use of social intranet features."

Simple architecture: * WebKit-based Google Chrome * a new windowing system * Linux kernel. Open source, large developer base, large user base. Smart!

Thinking about laptops that are gathering dust … the OS will run on x86 or ARM. I wonder about other requirements: * memory * display resolution * etc..

A new project, a natural extension of Google Chrome - the Google Chrome Operating System … to re-think what operating systems should be.

Referred from http://digital.venturebeat.com/2009/07/02/new-twine-interface-lets-users-visualize-shared-bookmarks/

referred from http://lists.okfn.org/pipermail/okfn-discuss/2009-December/007043.html

Rebooting is an essential task which should be performed every month to install updates and patch the kernel. Rebooting your server will help you to increase performance of your server. Let's see how to use the command line interface to to schedule a reboot for your windows server.