Sat 24 Mar 2012
Category : Technology/AirPrint.txt
I bought an AirPrint-capable printer from HP
- the Deskjet 3070 - and I can now send print jobs to it, wirelessly, from every Mac and iOS device that I have in my home. It's the first HP product that I've ever really liked, since the HP calculator that I had in the University, and that, believe me, had been a very very long time ago.
It was actually easy enough to set up - initially, via USB. I only tripped up because the printer seemed to need to be turned off, and then on, to get onto my Airport network. But after that, it turned up on its own on all my Macs, iPhones, and iPads.
If you're using a Lion-based Mac to set up the printer for the first time, you'll need to download the installer from HP
because the one on the provided CD only worked for machines on Snow Leopard. On the other hand, Apple's software update mechanism will automatically download the client printer drivers for you when you set up the individual Macs. No special drivers are needed for the iOS devices. They all just work.
, from Apple, is wonderful. And so is ePrint
, from HP, which goes one step further to allow you to send print jobs to your printer from anywhere on the Internet (with the appropriate security safeguards turned on, of course).
OK, so, a printer to fall in love with. Recommended for small home offices.
Mountain Lion Enablers
Category : Technology/MountainLionEnablers.txt
I've always wondered how Apple's Server Admin app worked, so that it was able to run on any OS X client machine to remotely administer the OS X Server.
I think I've just found my own way of doing that. Let me backtrack a bit.
I've been spending the last two weeks or so figuring out how to replace two Cocoa Foundation API calls - namely, AuthorizationExecuteWithPrivileges and AuthorizationCopyPrivilegedReference - that have been deprecated by Apple, meaning they're going away, soon, maybe even in Mountain Lion.
Without them, my GUI apps wouldn't be able to get the elevated administrator level privileges to change things at the system level.
There's another way to do that, that Apple is promoting - via launchd. And with that buzzword as a start, I meandered through a whole stream of other buzzwords - code signing, SMJobBless, launchd.plists, Mach ports, Unix domain sockets and TCP ports - before realising I've just broken through the muck to reach my very own Holy Grail - the ability to remotely administer the server (and safely at that, at least to a certain extent).
And it's fantastic. So much power. I could salivate at the things I could now potentially do. I was getting jaded at the thought of updating my suite of enabler apps for yet another one of Apple's cats. (And so soon, too, after the last one.)
But now, I'm juiced, thinking about building a version of MailServe that I could run, while on holiday traveling, say, to remotely configure and troubleshoot my server, if it went down.
Of course, these enablers wouldn't ever be allowed in the Mac App Store (because they require elevated privileges). But I'm building them for myself, first of all, and they'll be code-signed by my Apple Developer ID, so they'll still be able to run on Mountain Lion. You just continue to get them from my site. These enabler apps - they have some life left in them, still.