TidBITS

Hard link

TidBITS Watchlist: Notable Software Updates for 08-Sep-08

• Sound Studio 3.5.7 from Freeverse fixes a bug in the popular sound editor that prevented Automator actions and Sound Studio's Monbots automation tools from opening files. It also corrects an AppleScript error in the Bookend Audio Monbot when running under Mac OS X 10.5 Leopard. ($79.95 new, free update, 34.7 MB)
• Tinderbox 4.5.1 from Eastgate Systems enhances the "personal content assistant" with numerous cosmetic improvements, including new shapes for maps, customizable drop shadows, and improved typography. Outline titles can now extend to multiple lines; outlines can be edited in place; agents update more quickly; and agents and containers can have pull-down summary tables, sparkline plots, and bar graphics. Tinderbox 4.5 also features better address book and vCard integration, with automatic linking. ($229 new, free updates for purchases within the last year or $90 otherwise, 16.8 MB)

�

Copyright � 2008 Adam C. Engst. TidBITS is copyright � 2008 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.

04.09.2008 00:07:46 - TidBITS

Hard link

Google Serving Itself DMCA Takedown Notices on Chrome Videos?

Update: It's all working now, so take a look at the videos to get a sense of what Chrome can do. -Adam

So I decided that even if Google's new Chrome Web browser is available only for Windows right now, I should take a look through the feature videos to get a feel for what's forthcoming for Mac users.

"One box for everything." Sounds great. -click- "We're sorry, this video is no longer available." Gee, I wonder if Google served itself a DMCA takedown notice on the Tolkien reference.

"New Tab page." I'm in favor of that. -click- "We're sorry, this video is no longer available." Hmm, perhaps Chrome's tabs are a bit too kinky for YouTube.

"Application shortcuts." -click- "We're sorry, this video is no longer available." Grr...

"Dynamic tabs." -click- "We're sorry, this video is no longer available." -click- "We're sorry, this video is no longer available." -click- "We're sorry, this video is no longer available." -click- "We're sorry, this video is no longer available." Oh, never mind.

Maybe I'll try again in a few minutes.

�

Copyright � 2008 Adam C. Engst. TidBITS is copyright � 2008 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.

03.09.2008 03:09:07 - TidBITS

Hard link

Google Explains Its Forthcoming Web Browser with Comics

Understanding technical concepts, even for those who spend their days with their "heads inside the computer," as I conceive of it, can often be a reach. People learn in different ways, and hearing an explanation, seeing a visual representation, and reading about something all reach different individuals.

Google decided to hire the talented Scott McCloud to explain in graphics using the company's words how their new Chrome Web browser differs from all those currently available. It's a neat idea: in explaining their JavaScript optimization, for instance, you don't need to understand what a classless programming language is if you look at the graphical representation, which is simplified, but entirely accurate.

The comic was released under a Creative Commons license, and accidentaly sent ahead of schedule through postal mail to an unknown number of people. Philipp Lenssen of Google Blogoscoped explains that he received, scanned, and posted the comic; Google later posted the full comic at the company's book site.

The site referenced in the comic, www.google.com/chrome, isn't live at this writing, but a Google blog post says that a beta for Windows will be released on September 2nd, and that Mac OS X and Linux versions will follow further on in the development and beta testing process.

Chrome has a key difference from previous browsers: each tab runs as a separate process to isolate JavaScript slowdowns, security exploits, and browser crashes to that tab. This is much the same compartmentalization that multi-tasking operating systems use to prevent one crashing program from bringing down the entire system.

Google says in this comic that they have vastly improved the speed of JavaScript by commissioning an advanced JavaScript virtual machine. In June 2008, the WebKit project announced its own JavaScript virtual machine optimization project dubbed SquirrelFish.

For pages that feature pop-up windows, whether useful or advertising come-ons, each tab will capture the pop-ups and enable you to convert them into freestanding windows.

Security is enhanced, Google says, by disallowing each tab from writing files or examining data on the hard drive. This is a typical behavior, and something that Apple and Microsoft have implemented in some form in Safari 3 and Internet Explorer 8. Google has also implemented a three-tier hierarchy of trust that it believes will prevent unintentional privileges being granted to programs or scripts on Web pages that shouldn't have them.

The browser will also let you shroud a given tab in secrecy - an "incognito" window - so you can exclude its pages, passwords, and other details from the browser's cached or saved elements. People typically use this mode to avoid leaving traces on a shared computer - often for personal research, viewing unclothed individuals, or keeping a gift or party secret.

Chrome will be based on WebKit, the same open-source project used as the fundamental basis of Apple's desktop and mobile Safari and Nokia's S60 browser, which Nokia will ultimately use to replace all its current browsers and which is part of the future direction of the Symbian platform.

