Two popular techniques to pass references to objects from one view to the next are to create properties in the Application Delegate, or to continue to pass references from one view to the next like a relay race passes a baton from one runner to the next using a series of carefully placed update methods making for an allocation nightmare and increase the opportunities for memory leaks or the hard to track down crashes. Sometimes this need in programming is referred to as implementing Global Variables. There is also a well established design pattern that can assist with this need as well, it is called the Singleton Pattern.

Singleton Pattern

The Singleton Pattern is a derivative of the Factory Pattern that ensures that one and only one instance of an Object can ever exist. By creating one or more implementations of the Singleton Pattern within a given application, the concept of ‘global variables’ can better be managed through tighter control. This allows for what is called lazy instantiation. If you do not need the variable based on what is going on in the application, then do not ask for or create an instance of one.  In Objective-C, Apple has outlined the recommended technique for implementing the singleton pattern.

Objective-C Singleton Pattern

static MySingletonClass *sharedGizmoManager = nil;
(MySingletonClass*)sharedManager{
  if (sharedSingletonManager == nil) {
    sharedSingletonManager = [[super allocWithZone:NULL] init];
  }
  return sharedGizmoManager;
}
(id)allocWithZone:(NSZone *)zone{
  return [[self sharedManager] retain];
}
(id)copyWithZone:(NSZone *)zone{
  return self;
}
(id)retain{
  return self;
}
(NSUInteger)retainCount{
  return NSUIntegerMax;
}
(void)release{
  //do nothing
}
(id)autorelease{
  return self;
}

But you may find that the following is all that is necessary:

Singleton.h

#import <Foundation/Foundation.h>
@interface Singleton : NSObject {
}
+ (Singleton*) retrieveSingleton;
@end

Singleton.m

#import "Singleton.h"
@implementation Singleton
static Singleton *sharedSingleton = nil;
+ (Singleton*) retrieveSingleton {
  @synchronized(self) {
    if (sharedSingleton == nil) {
      sharedSingleton = [[Singleton alloc] init];
    }
  }
  return sharedSingleton;
}
+ (id) allocWithZone:(NSZone *) zone {
  @synchronized(self) {
    if (sharedSingleton == nil) {
      sharedSingleton = [super allocWithZone:zone];
      return sharedSingleton;
    }
  }
  return nil;
}
@end

Try and keep each singleton’s scope limited to manage only the information that is related to a particular use case and not as a catch-all for all global information across the application. It is probably best to utilize each singleton as a delegate to the information it is responsible for managing, and not use it as a means to gain access to any objects it has associations with. Although on the iPhone, and when being used in primarily a read only or a write seldom implementation, the risk of writing code that is not thread safe increases when utilizing shared objects. Keeping concurrency in mind, and utilizing the singleton as a delegate to the information at hand, one can watch out for multi thread related issues and deal with them in kind. One thing to watch out for would be include updating or setting properties of the singleton from within an implemented perform selector or a notification. If concurrency issues do arise, it may become necessary to synchronize access to certain properties or methods.

No, not the AppDelegate!

So why not just keep adding properties to the AppDelegate? After all, the AppDelegate is a singleton as well and is therefore accessible by invoking the sharedApplication class method. The problem with this techniques is that you end up loading up the application with too much information that may or may not be necessary depending on what functions the user chooses to evoke. It could also lead to longer and longer startup times. Get the application started as quickly as possible, and don’t leave the user hanging for too long.

What about Global Constants?

Keep in mind that this is not the best technique to employ if all you need is a means to define and gain access to Global Constants. The quickest way to do that is to create a Precompiled Prefix Header file and include that in your project. By default, most of the projects generated in XCode that create iPhone Applications will include a file with an extension of .pch. This file will initially look like the following:

#ifdef __OBJC__
#import <Foundation/Foundation.h>
#import <UIKit/UIKit.h>
#endif

One can then add any number of #define statements that will be included in all header files across the entire project.

#define SOME_STRING_CONSTANT @"My Important String"

Conclusion

The Singleton Pattern can be used to make the complex and ugly means of sharing a simple variable between two different views or view controls an easy task. If used sparingly and some basic guidelines are followed as not to bloat the application and create a multi thread nightmare to debug, this technique can be quite useful. Much more so than passing Objects back and forth among views or by breaking the encapsulation of the AppDelegate by assigning it more responsibility than it should have.

References

• Mac OS X Reference Library – Cocoa Fundamentals Guide – Creating a Singleton Instance
• iPhone OS Reference Library – UIApplication Class Reference
• Mac OS X Reference Library – Xcode Build system Guide – Using a Precompiled Prefix Header

I’ll go through how to open the iMac up, just enough to replace the hard drive. There is risk involved with this but if you take your time, you should be just fine. If you want to transfer your data to the new drive before you begin, I recommend using a USB drive adapter such as this one by Apricorn and Carbon Copy Cloner.

