The rise of Zooming User Interfaces | In usability we trust
The first time I ever read anything about Zooming User Interfaces was when I was reading The Humane Interface by Jef Raskin, where he introduced the concept of Zoom World, a whole OS based on a Zooming User Interface (ZUI). Of course this wasn’t my first encounter with this type of user interface since I’ve, among other things, been using Interactive maps like Google Maps. But it was the first time that I started considering a Zooming Interface a viable alternative to the traditional interaction idioms. In this article I will explore some of the Zooming User Interfaces out there today and also take a sneak peak of what’s around the corner. Why Zooming User Interfaces Consider this. The maze in this analogy are applications today, confined inside the constraints of the desktop metaphore. Through the evolution of man we’ve relied on recognizing landmarks as means to find our way around. Are ZUI’s difficult to use or hard to understand? Examples of ZUI’s Prezi Seadragon DeepZoom Mooncake Example
Media Research Lab
For the last decade the MRL has lead research efforts in Zooming User Interfaces (ZUIs). These interfaces create an intuitive information landscape - the user moves "further away" to get an overview, or "closer" for more detail, while keeping a sense of orientation and structure that traditional "pop-up" windows and dialogues can't match. Following Ken Perlin's initial "Pad" project (and patent with Prof. Jack Schwartz), a number of systems have been developed. "Pad++" was developed in collaboration with Prof. Ben Bederson and Prof. Ongoing MRL work in this area includes ZUIs for the web and handheld devices, with uses ranging from complex software controls to authoring and reading structured documents. Zooming Pad Demo Pad Web Navigation Demo Patents PAD patent
Xaitment
Products[edit] xaitment currently sells two AI software modules: xaitMap and xaitControl. xaitMap provides runtime libraries and graphical tools for navigation mesh generation (also called NavMesh generation), pathfinding, dynamic collision avoidance, and individual and crowd movement. xaitControl is a finite-state machine for game logic and character behavior modeling that also includes a real-time debugger. On January 11, 2012, xaitment announced that it making its source code for these modules available to "all current and future US and European licensees". The full versions are available for PC (Windows and Linux), PlayStation 3, Xbox 360 and Wii. The pathfinding plug-in is available with a Windows dev environment, but can deployed on iOS, Mac, Android and the Unity Web Player. Partners[edit] xaitment's AI software is currently integrated into the Unity game engine, Havok's Vision Engine, Bohemia Interactive's VBS2 Simulation Engine, GameBase's Gamebryo game engine.[3] Customers[edit]
OpenSolaris
History[edit] OpenSolaris was based on Solaris, which was originally released by Sun in 1991. Solaris is a version of UNIX System V Release 4 (SVR4), jointly developed by Sun and AT&T to merge features from several existing Unix systems. Planning for OpenSolaris started in early 2004. The first part of the Solaris code base to be open sourced was the Solaris Dynamic Tracing facility (commonly known as DTrace), a tool that aids in the analysis, debugging, and tuning of applications and systems. In December 2008, Sun Microsystems and Toshiba America Information Systems announced plans to distribute Toshiba laptops pre-installed with OpenSolaris.[20][21] On April 1, 2009, the Tecra M10 and Portégé R600 came preinstalled with OpenSolaris 2008.11 release and several supplemental software packages.[22][23] On June 1, 2009, OpenSolaris 2009.06 was released, with support for the SPARC platform.[24] There was a post confirming the leak posted to the OpenSolaris Forums on August 13, 2010.
FancyZoom 1.
Update: Version 1.1 released 2/8/08. Good bug fixes + Opera compatibility! ...so I fought back the charging Guanaco, immediately hopped on my paraglider, and basically caught the first flight out of Chile — but not without dealing with some cantankerous customs inspectors while drinking a cool glass of chicha. Really sorry it took so long! Smooth Javascript Image Zooming For Your Web Pages This much-requested chunk of Javascript to zoom images inline, originally written for this blog but later rolled out to the Panic website and used for screenshots, is now polished up, bug-fixed, available for you to use on your website! Designed to view full-size photos and images inline without requiring a separate web page load, FancyZoom's raison d’être (French for "raisin-determination") is providing a smooth, clean, truly Mac-like effect, almost like it's a function of Safari itself. Since FancyZoom is so easy to add to a web page, I encourage you to give it a try! Instructions 5Whoah. Example License
Readings in information visualization: using vision to think - Stuart K. Card, Jock D. Mackinlay, Ben Shneiderman
XSLT
Language for transforming XML documents XSLT (Extensible Stylesheet Language Transformations) is a language originally designed for transforming XML documents into other XML documents,[1] or other formats such as HTML for web pages, plain text or XSL Formatting Objects, which may subsequently be converted to other formats, such as PDF, PostScript and PNG.[2] Support for JSON and plain-text transformation was added in later updates to the XSLT 1.0 specification. As of August 2022[update], the most recent stable version of the language is XSLT 3.0, which achieved Recommendation status in June 2017. XSLT 3.0 implementations support Java, .NET, C/C++, Python, PHP and NodeJS. While XSLT was originally designed as a special-purpose language for XML transformation, the language is Turing-complete, making it theoretically capable of arbitrary computations.[5] History[edit] XSLT is influenced by functional languages,[6] and by text-based pattern matching languages like SNOBOL and AWK. XPath[edit] <?
Demingkreis
Demingkreis oder auch Deming-Rad, Shewhart Cycle, PDCA-Zyklus beschreibt einen iterativen vierphasigen Problemlösungsprozess, der seine Ursprünge in der Qualitätssicherung hat. PDCA steht hierbei für das Englische Plan -- Do -- Check -- Act, was im Deutschen auch mit ‚Planen – Tun – Überprüfen – Umsetzen‘ oder ‚Planen – Umsetzen – Überprüfen – Handeln‘ übersetzt wird. Der PDCA-Zyklus findet ebenfalls Anwendung beim kontinuierlichen Verbesserungsprozess bzw. beim Kaizen. Begriff und Geschichte[Bearbeiten] Der Begriff Deming-Kreis ist nach William Edwards Deming (1900–1993) benannt, einem amerikanischen Physiker und Statistiker, dessen Wirken maßgeblich den heutigen Stellenwert des Qualitätsmanagements beeinflusst hat.[1] Deming selbst bezog sich dabei auf den Shewhart-Zyklus[2] nach Walter A. Vier Schritte[Bearbeiten] Phasen des PDCA-Zyklus Der PDCA-Zyklus besteht aus vier Elementen: Plan Do Check Act Die Verbesserung dieses Standards beginnt wiederum mit der Phase Plan. Anwendung[Bearbeiten]
FancyBox - fancy image zooming tool