Scott McCloud is best known for his "Understanding Comics" and "Reinventing Comics," in which he uses the medium to explain its past, present, and potential future, a future in which McCloud has been deeply involved.

This is the best kind of browser war: unlike the monopoly-driven efforts by a certain firm to kill Netscape Navigator in the 1990s, we're in a time of browser plenty. Microsoft recently released a second beta of Internet Explorer 8 for Windows; Firefox 3 for all platforms appeared not long ago from the Mozilla Foundation, the spiritual heirs of Navigator; and Apple keeps pushing WebKit and Safari to have greater speed and more security for Windows, Mac OS X, and the iPhone and iPod touch. And that's not even considering other entrants such as OmniWeb, Opera, iCab, Camino, and Flock.

The nice part for users is that with Google's entry, we'll have four browsers, all of which are intended to be fast, easy, and secure, and which use three separate rendering platforms (Chrome and Safari sharing WebKit). This ensures the kind of diversity of evolution that promotes better software and a lower chance of a single flaw being exploited in all extant browsers. It also means job security for Web developers used to tweaking designs to look good in multiple browsers.

�

Copyright � 2008 Glenn Fleishman. TidBITS is copyright � 2008 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.

01.09.2008 22:31:47 - TidBITS

Hard link

Hot Topics in TidBITS Talk/01-Sep-08

App store mail list -- Where does one go to find the latest releases in Apple's App Store? RSS and Twitter feeds are available. (4 messages)

MacBook Pro power on airlines -- Attempting to charge a MacBook Pro on a flight didn't work, possibly due to the power required to charge versus the power needed to run the laptop without charging. (5 messages)

Screensaver/Expose issues -- A reader's screen saver starts and stops without any indication of the underlying reason. (2 messages)

Sleep Problems with Eudora -- A bug in Eudora is keeping a Mac from sleeping. (7 messages)

VNC on Tiger -- Readers share their experiences using Chicken of the VNC under Mac OS X 10.4 Tiger. (2 messages)

Security Concern of an un-commanded start-up -- An iMac mysteriously starts itself in the middle of the night. Gremlins? Or a bug? (6 messages)

�

Copyright � 2008 Jeff Carlson. TidBITS is copyright � 2008 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.

01.09.2008 20:58:37 - TidBITS

Hard link

How to Use Google Docs Offline in Safari

It's ironic that with all the writing I do, I've never settled on a single word processor, instead picking and choosing among lots of different ones depending on the task at hand. Although it's a mediocre word processor, we've started using Google Docs for certain sorts of collaborative writing, such as when Tonya and I are working on marketing materials for Take Control, or when I'm writing an article for Macworld. Its brilliant collaborative capabilities more than make up for its minimal feature set, and I have found it better for my needs than similar products like Zoho Writer and Buzzword, which don't seem as focused on enabling quick collaboration.

Like all online word processors, Google Docs has one significant architectural limitation: if you don't have Internet access, your documents are completely unavailable to you. Google has been working on eliminating this limitation with a technology called Google Gears (Zoho Writer and a few other Web apps also use Gears - it's an open source technology that any developer can implement). Gears addresses the disconnected problem with a database engine based on SQLite, and Gears-enabled pages can send and receive data from this local database cache when offline. When connectivity is reestablished, Gears synchronizes the changes back up to Google's storage cloud.

Gears has been available for the Mac via the Firefox Web browser for some time, but Google just released a "beta" version of Gears for Safari. (Nearly everything Google does is labeled as beta, even after years of development and millions of users, which makes it difficult to determine the actual state of the code.) I had tried Gears with Firefox briefly before our trip to Wales, but I found it a bit confusing and hadn't come back to it until this Safari release, which I suspect will be attractive to more Mac users anyway. The Safari release was quiet, and Google's Gears home page doesn't yet acknowledge that it's compatible with Safari.

Gears for Firefox is a Firefox add-on, but for Safari, Gears has two parts, an input manager (installed in /Library/InputManagers) and an Internet plug-in (installed in /Library/Internet Plugins). Some people don't like input managers; if so, stick with the Firefox version.

Installation and Setup -- Until Google officially releases Gears for Safari, you can't follow the normal installation method, which is to visit the Gears home page and click the Install Gears button (do that if you want to install in Firefox now). Instead, download this disk image and run the installer inside. You'll have to restart Safari to finish the installation. Gears automatically updates itself, so when Google releases new versions, you should just get the updates. You can also verify that the installation has worked by looking for a Google Gears Settings menu item in the Safari application menu. But don't choose that just yet. Instead, go to Google Docs, and at the upper right of the page, click the Offline link next to your email address to continue the installation process in a series of dialog boxes.