Parts Needed

Suction cups: I am using suction cups from our server room floating floor but you can use any kind of suction cups you find at your local store.

Phillips Screwdriver: This is to remove the memory door on the bottom.

T8 Torx Screwdriver: The internal screws require this bit.

Canned Air: This is to remove any dust that may settle on the screen before you reassemble it.

Disassembly

1. The glass is held in by magnets so use your suction cups to pull the glass off the iMac.
   
   
2. Remove the memory door on the bottom of the iMac.
   
3. Remove the Torx screws that are holding the metal case on.
   
4. Pull the metal case off by starting at the top. You will see a connection by the iSight that you need to disconnect. After that, the case will slide right off.
   
5. Now the remove the screws on the sides of the actual LCD screen.
   
6. Gently rock the LCD screen forward from the top and you will see the hard drive behind it. You may need to disconnect the two wires running to the LCD.
   
7. Pull on the back plastic bar  on the left side and it will swing out.
   
8. Remove the heat sensor by pulling off the foam and sensor carefully. Set the foam aside so we can use it to re-attach the sensor to the new drive.
   
9. The drive is ready to be come out by rocking the top out of the frame and then pulling it up.
   
10. Once out, we need to transfer the Torx screws to the new drive.
    

To reassemble, just follow the same steps in reverse. Go slowly and don’t force anything. All the pieces should slide back together without much effort. Some people like to take the LCD screen all the way off and that’s fine. You will need a T7 bit to disconnect the LCD screen from the board and just remember where each connector goes. Before you put the glass back on, use some canned air to blow off any dusk that may have settled on the LCD screen.

The key to a smooth and professional looking launch sequence starts with knowing exactly where the application will land at startup. Some applications start at exactly the same place each and every successive launch, others attempt to preserve the application’s state and launch into the screen where the user last used the application. Keeping this in mind can change the strategy of how the launch sequence is implemented. This includes screen orientation as well as how and even if the status bar it to be displayed.

One may witness flickering of the status bar from blue, to black or from black to blue during the launch sequence. This is mainly due to the fact that there are two places to change the behavior of the status bar. One is hidden in the info.plist file, and the other is typically via code in the Application Delegate’s applicationDidFinishLaunching method. The info.plist configuration is used before the main window is loaded, and the code in the Application Delegate is used during the launching of the main window. The reason one may want to utilize both styles is to take advantage of a full screen splash page, and then enable the appropriate looking status bar once the application has finished loading.

For the purpose of this example application, we will assume that the user state is preserved between executions, and we do not know exactly what the screen will look like when the user enters the application. We will therefore be implementing a full-screen splash view that will have the status bar hidden during the launch sequence. Once the splash view has disappeared, a black opaque status bar will be utilized throughout the application. It is also assumed that the application will launch in portrait mode, and that the first screen the user will see will also be in portrait mode.

Editing the Configuration File

The first order of business is to take care of the status bar. In Xcode, locate the info.plist file for the project. To add an additional property to the plist file, simply select one of the entries and click on the plus tab that appears to the right and select Status Bar Style from the drop down list:

Edit Projects plist File

There are only three different styles to choose from. Try each style out to see which one fits the needs of the application being developed. For this example we will set the style to UIStatusBarStyleDefault.

UIStatusBarStyles:
UIStatusBarStyleDefault — Gray (the default)
UIStatusBarStyleBlackTranslucent — Transparent black (specifically, black with an alpha of 0.5)
UIStatusBarStyleBlackOpaque — Opaque black

If on the other hand the desire is to hide the status bar when the application launches, then yet another property needs to be set. In this case, add the “Status Bar is initially hidden” property to the plist file and be sure to check the box next to the property.

Editing the Application Delegate code

So now that the status bar style is set, and initially hidden, how does one get the status bar to display again? You can actually turn the status bar on and off programmatically via code. This is particularly handy when the need arises to display a full screen view, such as the splash screen this application is utilizing. In the applicationDidFinishLaunching method of the Application’s designated AppDelegate class, add the following line of code to make the status bar visible again:

- (void)applicationDidFinishLaunching:(UIApplication *)application {
    // Override point for customization after app launch
    [window addSubview:viewController.view];
    [window makeKeyAndVisible];
    [[UIApplication sharedApplication] setStatusBarHidden:NO animated:YES];
}

Adding a Default.png Image

Surprisingly, the size of this file is not as important as the naming convention of the file. Default.png is a case sensitive PNG file. The image should be 480×320 according to Apple. Following Apple’s conventions, this image should look like the view that the user will see when the application has launched, and not the actual splash screen.

