Google Earth Beta for Mac

Thijs van As writes "AppleInsider reports that Google is developing a Google Earth version for Mac OS X. From the screenshots it looks similar to the Windows version, which is out since June 2005. The OS X version uses OpenGL rendering." From the article: "Earlier this month, a pre-release version of Google Earth for Mac OS X that uses OpenGL rendering reportedly began making the rounds overseas. The 40MB application packs a hefty set of preferences, allowing users to tweak detail and color, and control the speed of their 'flights.' Google Earth interfaces with Google's Web-based mapping service, Google Maps, in providing local search results and driving directions. However, sources say Google Earth for Mac OS X includes a superior set of satellite imagery when compared to the Google Maps Web service, offering additional clarity and a deeper zoom function."

Comments

Re:Fell off the ugly tree and hit every branch.

[TheRaven64]

No, take a closer look at the title bars - they are the newer style which came in with 10.3, so the demo machine must be running at least 10.3 but still using 10.2-style controls. The only other time I've seen an app this ugly on a Mac, Qt was to blame - I hope this isn't the reason here, because if it is then looking ugly will be the least of its problems (Qt messes up the feel a lot worse than it messes up the look).

I really don't care what it looks like...

[fyngyrz]

...I'm just happy to see it. While I enjoy pretty, what actually matters to me is functionality and reliability. And in this case, simply availability — this has been beta under Windows for quite some time already.

Too much focus on pretty can result in the "Hollywood Effect" —beauty without value, or worse, beauty that impacts value... like recent media player designs or the incredibly bad Kai's interfaces of yore. I've had enough of that kind of craziness.

Re:I really don't care what it looks like...

[JonathanBoyd]

And my exact point is that this affects its value not at all. The only thing that will affect its value here is if the user, that is, me, or you, decides to take an attitude that we're unwilling to use it because it is inconsistant.

The problem with inconsistency is that programs do things you don't expect. If you spend 95% of your time working one way, but have to work a different way for the other 5%, it becomes pretty inconvenient. For instance, most of the time when I'm typing, I'm using my Mac and the cursor selects whatever line is in the middle of the text cursor. Part of my work, however, involves doing an announcement sheet for church every week in Corel Draw on Windows. For some unexplained reason, it selects whatever line is under the bottom third of the cursor. This drives me nuts because my instinct is select with the middle of the cursor and end up selecting the wrong line quite a bit of the time.

It also has a bizarre convention whereby if you drag select from somewhere on a line to the start of it, then make changes to the formatting of the line, it will also select the carriage return on the previous line and apply formatting to it. Consequently I often have to drag select to the 2nd letter of a line, then shift-left cursor select the first letter. After 14 weeks of use, I have come to loath this program because it does not follow the conventions that I'm accustomed to. Arguably, it's just plain bad design, rather than inconsistency, but I think the inconsistency is still a factor.

You missed my point entirely.

Indeed I did. I apologise. Thought you were talking about clicking a window in the foreground application. My bad.

Say you're using Finder. So a Finder window is active ... Now you have to click again, on the same button, to get the result you should have already had.

That is indeed annoying. Trying that out in other apps, however, clicking a button in a background application activates the button, so the problem would seem to lie with an inconsistency with the GIMP, rather than bad OS X GUI design. One more mark against inconsistency ;^)

The menu at the top uses considerable vertical space, all the time, which is unusable for all applications. You can't get a window to cover the menu bar. At least, I can't in 10.3.9.

Can't in 10.4.3 either, which I'm fairly happy about. Wouldn't want to lose sight of my menubar. It's fairly full. It's only a wee bit of vertical space, especially compared to the resolution of modern screens. Though if you're using multiple monitors, then you only need a menubar on one screen and can avoid them entirely on others, thereby saving space.

Windows may, or may not, require a menu. For some (dialogs, for instance) a YES or NO or even simply OK is all the UI they need. This can be true of much more complex applications as well; if the developer is allowed to make that choice, of course

True, but document windows all seem to have them, which irritates me greatly in Windows. Though the inconsistency in multi-document and single-document interfaces annoys me more. And the inefficient taskbar. And the way that opening multiple files belonging to one program sometimes loads the files into separate windows in one instance of the application, while launching several instances of the application in other cases. And not being able to open a bunch of files by double-clicking on a selected group. But I'm getting a bit off-subject here. I find Windows stressful. It just gets in the way so much.

If a menu is embeddded in a window, say, application A, and there is no menu at the top of the screen, then application A may be dragged to the top of the screen, thus providing menu-on-top functionality if you like it.

Only really works