Linked by Thom Holwerda on Sun 18th Nov 2007 15:46 UTC
This is the sixth article in a series on common usability and graphical user interface related terms [part I | part II | part III | part IV | part V]. On the internet, and especially in forum discussions like we all have here on OSNews, it is almost certain that in any given discussion, someone will most likely bring up usability and GUI related terms - things like spatial memory, widgets, consistency, Fitts' Law, and more. The aim of this series is to explain these terms, learn something about their origins, and finally rate their importance in the field of usability and (graphical) user interface design. In part VI, we focus on the dock.
Permalink for comment 285033
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
The Verge pointed me to a blog post by Leap Motion - which reveals how their Kinect-like motion control works with Windows 8. "From the second you plug in your Leap Motion Controller, you'll be able to browse the web and interact with your computer just by moving your hands and fingers in the air. With Leap Motion technology and Windows, you can do everything that's possible with multi-touch inputs - without actually touching anything. This also means that existing applications in Windows 7 and 8 will respond to your natural hand and finger movements. Soon, we'll show you how Leap Motion will work with Mac OS X." Quite cool.
Linked by Thom Holwerda on 05/20/13 21:50 UTC
PocketNow interviews Marc Dillon, and there's an interesting note about why Jolla is keeping the display properties under wraps: "We're leaving some of those details out because we do understand that there are a lot of really big players in the market and they tend to take certain components in the market and dominate them. We created the ability to actually be able to run Sailfish on multiple hardware displays and be able to swap components, so this is part of the demand and supply planning phase. We are committed to this industrial design which is a 4.5-inch display, an 8 megapixel camera on the back and a front-facing camera at the front, and the exact specs of the display we'll provide when we're close to delivery." Something you rarely hear anything about.
Linked by Thom Holwerda on 05/19/13 23:15 UTC
"This is my NeXTstation Turbo Color booting the Mac System 7.1 Operating System using a hardware add-on called 'Daydream'. The Daydream has a Mac ROM and a few custom ICs in it and hooked up to the NeXTs DSP port. Turns your NeXT into a full fledged 68k powered Mac." So cool.
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
"The NetBSD Project is pleased to announce NetBSD 6.1, the first feature update of the NetBSD 6 release branch. It represents a selected subset of fixes deemed important for security or stability reasons, as well as new features and enhancements. Please note that all fixes in the prior security/bugfix updates (NetBSD 6.0.1 and 6.0.2) are also in 6.1."
Linked by Thom Holwerda on 05/18/13 21:06 UTC
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy.
Linked by Thom Holwerda on 05/18/13 7:37 UTC
"In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Linked by fran on 05/18/13 1:38 UTC
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
Linked by MOS6510 on 05/17/13 22:22 UTC
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
"It was the only moment I heard regret slip into Otellini's voice during the several hours of conversations I had with him. 'The lesson I took away from that was, while we like to speak with data around here, so many times in my career I've ended up making decisions with my gut, and I should have followed my gut,' he said. 'My gut told me to say yes.'" The world would've been a much different place - Apple would have been less dependant on Samsung for its chips, which probably would've meant less money for Samsung to develop its Galaxy business.More News »
Sponsored Links
Member since:
2005-07-11
All that being said, a contextual help area that is constantly being updated based on what the user is doing is a fantastic idea. The horrible implementation in Office has unfortunately soured people to it. If someone could come with an implementation similar to tooltips (there when you want it, invisible if you dont need it), IMHO it could be a fantastic way of doing inline help.
Newer versions of Word, most versions of WordPerfect since 8 or 9, and a few KDE apps do this. They put a ~2" column along one side of the screen (right for Word, left for WordPerfect). This area is used for displaying contect-sensitive help links, useful hints, and similar stuff. On low-resolution setups (< 1024x768) it's more annoying than anything as it takes up ~ 33% of the horizontal screen space. But on higher resolution setups, it's not that bad.
The WordPerfect implementation is a lot nicer than the Word implementation. It's actually useful. Especially when it's part of their wizards or perfectexpert projects or whatever they call it.
The problem with hiding the dock (or panels of any sort on other operating systems) is that the trigger area for showing it is WAY to large. If (for example), the trigger was in the lower left hand corner, and as soon as your mouse hit it, the dock would expand out, anchored from the left side of the screen, you would get the desired functionality, while very rarely triggering it accidentally. When the bottom five pixels of the entire monitor triggers the show operation, you will trigger it accidentally far more often then on purpose.
Not sure about GNOME or XFce, but the KDE external taskbar and kpanel can be configured like that. Enable the left or right hide buttons and auto-hide. 3 seconds (or so) after your mouse leaves the panel, it will zip off to the side appearing as thin bar with an arrow down in one corner. Pop the mouse down to that corner and click to bring it back.
Personally, I can't stand the dock concept, and prefer to put a taskbar at the bottom of the screen that only shows running apps. And an app launcher at the top of the screen with just the apps menu, some quick launch shortcuts, the system tray, and clock. Set to auto-hide. Since it's only used to launch apps, it doesn't need to be visible all the time. And since the taskbar only shows running tasks, it doesn't need to be very tall (32px is plenty). It's a beautiful setup in KDE; GNOME and XFce are a little more difficult to get working right, but once it's configured, it works the same.
Separate running apps from non-running shortcuts/repositories/launchers/etc. Only show the info that is needed. Hide everything else until it's needed.
Edit: Why doesn't the quote feature [ q ][ /q ] work on the the v4 setup???
Edited 2007-11-18 22:08 UTC