Xcode provides a mechanism to create a Default.png file from an attached device running the application. From the Organizer window, select the device, click on screenshots and click capture. To make that screenshot your application’s default image, click Save As Default Image. Even though the image that is created includes the status bar as it looked when the screen shot was captured, the iPhone OS replaces it with the current status bar when your application launches. Just to be clear, this is not a splash screen…not yet.

Long Launch Sequences to Varying Views

So far, this is what most applications will implement if they implement any sort of controlled visual experience when the application launches. If you follow Apple’s guidelines, and the image you produce is the first screen that the user will see, all is good. Except, what if the launch sequence is not as fast as the user expects? What if the application preserves state and lands on a different view based on the users last know state? Then this technique is not up to the task.

Photoshop a branded image representing the application and save it as a PNG image sized at 480×320. Do not include a status bar of any kind in the image file being created. Add this image file to the project. Now the application sort of has a splash screen, through a misused implementation of the Default.png file. To correct this, simply add an image view as a property to the App Delegates header and create it as follows:

    splashView = [[UIImageView alloc] initWithFrame:CGRectMake(0, 0, 320, 480)];
    splashView.image = [UIImage imageNamed:@"Default.png"];
    [window addSubview:splashView];
    [window bringSubviewToFront:splashView];

At this point, the image view is utilizing the exact same image file that was created in Photoshop. There’s no chance of the initial view being different than the Default.png file at this point. The one remaining problem is the timing of when to remove the image view from the subview. This can be handled in one of two ways…

Controlling the Duration of the Splash Screen

The first option is for those with quick startup times that just want a splash screen. In this situation, create a method to remove and release the splash view, then calling that method via a timed perform selector call as follows:

    [self performSelector:@selector(removeSplash) withObject:nil afterDelay:1.5];

The removeSplash method does just that, removes the image view from the subview and releases the object.

    -(void)removeSplash;
    {
      [splashView removeFromSuperview];
      [splashView release];
    }

The second method uses the same remove splash method, but relies on the built in event management to trigger when the method gets called.

    [[NSNotificationCenter defaultCenter] addObserver:self
          selector:@selector(saveClaim:)
          name:@"RemoveSplashScreen"
          object:nil];

Now all that needs to be done is to post the notification from anywhere. This technique is particularly useful if the reason that the launch sequence is taking a long time has nothing to do with code that was implemented in the App Delegate.

    [[NSNotificationCenter defaultCenter]
          postNotificationName: @"RemoveSplashScreen"
          object: nil];

This technique can be employed from anywhere within the application. Removing the observer after the fact may avoid crashes if there is an opportunity for this notification to be fired multiple times. Releasing an object when no object it there to be released can lead to troublesome crashes to track down. The quick and dirty is to use the delay on the performSelector call.

Conclusion

And there it is, a splash screen that conforms to Apple’s guidelines. No hidden APIs, no hacks, no special sauce. A simple, straight forward approach to making the initial interaction with the user as pleasant as possible.

References:

• iPhone OS Reference Library UIApplication Class Reference UIStatusBarStyle
• iPhone OS Reference Library iPhone Development Guide Capturing Screen Shots
• Mac OS X Reference Library Threading Programming Guide Cocoa Perform Selector Sources
• Mac OS X Reference Library NSNotificationsCenter Class Reference

We’ve all been in the situation. Your mother calls you with a computer problem and you know it’s going to take at least an hour to walk her through the steps over the phone. Then she yells at you when you sigh out of frustration.

If you have parents who use Macs then these calls happen less often but they still happen and usually at the worst time. This is how I use iChat and Snow Leopard’s Screen Sharing app to remotely control my parents computer and quickly solve their dilemmas.

Apple’s Screen Sharing is based on VNC and it is very powerful. Generally to remotely control a machine, you need to configure the host machine and open ports on the firewall. The genius behind Apple’s solution is that they use iChat to initiate the session and no other configuration is necessary. If you can talk them through setting up iChat for their account, you’re home free.

Of course you’re going to need a compatible iChat account such as a .mac, AIM or Gmail account. I use Gmail since it’s free and my parents raised a frugal son. They also have a Gmail account so we’re on the same page as far as chat providers go. If you’ve never used iChat with them before you need to help them setup their account. Apple has made this pretty simple but if you can do it in person it’ll be easier on everybody. Next time you’re over, quickly setup iChat with their info so in the future you can get right into it.

The bonus of using audio and video to help them makes this a rather pleasant experience. If you have the hardware, get a video chat going and start the magic. When you’re in iChat, make sure you see them in your Buddy List. If not, do the following.

1. In iChat logged in under your Gmail account, add them as a buddy.



2. If you both have a video icon, start up a video chat. You can also do an audio chat or just talk to them over the phone.



3. Now request to take control of their screen by going to either the Buddies menu or the Start Screen Sharing icon in iChat.