First, Google Gears asks you to enable offline access; click the Enable Offline Access button. Next, Gears asks if it's acceptable to store data on your computer (necessary, of course, but nice to be asked). Select the "I trust this site. Allow it to use Gears" checkbox and click Allow.

Gears then asks if you want to make a desktop shortcut, which isn't necessary, and can be done later if you want. The desktop shortcut is actually a small application that's created on your Desktop, but it doesn't have to stay there. Double-clicking it opens Google Docs in the Web browser that was your default as of when you created it; it isn't smart enough to switch if you change your default, but you can recreate it if necessary. Merely dragging the Google Docs URL from Safari's address bar to the Desktop to create a .webloc file provides exactly the same functionality as the Google Docs application that Gears creates.

Once all that is done, Gears synchronizes your data, which shouldn't take long unless you have a vast number of documents stored in Google Docs. Subsequent synchronization takes place regularly, and you'll likely never notice it.

Basic Usage -- If Safari is open, you can just navigate to http://docs.google.com/ manually, via .webloc file, or via the Google Docs application that Gears creates. Once there, click any document to open it, make changes as you would normally, and when you're done, click the Save & Close button. Keep in mind that you can edit only word processing documents; spreadsheets and presentations can be viewed offline but not edited yet.

Google uses only a tiny icon that switches between a green checkmark and a gray slashed circle to indicate whether you're online or offline in the main Google Docs file list. Unfortunately, that icon doesn't update quickly, so even after I disconnected my Mac from all networks, it claimed I was online for a few minutes before realizing otherwise. Similarly, when you're in a particular document, a green, downward-pointing arrow indicates that the document is in sync; a gray, upward-pointing arrow tells you that there are changes that need to be saved next time you connect. Maybe it's just because I'm feeling my way around what it's like to work offline in an online word processor, but I would have appreciated more obvious status markers.

Edited documents do get a little "Edited offline" tag next to them in the Google Docs file list, and shortly after you reconnect to a network, Gears notices and synchronizes your documents back to the cloud, erasing the "Edited offline" tag at the same time.

Note that if you choose to install Gears for both Firefox and Safari, the two don't share the same data store. In other words, if you make a change in a document in Safari while offline, you won't see that change in Firefox until the Safari version is synchronized back to Google Docs. That's not unreasonable, but for those of us who use multiple Web browsers regularly, it could cause some confusion.

Protecting Against Beta -- My only concern about the pre-release nature of Gears is that I'd hate to lose a plane ride's worth of work should something go wrong. I haven't used it much, and although I haven't had any problems, I do worry a bit, since Gears is saving to a database, not a normal file that you could extract easily if necessary.

Of course, you can always copy the text and work on it in TextEdit or some other simple word processor, but what I'm considering instead is using a utility like Keyboard Maestro or CopyPaste Pro that maintains a clipboard history. Then, every so often, as a backup, I'd just select all and copy.

Needless to say, Gears is free, as is Google Docs, and it requires Safari 3.1.1 or later on Mac OS X 10.4.11 or 10.5.3 or later. Even if you don't plan to use Google Docs offline much, I'd encourage you to give it a spin, since it might let you get some work done at a time when you'd otherwise be dead in the Internet water.

�

Copyright � 2008 Adam C. Engst. TidBITS is copyright � 2008 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.

01.09.2008 18:18:13 - TidBITS

Hard link

SugarSync Sweetens Online Syncing

In my ongoing efforts to keep up with the latest Mac backup tools, I've come across a number of services that promise to automatically synchronize some set of files from your Mac or PC with a server somewhere on the Internet, such that you can access those files from nearly any device that can run a Web browser. Among the many services in this category are SpiderOak, Dropbox, and of course MobileMe's iDisk feature.

On the whole I've found these services interesting but not exciting - there's always at least one "gotcha," such as a missing key feature, significant bugs, an unreliable infrastructure, or so-so Mac software. (MobileMe, alas, has thus far been an offender in all the above categories.) However, one such service I've had my eye on for a while, SugarSync from Sharpcast, suddenly got much more interesting last week with the release of an iPhone client and a new online feature.

Introducing SugarSync -- First, the basics. You pay for the SugarSync service based on the amount of online storage space you want - rates start at $24.99 per year for 10 GB and go up to $249.99 per year for a healthy 250 GB. Once you've signed up (a free trial is available), you download the free client software, which is available for Mac OS X and Windows; they also offer mobile versions for Blackberry, Windows Mobile, and now iPhone.

