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.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-02-05
The dock is more tailored to the Apple UI ideas. In windows/linux, you launch an app and it runs fullscreen. At that point, you want as little OS interference as possible. This effectively embraces the idea that applications are Modes. The taskbar provides a way to switch modes.
The Apple way says that applications arent modes, they are operating system objects. The traditional mac approach is you never run windows fullscreen, you run them as large as they need to be. Transitions between one application and another are more seamless, they all look and act the same, have the same menubar, you can often see the work you are doing in one even if you are in another. It is a concept that is very hard to explain to someone who has never really worked with it, but anyone who grew up on mac classic not only gets it, but finds the fullscreen approach kludgy.
Member since:2005-07-06
in linux you can work the way you want to, there is no set desktop in linux.
but gnome and kde use a lot of windows elements as that is what most potential users are used to.
btw, did you just call non-apple users stupid without being direct about it?
anyways, i would say both ways have its issues, and its related to using windows the way they do. i wonder if not one should take a step back to the days before apple introduced free-floating windows.
some of those wm's on *nix seems interesting in that regard.
Member since:2007-07-01
Huh? The Xfce I'm using even has smart window placement, so if I open up 4 terminals simultaneously, not only are they not maximized, but they're automatically placed in separate corners of the screen so all 4 are fully visible at the same time.
Lumping all *nix DE's/WM's together might be a bad idea.
Member since:2005-10-12
"In windows/linux, you launch an app and it runs fullscreen"
They don't, surely? They launch at whatever size you set them to the last time you opened them. They don't even start out full screen do they? Now you have me scratching my head and trying to remember how they worked in Win 98 - someone I do work for is still running W98 on one machine, and I don't think even there the apps open full screen.
I just fired up a whole bunch in Linux, and not one opened up full screen. What is this about?
Is there any difference between MacOS and other OSs in this respect? The tiling or tabbed window managers of course, in Unix/Linux, but they are a rare breed.
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.
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.
"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.
"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."
"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.
"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.
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."
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."
"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."
"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.
Member since:
2005-07-06
thats one blurry line imo...