4. They will see a request dialog similar to this where they can Accept or Deny your offer.



5. After they accept your Screen Sharing request, you now have control of their machine. Fix their issues and they will think you’re a god.
6. When you’re finished you can end the Screen Sharing session by clicking the iChat icon in the menu bar and selecting End Screen Sharing.

This is such a great tool that you have try it out to see how slick it is. I thank Apple for making such a perfect solution. No opening ports on their router or third-party software to install. Just a clean simple solution utilizing something you probably already use with them. Give this a try the next time you get that dreaded phone call and I promise you’ll be thankful.

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Finding a Niche in the Electric Vehicle Market
• A 2011 Green IT Forecast

You get a new Mac and even though you know you should, you don’t want to start over from scratch and reload the whole system. To make matters worse, you have Boot Camp installed and really don’t want to start over on the Windows side. So, here’s how you can image both OS’s to a new machine using free tools.

You need to download the Carbon Copy Cloner and Winclone software packages. CCC was created by Mike Bombich and has been used for years to clone Mac machines. It is the standard tool for this job. Winclone is made by Twocanoes Software and this is what we will use to image the Windows Boot Camp partition.

Let’s Get Started

Lets start off with Winclone first. After you install the app and run it for the first time, it will tell you it needs to download and install NTFSProgs. Click the download button and install NTFSProgs by following the wizard. The NTFSProgs software allows Winclone to properly read NTFS formatted partitions.

Now run Winclone again and select your Boot Camp partition in the Source dropdown. You can write some notes in the Item Description field if you’d like. When you’re ready, click the Image… button.

It will prompt you for a name and location to save the image to.

Now we wait for Winclone to do its work. When it’s completed, this dialog box will appear. You can now quit Winclone.

Carbon Copy Cloner is a little different in that it can image from your old machine to your new one using a Firewire or network connection. For this tutorial we’ll use the Firewire method. Setup your new machine and connect a Firewire cable between the two Macs. On the new Mac, hit the power button and hold down the “T” key on the keyboard until you see the Firewire symbol on the screen. This boots it into Target Disk Mode where it will act as if it’s just an external Firewire hard drive. On your old Mac we need to launch Carbon Copy Cloner. Your Source Disk drive is your local drive and the Target Disk is the Firewire drive. Click the Clone button and off we go.

After CCC is finished, reboot the new Mac and it should be identical to the original. From here on out, we are done with the old machine. When we imaged the Mac partition, we also brought along the Winclone image with it so now we can restore that image on our new Mac. Launch the Boot Camp Assistant in the utilities folder to create a new Windows partition.

Launch Winclone and click on the Restore tab. Click the Select Image button and browse to your Windows image. Mine was in the Documents folder.

Restore it to your newly created Boot Camp partition.

You know have a new Mac that’s a complete clone of your old one, Boot Camp and all. Windows will probably complain, as it always does, about drivers. Just insert your OS X DVD while in Windows and let it re-install the Boot Camp drivers for you. Of course, starting over from scratch is cleaner but sometimes you just don’t have the time. Proper cloning offers a reasonably quick solution.

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Why iPad 2 Will Lead Consumers Into the Post-PC Era
• The Near-Term Evolution of Social Commerce
• Content Farms: The Players, The Benefits, The Risks

Thinking others might be feeling the same way I quickly threw together this Google Quick Search Box plug-in (ZIP, 742kb) that will let you send searches to reference sources for HTML, CSS, JQuery, PHP, MySQL, Python, and WordPress. You can start the query by entering text directly into QSB or by selecting text within Espresso itself, or any other application for that matter.

It seems like a simple feature hardly worth mentioning but I’ve found that having the option to quickly check up on the details of a particular function, element, declaration, etc. is an essential part of the way I work. In Coda you can add your own reference books directly into the application associating each one with a particular code type, e.g. php, css, javascript.

While in the code editor you can then select some text and choose “Look Up in Reference Books” from the contextual menu which will execute a search at the associated reference source using the text as the query. Unfortunately, one of the drawbacks to this approach is that you can’t quickly send queries to more than one source for a given code type. Nevertheless, over time I’ve really become dependent on being able to run these quick lookups.

I figured the best way to close this gap in Espresso was by building a QSB plug-in. To install the plug-in just add the codex.hgs file into your ~/Library/Application Support/Google/Quick Search Box/PlugIns directory. Once installed you will need to restart QSB in order to access the new actions.

Once you have everything working, just add any text into QSB (don’t forget to prepend with a space) press “tab” to pivot to an action and select a codex to search. Typing “codex” will bring up all available sources or you can just type the name of a specific source, e.g. WordPress, JQuery, and so on. Once you have selected the codex to be searched, press return to send the query. Alternatively, you can also start by sending text to QSB from within Espresso, or whatever other editor you’re using, by selecting the appropriate bit of code and choosing “Send to Quick Search Box” from the services menu.