The client software runs in the background and automatically synchronizes any folders you specify (such as your Desktop folder or Documents folder, space permitting) with the SugarSync servers. Assuming an active Internet connection, synchronization happens immediately when files in the designated folders change on any device - that makes it a genuine "push" application. You can see and download your synchronized files by logging in to the SugarSync Web site, and if you set up the software on more than one computer, you can use it to sync files between them. All files are encrypted and transferred using SSL connections.

So far, that may sound like a more-flexible, higher-security, cross-platform version of iDisk. But wait, there's more!

Doing iDisk One Better -- If you've paid close attention to the MobileMe news, you may know that the service is missing a feature that was demonstrated publicly and was even shown in Apple's introductory video about MobileMe (though the video was later changed to remove any mention of this feature). What we were supposed to have seen was a button on the iDisk page of the MobileMe Web site that let you email someone a link to any file. So, instead of emailing a large attachment, you'd just put a file on your iDisk, click a button, and send someone a special, private URL at which they could download the file. That sounded great to me, but for whatever reason, that feature isn't part of MobileMe - at least not yet.

Well, with SugarSync you can do exactly this. For example, the other day I needed to send out copies of a number of my Take Control ebooks to a user group at which I'm going to be giving a presentation next week. The combined size would have exceeded what my mail server permits, and the files could easily have been rejected on the receiving end too. So I stuck them in one of my SugarSync folders, selected them in the SugarSync Manager window, clicked the Send Files button, typed in an email address, and that was that.

SugarSync on iPhone -- All that is useful, but it gets even better with the iPhone app. With a couple of taps, you can see a list of the files in the designated sync folders on your Mac or PC, and if they're in a format the iPhone understands (such as Microsoft Office, PDF, plain text, or most graphics formats) you can view the file on your iPhone. Not only that, but you can email someone a link to any of these files right from your phone - and here's the cool part - even if the file isn't actually on your phone.

So picture this. You've set up your Downloads folder to sync with SugarSync. On your way out the door to work, you click on a link to download a 300 MB file, knowing that it will take some time to show up on your computer. Then, while riding the train or walking down the street, you pull out your iPhone, tap a few buttons, and email a link to that file to a friend, who can download it immediately, without the file ever having to sync to your phone at all - no worries about bandwidth limits, slow uploads, or anything else. (Oh, and by the way, when you get to work, the file will also be waiting for you on your PC!)

The technology behind this is all very straightforward, but SugarSync's excellent implementation is what makes it feel magical. I'm so used to syncing meaning literally copying entire things from one place to another (and it usually is exactly that), but the SugarSync iPhone app lets you do a sort of lightweight, virtual syncing that turns out to be much more practical in many situations.

Here's another example. You've got, say, 10 GB of files on your Mac synced with SugarSync, but far less than 10 GB of free space on your iPhone. And if you did have the space, you wouldn't want to wait for all that stuff to transfer - even with a USB connection, it would take a very long time. Yet, curiously, when you look at your sync folder on your iPhone, all the files appear to be there, with changes appearing almost instantly even over a cellular connection. And, sure enough, if you try to view one of the files on your iPhone, there it is!

Well, I fib slightly. What I described can happen, and often does, with smaller files and a Wi-Fi connection. But in fact what SugarSync offers iPhone users is essentially on-demand sync. It shows you all your files, and as soon as you ask for one, it fetches it from the server, which in some cases can be so fast it appears that the file was already on your phone. SugarSync also deletes the file when it's no longer needed, so you can get approximately the effect of having many gigabytes of files available on your iPhone at any time without (most of) them actually being there.

I'd like to mention two other interesting features of the SugarSync iPhone app. One, a seemingly small but very handy thing, is renaming: you can rename a synchronized file on your computer (and the SugarSync server) from your iPhone. I'll give you an example of how I put this feature to use. The iPhone can display text files, but only if it knows they're text files, which it determines by looking at the extension. I had some documents on my Desktop that I created in BBEdit and didn't bother giving an extension, and I wanted to read them on my iPhone. No problem: I just added a ".txt" extension, and a View File button instantly appeared in SugarSync, letting me see their contents.

The other interesting feature, which doesn't appear in the desktop or Web versions of SugarSync, is a list of Recent Documents - which is to say, shortcuts to the most recently edited files in any of your designated sync folders. Unfortunately, files don't disappear from this list when they're deleted, and I had dozens of copies of some "recent" (but long since deleted) files on my iPhone. I eventually figured out how to clear them from the list, but it was an odd, awkward procedure: I had to log in to the SugarSync Web site, locate the previously trashed files in my Deleted Files folder, select them all, and click Permanently Delete. They did immediately disappear from my iPhone, but I think the Recent Documents feature should exclude deleted files.

