When I buy a new camera one of the first things I do is affix a GGS glass screen protector over the LCD screen. I did this even on my prosumer digital SLR despite its scratch resistant glass screen. The reason why is that while they may be scratch resistant, they also feature anti-reflective coatings that simply do not last the life of the camera. And as that slowly wears away the screen begins to look like it’s lost a battle with sand paper. Not to mention that scratch-resistance does not equate to scratch-proof.

I’m always amazed at how many people buy plastic-film screen protectors (commonly seen on touch sensitive smartphones) that do little if anything to protect the screen. More often than not they occlude the screen as they quickly become scratched. They offer little to no protection from hard objects, and they frequently need replacing (especially given how easy it is to trap air bubbles beneath them).

GGS screen protectors, on the other hand, are different as they are made out of optical quality glass. They are thin, sturdy, and affix tightly to the back of the camera. Once on, they almost appear built into the body (this is where careful application is key). They don’t scratch easily as they are made of glass, and when they do you know you’re investment has been justified.

I’ve personally scratched and shattered a GGS screen protector, and I know without it I would have been left with a potentially ruined screen instead of a cracked $8 investment. The only downside is that when the GGS screens shatter glass shards can fall off despite being laminated. Removal of the broken screen is simple: slide a credit card (or other rigid plastic object) under a side and slowly work your way around until it pops off (if it’s really stuck, warm it with a hair dryer). Depending on how long it’s been in place the adhesive may leave a sticky residue that is easily removed with nail polish remover or a Goo Gone equivalent.

Other brands of glass screen protectors exist, and some even feature anti-reflective coatings that cost 5-10 times more. But none that I have tried are as consistently well reviewed, as minimally invasive, or as affordable as the GGS models. It’s the rare case where the best also happens to be the cheapest.

— Oliver Hulland

[These glass protectors are NOT meant to be used with capacitative touch screens.--OH]

Available from Amazon
$4-$8

Manufactured by GGS (I can’t seem to find a manufacturer’s website, but if you have better luck let me know and I’ll update this)

We’ve shown you lots of ways to free up hard drive space before, but before you go and download disk-visualizing programs, you might want to do a quick search for big files. Here’s how to do it on Windows and OS X. More »

Exercise is often hard enough on its own, but you make it even harder on yourself if you’re not practicing good breathing techniques while you’re working out. Proper breathing delivers the right amount of oxygen so you can exercise longer with less effort. Fitness blog The Greatist breaks down how to do it for several popular exercises. More »

However, if a track’s “Remember playback position” option is set (and most audiobooks have this set by default) the track’s AppleScript bookmark property will contain the number of seconds that a track has advanced before being stopped. Thus, any track with a bookmark value greater than zero would have been partially played.

Here is an AppleScript that will copy all the tracks in the “Books” library to a new playlist named “Partially Played”. Each time it is run it will update the “Partially Played” playlist.

property nameOfPlaylist : "Partially Played"

tell application "iTunes"
	try
		set thePlaylist to some playlist whose name is nameOfPlaylist
	on error
		set thePlaylist to (make playlist with properties {nam ...

New one from Will.i.am featuring the beautiful voice of Eva Simons produced by Steve Angelo from Swedish House Mafia.

Will.i.am – This Is Love (ft. Eva Simons) (Save Link/Target As…)

It works in applications like:

• Finder
• Mail
• Preview
• TextEdit
• Xcode

and probably in most applications that use the standard UI (the string to be used in defaults appears in AppKit.framework). It doesn’t work in Safari or iTunes.

In Terminal type:

defaults write -g NSScrollViewRubberbanding -int 0

It should work after you relaunch your applications.

To undo this change, run this command in Terminal:

defaults delete -g NSScrollViewRubberbanding

[kirkmc adds: Works as described. I haven’t tested many apps, so feel free to post which o …

I got a lot of great response and questions about my post with the UIStoryBoard. This means people are interested in using it, and I’m not good with explaining things.

I did combo this drill down with a sorta complex core data model and assumed this was setup before handing off objects to each subsequent class. I’m going to nix the core data in favor of a simple input, but we are going to keep music on the table!

Lets start here : UIStoryBoardDrill.zip

This Xcode project will start you out with some plist data that is a nested list of music genre, artist, album, song. At the same time not to complicate the ViewControllers on how it handles these different tiers the data is only nested as a “NSString name” , “NSArray items” pair. This way we constrain straight on the loopback of the table segue.

First take a look at the “Auto” side of this app, this table view controller uses the cells prototype push outlet to auto loopback to the controller again. Because this dose not utilize the didSelectRowAtIndexPath: (or to be clear) this does call but, performs the segue regardless. This practice will make use of the sender value in the prepareForSegue: to identify which cell was clicked on. Realize we are not making a decision where to go next, thats already happening via the segue, we are only deciding what to take with us. We send some values to the next view controller that is another instance of this current one, but is not this exact one. And the view controller is then stacked in the navcontroller and is now only aware of the sub-array we handed down to it.
This auto drilling can be a little limited because of the way we always drill into the same view controller class type. But! if you want to explore here, I suggest you make another cell prototype with a different identifier and a different segue outlet, and use it at your desired tier.

The “Manual” side takes on calling segues from code and needs the fake UIBarButtonItem to create the loopback segue. This little trick will let you define segue identifiers and then let you decide with directing to take with the call to performSegueWithIdentifier: The other important thing is to know what object you want to send along here as the sender. The cell is no longer the sender that is triggering the segue, didSelectRowAtIndexPath is and we could likewise send the UITableViewCell or filter it down to the object we are after. This is the place I test for the data nesting and chose to end the drill down. Calling the different segue will push over to the details view, but the stack of drills downs is still managed by the navcontroller.

Good luck and happy storyboarding.