With the theory that a picture is worth a thousand words I recorded this quick video demonstrating the plug-in in action.

Now that I have quick access to all my reference books I think I’ll be switching over to Espresso full-time. I’d be interested in hearing if anyone else has recently made the switch to Espresso and if so what they’ve been missing the most.

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Copenhagen Boosts Tech Companies’ Green Plans
• Why iPad 2 Will Lead Consumers Into the Post-PC Era

Computers get dirty, especially their human interface surfaces — keyboards and pointing devices.

In some instances, dirt can even affect input device performance as well as appearance. Some time ago the faithful SlimType gave me a scare when the F and W keys stopped responding properly. A keystroke would register only when the key was pressed more firmly than usual, and the subtle over-center click of the SlimType’s scissors keyswitch mechanism was missing — the malfunctioning keys feeling “numb” and offering higher than normal resistance.

The medicine that time proved to be blowing out the accumulated crud beneath the key console with compressed air. I successfully used an automotive shop compressor with a blow gun. For more cautious folks, or those without convenient access to a compressor, one of those little aerosol cans of compressed air used for cleaning photography equipment could do the trick.

But sometimes a bit of compressed air isn’t enough. So, here is our guide to cleaning everything from mice to laptops.

Getting Started: Apple’s Cleaning Recommendations

Apple has posted a Knowledge Base article covering recommendations and guidelines for cleaning Apple computers, displays, or input/ peripheral devices. Much of its advice should be common sense, such as before you start cleaning:

1. Turn off your Mac.
2. Unplug the power cord from the wall or power strip.
3. Remove the battery (from products with removable batteries such as some Apple portables or from wireless devices such as mice and keyboards).
4. Disconnect all external devices from the computer.

Other warnings some users might be less likely to think of are:

• Don’t use window sprays or cleaning products containing ammonia, chlorine, or abrasive ingredients.
• Don’t use rough towels or cloths to dry the plastic.
• Don’t spray cleaner directly onto your computer. Liquid could drip inside the case and cause an electrical shock or malfunction.
• Don’t use excessively damp cleaning wipes.

If more than dusting is needed, use a lint-free cloth slightly dampened to wipe away dirt or grime. Don’t over-wet the cloth. If you can squeeze drips of water out by wringing, it’s too wet.

Solvents and Cleaners

Plain water may not be effective on oils or grease residues, in which case a stronger agent will be needed. Try iKlear or mild detergent first.

Cleaning Laptops

Instructions specific to Apple laptops include not using isopropyl alcohol on bare LCD panels (or any type of alcohol or ammonia-based glass or window cleaner, I hasten to add). Use only a damp, soft, lint-free cloth or purpose-made, Apple-approved LCD cleaning product like iKlear.

Aluminum portables are best tackled with a damp, soft, lint-free cloth. Apple says it’s safe to use 70 percent isopropyl alcohol on them (I personally wouldn’t) or iKlear. Remove surface dust or loose dirt gently with your bare hand before proceeding with cleaner and cloth. After cleaning, dry the aluminum with a soft, lint-free cloth.

For plastic portables, the same applies as aluminum, but I would recommend a gentler, damp-cloth approach first and reserve the heavier-duty agents for stubborn stuff. As with the metal machines, remove any loose surface dirt gently with your bare hand before proceeding with cleaner and cloth. After cleaning, dry the plastic with a soft, lint-free cloth.

For the new unibody MacBook’s non-slip plastic coated aluminum bottom case, Apple recommends using a 3M Gray Microfiber or soft dye-free, lint-free cloth for cleaning, once again giving its blessing to 70 percent isopropyl alcohol or iKlear on the bottom case.

Mouse Cleaning

Mice get dirty. When your mouse becomes covered in fingerprints or its surface is soiled, you can gently wipe it with a clean, lint-free cloth. If necessary, moisten the cloth using plain water, making sure not to over-saturate it, and be mindful that the mouse’s internal electronic components may be damaged if water seeps or drips inside.

With Apple’s Mighty Mouse, the scroll ball can be cleaned using a lint-free cloth lightly moistened with water, making sure to rotate the ball itself to ensure complete coverage or you can use something like Wet One.

Drowned Keyboard First Aid

Moisture is potential death to electronics, as anyone who’s ever spilled liquids on a computer keyboard or laptop can ruefully tell you. Apple also warns against using solvents like acetone, alcohol, or alcohol-based cleaners on your computer, admonishing to never spray cleaner directly onto the machine, since liquid could drip inside the keyboard or case and cause an electrical shock (or more likely a component-frying short-circuit and/or residual corrosion).