Versioning, Almost -- Although I'm most excited about the SugarSync iPhone app, I also want to mention an important new feature that applies across the SugarSync line: versioning. Previously, SugarSync kept copies of synchronized files that you'd deleted, but now, in addition, it keeps up to five older versions of every file. This is very good, because it officially promotes SugarSync from "just a sync program" to "an honest-to-goodness backup program" in my book - it now creates what I refer to as additive incremental archives.

However, my enthusiasm for this new feature is tempered by the fact that it stores only the last five versions; because SugarSync syncs so efficiently, those five versions of an important file you're working on could easily turn out to be all from the last 10 minutes! If you could store more versions, or if you could restrict SugarSync to keeping a maximum of one older version per hour (or even per day), I think that would provide more realistic and practical protection. As it is, it can't do the one thing I want to be able to do with backups of files I'm actively working on, which is to restore an arbitrary version from hours or days ago, even if the file has been saved dozens or hundreds of times in between. So, it's no Time Machine, but at least it's a step in the right direction.

Final Thoughts -- I recently read a rumor to the effect that Apple is planning an iDisk feature for the iPhone and iPod touch in the next month or two. Obviously, I have no idea if the rumor is true, or what such a feature would look like if it did exist. But I will say that if Apple wants to outdo SugarSync in cleverness and convenience, they've got their work cut out for them.

Meanwhile, even if you don't have an iPhone or iPod touch, SugarSync is well worth trying out. Sharpcast offers a 45-day free trial of the service with a 10 GB limit, which should be more than adequte to get a feel for what it can do. SugarSync 1.1.10 for Mac is a 19.9 MB download.

�

Copyright � 2008 Joe Kissell. TidBITS is copyright � 2008 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.

30.08.2008 23:49:04 - TidBITS

Hard link

Searching for the iPhone 3G Case of My Dreams

For nearly as long as I've owned cell phones, I've carried them in my pocket, sans case, and I figured that when I got my spiffy new iPhone 3G, I'd probably do the same thing. The new phone would be slimmer than my old one, making it more pocketable, and I'd never had any particular problems with scratches or other damage (as long as I remembered not to put coins, keys, or other hard objects in the same pocket as the phone).

However, as soon as I began using my new iPhone, I realized that the glossy plastic case provides very little grip. If my hands are at all sweaty, the device feels worryingly slick. I found myself feeling anxious about pulling the phone out of my pocket on a crowded subway platform or sidewalk, because it would be so easy to drop. And, of course, even if the phone kept working thereafter, its beautiful shiny surface would be marred.

In the first couple of weeks after the iPhone 3G's launch, only a few case options were available (and of those, still fewer were available here in France), and though I fully expect that number to climb into the triple digits before long, I had to work with what I could find. My major desire was for something to provide traction, and secondarily, to cushion the phone slightly in the event that it did fall. I won't wear a cell phone clipped to my belt or otherwise visible on my person, and I don't like having to perform an additional procedure of opening a case or removing a phone before I can use it. So holsters, sleeves, wallets, and other such designs were out - I was looking for a simple, slim case with a decent texture.

PixelSkin -- The first case I tried was the PixelSkin from Speck Products. This is a rubbery one-piece case that slips onto the phone easily and allows ready access to the controls, ports, and camera lens. (The case feels like it's made of silicone, but the manufacturer doesn't say what the material is.) Because of the case's texture and chunky surface, my anxiety about dropping the phone magically went away - an immediate plus. I also appreciated that it came in purple, my favorite color (as well as five other colors), and putting the case on the phone was as easy as could be.

After using the PixelSkin for about a week, though, I realized that my criteria for choosing a case had left out a few important facts. For one thing, I hadn't considered the ease of getting the phone into and out of my pocket. As fantastic as the PixelSkin was at being "grippy," that also meant that I couldn't get it out of my pocket in a hurry without turning the pocket inside-out. So for me, a texture that didn't adhere quite so well to its surroundings would have been a better choice.

Also, although the PixelSkin was plenty thick and cushiony (a good thing safety-wise), that made my slim new phone about as thick as my old one had been, a minus in my book. In addition, the case's raised lip around the screen, which might have protected it if the phone fell, sometimes interfered with tapping or dragging right near the screen's edge. And finally, I prefer to use a dock when syncing and charging my iPhone, and the PixelSkin's case had to be removed every time I docked the phone.

Elan Form -- So my revised selection criteria included thinness, a less-tacky surface, better access to screen edges, and dockability. That turns out to be a rather tall order for an iPhone case, but I found one particularly promising candidate: the Griffin Elan Form. It's a thin, two-piece polycarbonate shell covered with leather. (It comes in pink with brown trim, and in black.) The large, top piece slides on the phone and stays there; a smaller bottom piece pops off to enable the phone to dock. Griffin also includes a screen shield made of heavy transparent plastic.

