A few days ago, Apple surprised everyone by releasing the first beta of Safari 4, the company's latest version of their WebKit browser. While I generally love Safari on the Mac (my browser of choice on that side of the fence), I've never felt as comfortable with it on the Windows side of things. In any case, this latest beta has made a very bold move in the interface department, and I'm sad to say that it's not for the better. Let me explain where it went wrong for Apple.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2007-09-08
Err... Native controls in Windows certainly do have their own window, the same as they do in X.
In both systems, a window is simply a region of the screen, which can be drawn to, can receive events, and can have a parent window. The parent window may be the desktop itself (which is also considered to be a window).
The difference is that there are far more special cases in Windows than in X. Special cases in X only occur for top-level windows, or stuff like virtual desktops, and are all handled by the window manager.
In Windows, pretty much every type of control is a special case, which adds default behaviour and appearance. But they are all still windows.
Member since:2006-01-01
Yes you are right, with Windows, every control IS a window (this excludes the menu bar) but unlike X.ORG, by default "visually" it does *not* live outside the parent form (which is the case with X when you show the widget) that created the control (widget). With X.ORG, each control/window/widget can live outside the parent window (form) that created the widget. The Window Manager gives it a border so it is treated like another form (when speaking with Windows terminology). Thus, the "window manager should handle the tab bar logic".
With windows however it is a different story. Each newly created control must be assigned to a real window with borders or what we call a "form". Thus, the "window manager should handle the tab bar logic" is voided because visually, it is not a form.
Because of the way X treats controls, it makes it a bit difficult to create an MDI and not just that but if things get messy, you may end up with a task bar button for each icon on your desktop because each object in X is treated as if it was a form equivalent in Windows. So you have to do a few extra steps to make it behave the way you'd expect to.
As far as Safari is concerned, I trully doubt that's a real title bar. It's probably a panel aligned to the top and masked to look like a title bar. With Windows you can make the entire form behave like a title bar so it's not that hard.
Edited 2009-02-28 22:43 UTC
The new WebKit Opera for Android has been released. "Opera 14 for Android is built on top of Chromium 26, with a total overhaul of the UI in native code, making it fit well with the latest Android design guidelines. Go get the build from Google Play or point your browser to m.opera.com, and give it a spin!"
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."
Member since:
2006-01-01
Window manager? There isn't such thing in Windows. The window border is part of the client area (the form) plus not every new window represents a "new form". Sometimes they are just instances of controls and you would have to manage the show/hide and close functionality manually. Unlike X.ORG, each control (widget when speaking in Linux) does *not* have its own window and it has to have a parent like a form in order for it to be shown thus the "Window Manager" idea is voided.
Edited 2009-02-28 12:32 UTC