Should you spill liquid on your keyboard, if it’s thin and clear fluid, immediately shut the computer down, unplug the keyboard, turn it upside down, and drain the liquid out, let it dry (inverted or on edge is best) for 24 hours at room temperature, after which it may or may not recover. If the liquid is greasy, sweet, sticky, or acidic, you’re likely out of luck. I ruined a MacAlly iceKey scissors-action keyboard a while back by sloshing diluted Grapefruit Seed Extract (extremely acidic) on it twice in a week — the only times I’ve drowned a keyboard in two decades of computer use. We disassembled the keyboard and cleaned the circuits, but corrosion had set in.

Computer Disinfection

With the H1N1 flu pandemic, computer contact surface disinfection has moved to the front burner, especially for machines accessed by multiple users. Apple support also has a Knowledge Base article entitled How To Disinfect The Apple Internal Or External Keyboard, Trackpad, And Mouse. The article recommends, in addition to regular cleaning of your computer and input devices, that disinfecting them may be desirable, noting that,”Multiple people using the same computer, people using the computer when they were ill, and the particular environment where the computer is used, are a few reasons you may wish to disinfect areas of the computer that people come into contact with the most.”

Using a mild soap with antibacterial properties will help, but Apple suggests properly disinfecting contact areas with products like Lysol Wipes, Clorox Disinfecting wipes, or Clorox Kitchen Disinfecting Wipes. I would be cautious about using them on the screen however (except for glass-covered aluminum laptop and iMac displays), and would stick with water or iKlear for that. Otherwise, follow the general rules outlined in the regular cleaning instructions above, with a special caveat to not use disinfectant wipes containing bleach, or disinfectant sprays in general.

What are some techniques you’ve used to clean those hard to reach and sensitive areas of your gadgets?

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Why iPad 2 Will Lead Consumers Into the Post-PC Era
• A 2011 Mobile Forecast
• Green IT’s Q4 Winners: Wind Power, Solar Power, Smart Energy

So you’re loving your brand new Magic Mouse but are missing the ability to activate Expose and Spaces right from the mouse? Not to worry, we’ve got you covered. Using SIMBL and a neat little preference pane called MultiClutch, we can map our own custom shortcuts to the left and right swipes coming from the Magic Mouse and have them activate Spaces and Expose instead of navigating forward and back.

Getting Setup

The first thing we need to do is to get MultiClutch up and working in a 64-bit Snow Leopard world. MultiClutch, like a lot of apps relying on InputManagers, kind of got gimped when the new big cat showed up. Luckily though, a recent fork in the project now allows for its plugin to be loaded through the latest SIMBL release.

You can find some detailed instructions on how to get MultiClutch up and running from the source of the new plugin, but essentially what you need to do is:

• Install the original MultiClutch application.
• Install the latest version of SIMBL.
• Download the forked version of the MultiClutch plugin and load it into the SIMBL plugin directory at /Library/Application Support/SIMBL/Plugins.
• Go in and remove the old version of the MultiClutch plugin from /Library/InputManagers.

Adding Shortcuts

Once you have MultiClutch up and running, open its preference pane and add new gestures for Swipe Left and Swipe Right and then assign them each key commands. If you’re configuring for use with Spaces and Expose you’ll have to use one of the function keys. You may have to do some shuffling around depending on what function keys you already have mapped. I used F1 and F2 as they weren’t already mapped to anything.

Then just go into your preferences for Expose and Spaces and set Activate Spaces and All Windows to the corresponding key command you used in MultiClutch. Since we’re using SIMBL you’ll have to quit and relaunch any applications that were already active when we started in order for the system to pick up our new shortcuts when that application is active.

Caveat Emptor

Obviously this is not an ideal solution, and ultimately it would be best for Apple to build in some customization options for Magic Mouse gestures right into the Mouse preference pane. As with anything that is this hacked together, your milage may vary, but I’ve been using it for a couple days now and it’s working great. On the whole I really love the new Magic Mouse but not having my Expose and Spaces was a bit of a deal breaker for me. Hopefully this will at least be able to tide us over until a more solid solution comes along.

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Why iPad 2 Will Lead Consumers Into the Post-PC Era
• The Near-Term Evolution of Social Commerce
• Content Farms: The Players, The Benefits, The Risks

I’ve been playing around with Google Quick Search Box lately and am especially enjoying this services plugin from Martin Kuhl which lets you activate and pass input to OS X services right from within QSB.

One snag though has been that services created through the new Automator template included in Snow Leopard leave out some vital bits that limit integration. Luckily, a handy application from Waffle Software called ThisService makes creating proper services that integrate seamlessly with QSB a lot easier than you might think.

Being able to extend the functionality of QSB with OS X services really opens up a lot of possibilities. Grab text or files in QSB and pass them on to your services to do whatever you want with them, like creating a new To Do item in iCal. I’ve been focused recently on replicating functionality that I lost when I made the switch over from Quicksilver and I think that this improved service integration will get me about 90 percent of the way there.