It took a bit of oomph to get the case on the phone, as the fit is quite snug. The first few times I removed the bottom piece to dock the phone took a bit of finessing too; but now it stays on nicely when I want it to be on, yet comes off without a struggle.

The textured leather provides a nice solid grip on the phone without the stickiness or bulk of the PixelSkin; it also slips into and out of my pocket easily. Because the lip around the screen is much smaller, access to the edges of the screen is no problem. And, of course, I can now dock the phone without removing the entire case, though I do have to slip off the bottom piece, which could then potentially be lost. I'm not sure it's a huge improvement to remove only part of the case rather than the whole thing to dock the phone, but it seems somewhat easier to me. One small complaint: after a few weeks of use, the leather began pulling away from the plastic shell in one corner. I'm sure I could glue it back into place, but I shouldn't have to be making repairs, however minor, on something I just bought.

Using the Elan Form made me realize there was yet another deficiency in my selection criteria: I hadn't taken the screen into account.

I wasn't especially worried about scratching the glass screen, but all the same, I figured it couldn't hurt to pop in the Elan Form's screen shield. Unfortunately, this piece of plastic is a real blemish on the case's overall design. Thankfully, the shield doesn't adversely affect the screen's touch sensitivity. But it's a thick piece of plastic that's not perfectly rigid and as such, it doesn't make complete contact with the entire screen. Even if you scrupulously avoid moisture or grease on the screen or the cover, the parts of the shield that come in contact with the screen will have a blotchy, amoeba-like appearance, which is both unsightly and distracting.

Crystal Film -- A number of companies make flexible, stick-on screen protectors for the iPhone, and having read a review of the Elan Form that mentioned the screen-shield problem, I preemptively purchased a pack of Power Support's Crystal Film for the iPhone 3G. Each package contains two removable screen protectors that (in theory, at least) adhere perfectly to the glass's surface. (The company also makes a version called Anti-Glare Film, which is supposed to reduce the appearance of fingerprints due to its matte finish, though some users have complained that the finish also gives the display a grainy appearance. I haven't seen or tried that version.)

Years ago when I had a Palm, I bought screen protectors, and I remembered how tricky it was to apply them without getting any air bubbles or dust particles between the protector and the screen. So I took extraordinary precautions to work in as dust-free an environment as I could and to clean the phone thoroughly. Then I applied and removed the adhesive sheet Power Support includes for last-second dust removal and applied the screen protector as carefully as I could.

On the plus side: I was able to apply the film with no dust or bubbles. Unfortunately, I didn't realize until it was too late that it was very slightly crooked; the alignment turned out to be much more of a challenge than anything else. More irritating, though, was the fact that even though this Crystal Skin model was expressly designed for the iPhone 3G, it doesn't quite cover the screen - there's a gap of about 1 mm all the way around. And because the Elan Form comes just to the edge of the screen in the front (a good thing), it leaves the edges of the Crystal Film exposed, so I'm constantly reminded that it's there (and that I didn't get it on perfectly straight).

Apart from that, the Crystal Film works as promised. It feels and acts just like the original glass, and collects grease and fingerprints with equal ease. That's all fine with me, though, because the main thing is that I don't worry about minor scratches or dings on the screen and the display isn't impaired in any way.

Inching Toward Perfection -- Now that I've gone through two cases and a screen protector, I've finally come to understand what I actually want in an iPhone case, though finding the model that suits me perfectly will undoubtedly require more trial and error. I want something that will interfere as little as possible with my normal use of the phone - pocketing it, docking it, and interacting with it - while providing a good grip and protection against scratches and other minor damage, preferably for the whole phone.

With that in mind, there are two other products I'm interested in trying:

• ZAGG invisibleSHIELD: It's like a stick-on screen protector, but the two pieces wrap around the entire phone. It claims to improve the grip, though I wonder how well it will stay on, and whether I'd be nervous that it provides essentially no impact protection.
• Speck Products' SeeThru: These cases are similar in design to the Elan Form, including the slip-off bottom piece for docking, but are transparent (in your choice of colors - again, happily, purple is an option). Unlike other hard plastic cases with docking support (such as the Incase Slider Case and the Contour Flick), these have non-slip strips on the side. And, as a bonus, the removable bottom section doubles as a stand that holds your iPhone in landscape orientation.

I'm sure there are other suitable options too, or will be in the near future. Of course, I'd prefer not to spend as much money on cases as on my calling plan, so the case of my dreams better come along soon!

�

Copyright � 2008 Joe Kissell. TidBITS is copyright � 2008 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.

30.08.2008 19:35:35 - TidBITS

Hard link

BBEdit 9.0 Adds Something for Everyone

Bare Bones Software's BBEdit, one of the longest-standing applications in the Macintosh world, has received a major update to version 9.0, adding a number of features that will likely enhance the productivity of anyone who uses the text editor or currently relies on a less-capable program. Whether you need a Web authoring tool, a programmer's editor, a utility for manipulating massive text files, a writing tool that focuses purely on text, or all of the above at different times, BBEdit 9.0 has new features that will make your life easier. Oh, and yes, if you look hard enough, it has ponies too.

Find Modelessly -- Perhaps the most significant changes to BBEdit 9.0 apply to its much admired searching capabilities. In this version, Bare Bones has separated the act of searching for text within a single file from searching for results across multiple files. A modeless, resizable Find window provides all the grep-capable searching power that BBEdit users have long appreciated. However, if you want to run a search across multiple files, you'll instead rely on a new Multi-File Search window that's also modeless and resizable. Multi-File Search can search through open documents, as well as the contents of disk browsers, recent folders, BBEdit projects, recent Xcode products, and even saved Spotlight searches. There's also an option to colorize grep searches in the Find window, which should make complex grep patterns easier to parse.

After all these years, it's great to see Bare Bones setting the old modal Find & Replace dialog aside ("Thank goodness!" exclaimed Tonya when I shared this news). But never fear, if you're addicted to the old interface, or if you frequently want to switch from searching for text in a single file to searching for the same text in multiple files, an option brings back the old Find & Replace dialog.

Another related feature that has changed significantly, and for the better, is BBEdit's Find Differences. In BBEdit 8.5, Bare Bones added the capability to display which characters within a line were different between two similar files. That was huge for us, since it enabled us to use BBEdit in conjunction with the Subversion version control system to work with TidBITS articles. Though code may have relatively short lines, a line of prose is a paragraph, and without knowing what within a paragraph has changed, knowing only that two paragraphs are not the same isn't particularly helpful. In BBEdit 9.0, Bare Bones has enhanced the Find Differences feature such that it not only shows the changed lines, and the changed characters within each line, it also lets you see and replace individual spans of differing characters within each changed line.

Browse & Edit -- BBEdit has long had File Group documents that enabled you to bring together files and folders from disparate parts of your hard disk, but file groups were really just an alternative view of files that already existed in the Finder; you could open, rename, and delete them, but not much more. Similarly, the program has long featured Disk Browser windows that showed a view of files and folders on the hard disk; within a disk browser you could see, but not modify, the actual content of files. In BBEdit 9.0 both file groups, renamed Projects, and disk browsers now work the way they should in providing not just opening and previewing capabilities, but full editing. Whenever you click a file in the left sidebar of a project or disk browser window, the file opens in the main window, fully editable. Double-click a file and it opens in its own window, just as in previous versions.

For programmers dealing with hundreds or thousands of files, BBEdit's file groups and disk browser windows were useful before, and they're far more useful now. For those for whom the previous features weren't helpful previously, they very well may be now - I plan to give them a try, whereas I'd never seen the benefit before.

Alas, BBEdit's FTP/SFTP Browser does not yet share this editable pane feature, which would be huge for Web developers. It would also be great to see additional version control interface within disk browsers, identifying files that had been changed in the repository but not yet updated, or that had local changes not yet committed back to the repository.

Because it's possible to have a file open in a project window, in a disk browser, and in an independent window, BBEdit 9.0 also lets you change a file in any window and have the changes reflected immediately in all the others. I can't quite imagine why you'd want to open multiple views to a particular file intentionally, but the alternative - keeping track of which window contained which changes to the same file - would undoubtedly cause fits of uncontrolled gibbering.

More Features -- Though editable panes in Project and Disk Browser windows and the modeless Find interface are the marquee features of BBEdit 9.0, there are plenty of other additions. A Scratchpad window provides an constantly saved place to dump bits of text for editing or copying into other documents. If you use BBEdit on multiple Macs, the program can now sync the contents of the ~/Library/Application Support/BBEdit folder to other Macs via MobileMe - handy for maintaining the same clippings, text factories, and other settings between computers. One clever technique - if you have to use BBEdit 9.0 on someone else's Mac temporarily, you can simply copy the version of the BBEdit folder on your iDisk down to the Mac to recreate your personal environment.

Also new is text completion, which enables you to type a character or two, press a key, and select the desired expansion from a pop-up (text completion can also kick in automatically after a delay in typing, but I found that a bit overwhelming in normal use). This is probably mostly helpful for programmers, since BBEdit provides language-specific expansions pulled from the current document, nearby documents, clippings, and other sources. BBEdit's built-in language support is also reportedly improved, particularly for Ruby, JavaScript, HTML, and Python.