The bad news is that this means I need to whip up a bunch of custom services for myself. The good news is that ThisService makes that task very easy. Just give it a script (AppleScript will do, but if you’re more comfortable with other scripting languages you can use those), define the type and name of your service and click Create Service. ThisService handles all the fiddly Cocoa bits and spits out a completed service into your ~/Library/Services directory where QSB will see it and serve it up as an available action when appropriate.

Actually writing your AppleScript will likely be the most complicated part, which is why ThisServices comes bundled with some handy starter scripts to put you on the right path. They also make a number of example scripts and services available for download from their site. The scripts don’t need to be complicated. For example, here is the one I use for adding To Do items in iCal:

on process(input)
tell application "iCal"
tell calendar "work"
make new todo at end with properties {summary:input}
end tell
end tell
end process

If you wanted to get fancy you could pass additional properties like the due date, priority, etc., but just getting a new item into the list is all I need.

Once you have your service setup accessing them through Quick Search Box is as easy as can be. Because showing seems to be more useful than describing, below is a quick little video clip of the To Do service in action. What kind of services would you like to have? Share your thoughts in the comments.

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Why iPad 2 Will Lead Consumers Into the Post-PC Era
• The Near-Term Evolution of Social Commerce
• Content Farms: The Players, The Benefits, The Risks

Although I’ve been supporting Macs since they came out in 1984 (when I was in high school), I haven’t received any “formal” training. It has mostly been learning by doing, reading the occasional book and now of course, TheAppleBlog. Does formal certification really make a difference as a technician? You tell me.

Recently I got into an argument with a vendor that somehow thought a technician who first started repairing Macs sixth months ago trumped my 25 years experience. Did certification make this person a better technician? Having done quite a bit of hiring myself, I’ve too often found that certification only verifies your ability to take a test and may not have bearing in the real world.

Now that the market has changed and everyone seems to be competing for scarce resources, perhaps a certification would be an additional edge? What’s the business strategy for independent Mac technicians wanting more? The answer took a lot of research — even Apple wasn’t able to answer my questions — so learn from my journey.

Credit goes to both Brian Best of BestMacs and Doug Hanley of MacTEK Training, because without them I wouldn’t understand the alphabet soup of ACSP, ACMT, ACTC, ACSA, AASP, ACN and more. Didn’t we all become Mac users to avoid mysterious terms? As many of you know, the ease of the Apple user interface is equalled only by the frustration of trying to understand Apple’s certifications programs. Figuring out this path was much harder than any video game I’ve ever played, but a “game” may be the best metaphor to describe the process.

The Game

You begin the “game” as a general Mac user. The three worlds you’ll generally see in the game are IT, Pro Apps, and Sales. As an IT person maybe you have skills, maybe you don’t. Nothing stops you from simply repairing Macs on your own, unless you do things that specifically void the warranty and you get caught doing so. You do not need permission per se from Apple to work on Macs. Many folks are happy at this level collecting coins one by one, but you can’t proceed any further unless you get a certification — the key that unlocks the next level in the game.

The first certification most go for is Apple Certified Support Professional (ACSP) which used to be known as an Apple Certified Help Desk Specialist (ACHDS). This certifies your ability to understand the operating system and is earned based on the OS version. Therefore, you are an Apple Certified Support Professional in 10.5 (or soon 10.6). Each OS requires certification, but your certification does not expire. Therefore, if you are a ACHDS in 10.3, you can call yourself certified without understanding 10.5 at all. Your can take the test without training (many do), self-study via materials from Peachpit, or attend an instructor-lead course at an Apple Authorized Training Center (AATC). MacTek is one of those centers. You’ll take the test at a Prometric testing center and pay around $200. The test takes about 90 minutes or so and you get the results immediately.

Apple Consultants Network

While certification is the means, the end you may be reaching for is the ability to join the Apple Consultants Network (ACN). Joining the ACN requires any Apple certification, such as the ACSP discussed above, or any number of other certifications (described below, though one source says not all certifications are valid, so beware). Keeping with the video game analogy, the ACN is like an entire new area of the video game you want to explore, but the boss that must be defeated first is Apple, and your weapon is a certification!

After getting a certification you can then apply to join the ACN. The application fee is $60 and the actual fee to join is $395 as a sole proprietor. The full requirements are here. You’ll get lots of benefits such as product discounts as well as the ability to network with other Macintosh consultants. As an ACN, Apple store employees may hand out your card to customers in the store. Now your business can really expand as every Apple store customer is a potential customer for you.

ACN membership is great and many stay at this level of the “game” using the ACN membership as a multiplier for their income. However, you still can’t do hardware repairs under warranty nor order Apple parts. As with the video game, you’re stuck at this level unless you explore further and try to defeat the next boss. Apple always controls the rules. Accept it as part of the game. Fail to accept it and you’ll get slapped back to the beginning of the game quicker than you can click the home button.

Server Administration Certification

From this point, you have a couple directions you can go. You can focus on repair and service, or you can focus on server or advanced software administration (many folks will do both). I will discuss the server administration certifications and the hardware services certifications. You can think of each of these as two separate worlds in the game. You can choose one or the other, or explore them both.

The first level server administration certification is another 4-letter acronym: ACTC: Apple Certified Technical Coordinator. In addition to passing the test for ACSP, you’ll face the Server Essentials test. This extends your workstation abilities to servers. An even higher level of certification within the server realm is an ACSA — Apple Certified Systems Administrator. For the ACSA, you’ll need to pass four tests: Server Essentials, Directory Services, Deployment, and Mobility and Security for 10.6 (or Advanced System Administration for 10.5).

Apple also offers the ACMA (Apple Certified Media Administrator) which includes Server Essentials, Xsan, Final Cut Server and as an option, Support Essentials, Deployment, Directory Services, or Final Cut Level 1. Other certifications are not necessarily IT related and are software-focused. That’s a realm I’m not exploring as we chose the IT track at the beginning of the game.

Hardware Repair Certification

Moving on from server administration to actual Apple hardware repair, the primary certification you will earn is the Apple Certified Macintosh Technician (ACMT), formerly the Apple Certified Portable Technician (ACPT) and Apple Certified Desktop Technician (ACDT). This certification means you are theoretically qualified to do warranty repairs on Apple Macintosh equipment. The skills required for ACMT are those of hardware repair and software troubleshooting. You don’t need an ACSP to be an ACMT, but many people earn both. The educational process for hardware repair is more intense and it’s less likely you’ll pass the test without some training. At this level, you can also go to an AATC and pay about $4,800 for both the hardware and software aspects of the course, or your can purchase self-study materials from Apple called “Apple Care Technician Training” for $299.

Apple Authorized Service Provider

Similar to how passing the ACSP allows you to join the Apple Consultants Network, passing the ACMT allows you to enter the realm of an Apple Authorized Service Provider (AASP). You may not automatically become one though, and only AASP’s get reimbursement from Apple for warranty work. However, being an ACMT is very helpful if you want to get a job as an AASP. You may also apply to do warranty repairs for your larger organization of over 50 Macs via the Self-Service program. If you want to advance to being able to do warranty repairs for anyone, you’ll face that same boss again, Apple. Note that becoming an ACMT will not necessarily earn you any more money than an ACSA or ACTC. Facing the next boss may be too expensive and too restricting, but if you do want the next level, read on.

Getting to that AASP level is really the final level of the game. You’ll need to have an ACMT on staff and follow stricter requirements than joining the Apple Consultants Network. Generally you’ll need a real store front and not be a one-person operation. Apple grants exceptions (doesn’t every game have cheat codes?), but don’t count on it. Once you have your AASP you can be listed with Apple as a service provider and get reimbursed for warranty repairs.

So I’ve loaded the game and pressed Start. Is certification worth it? What about ACN or AASP? Which training should I go for? Is instructor lead training worth it? Any training vendors willing to sponsor me? What about the self-study programs? Share with me your experiences in the game and let’s develop a definitive guide including “cheat codes.”

Apple-authorized Organizations

ACN (Apple Consultants Network)
What it is: Network on Apple professionals, receives discounts and assistance from Apple, and can be referred from Apple retail stores.
Requirements: Any certification.

AASP (Apple Authorized Service Provider)
What is it: Business that is permitted to do Apple warranty repairs for reimbursement and order parts from Apple.
Requirements: Have an Apple Certified Macintosh Technician on staff, among other requirements.

Certifications

Apple Certified Support Professional: Basic understanding of the client Mac operating system and troubleshooting.

Apple Certified Technical Coordinator: Deeper understanding of the Mac OS, including the Mac OS X Server and Server Essentials.

Apple Certified Systems Administrator: Even greater technical understanding of the Mac OS X Server, including passing tests on Server Essentials, Directory Services, Deployment, and Mobility and Security.

Apple Certified Media Administrator: This is a sister track of the “Apple Certified Systems Administrator” with a focus on the needs of media management, and includes training in XSan or Final Cut.

Apple Certified Macintosh Technician: You can do Apple hardware repairs, both in and out of warranty. Required to start (or get a job with) an Apple Authorized Service Provider, or self-service your large organization.

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

• Why iPad 2 Will Lead Consumers Into the Post-PC Era
• The Near-Term Evolution of Social Commerce
• Content Farms: The Players, The Benefits, The Risks