For sysadmins, BBEdit can now read and write bzip-compressed files (.bz2) such as Leopard's log files, much as it could already work with gzip-compressed files. And last, but by no means least for those of us who write for a living, BBEdit windows now feature a constantly updated character, word, and line count; clicking it toggles between counting for the document and the selected text.

Upgrade Details -- Upgrades for registered customers of any previous commercial version of BBEdit cost $30. New copies of BBEdit 9.0 remain priced at $125, and the educational price remains at $49. The program is available immediately; there's a fully functional 30-day trial version that's a 15.4 MB download. It requires Mac OS X 10.4 or later, and is a universal binary.

�

Copyright � 2008 Adam C. Engst. TidBITS is copyright � 2008 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.

28.08.2008 21:23:03 - TidBITS

Hard link

TidBITS Watchlist: Notable Software Updates for 01-Sep-08

• Coda 1.5 from Panic is a highly significant update to the single-window Web authoring tool. The most notable new features include support for the Subversion version control system, the capability to search for text across multiple files, custom Web books for your favorite online reference pages, and improvements to the text clipping feature. Support for AppleScript has been expanded, a "Reverse Publish" feature downloads remote items, and tabs now indicate whether files are local or remote. There are numerous other changes and bug fixes in the program; be sure to read the release notes. ($99 new, free update, 19.9 MB)
• RapidWeaver 4.1.1 from Realmac Software beefs up the WYSIWYG HTML authoring tool with support for Leopard's Quick Look feature, an automatic resizing option for dragged-in images, and easier publishing of Web sites to MobileMe. There are a number of other bug fixes and minor improvements. RapidWeaver 4.x requires Mac OS X 10.5 Leopard. ($79 new, free update for 3.6 and 4.0 users, 33 MB)

�

Copyright � 2008 Adam C. Engst. TidBITS is copyright � 2008 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.

27.08.2008 00:49:44 - TidBITS

Hard link

Hot Topics in TidBITS Talk/25-Aug-08

Leopard - Microsoft Office Issue -- After running a system update, Leopard wants to run the demo version of Microsoft Office instead of the registered version. (6 messages)

Archiving a Time Capsule -- Archiving a Time Capsule drive seems to work fine at first, then becomes unbearably slow. What's the holdup? (2 messages)

.Mac Slides are missing after iPhoto Update 7.1.4" -- MobileMe no longer offers the capability to share photos with others as a screen saver, but existing .Mac slides still appear in screen savers. (14 messages)

More Photo Backup Options While Traveling -- Readers share more thoughts about backing up digital photos. (2 messages)

Why I Hate the Eye-Fi Share Wireless SD Card -- Adam's experiences with the Eye-Fi Share card elicit one solution to a problem as well as other readers' experiences. (10 messages)

Using an iPhone when I drive -- A reader wants to talk with others on his iPhone while driving - without endangering himself, of course. TidBITS Contributing Editor Mark H. Anbinder covers some devices that are built into new Audis. (4 messages)

iWeb and MobileMe question -- Updating a Web site created on one machine proves tricky from a new laptop. (6 messages)

iPhone Ver 2.0.2 "Bug Fix" -- Who knows what the iPhone 2.0.2 bug-fix release offers? Not us, which is why we can poke fun at Apple, as well as the "MobileMess" situation. (6 messages)

Cleaning out IMAP mailboxes -- What options are available for managing the size of IMAP mailboxes from Mail? (3 messages)

Office 2008 updates won't install -- Readers have trouble installing the latest Microsoft Office updates and discuss what's changed in the suite. (4 messages)

Wine with Bento -- Charles Maurer's article on managing his wine collection with Bento brings to the table discussion of tools to catalog other items such as books and music. (6 messages)

MobileMe Web Interface Insecure, But Other Apps Get It Right -- Readers discuss the security aspects of MobileMe following Rich Mogull's article. (3 messages)

Flash Problem -- After years without fail, suddenly Flash refuses to work correctly on a reader's computer. JavaScript might be the culprit. (2 messages)

I want to say goodbye to Outlook -- It's hard to unshackle oneself from Outlook, but there are alternatives. (3 messages)

�

Copyright � 2008 Jeff Carlson. TidBITS is copyright � 2008 TidBITS Publishing Inc. If you're reading this article on a Web site other than TidBITS.com, please let us know, because if it was republished without attribution, by a commercial site, or in modified form, it violates our Creative Commons License.

25.08.2008 11:12:25 - TidBITS