Scriptable Applications: iPhotoiPhoto is currently at version 5. AppleScript is not long for this world.
iPhoto version 2 offers easy control and automation via AppleScript.
Monday, December 26, 2005
AppleScript - going the way of the Newton?
Apple's main page for scripting iPhoto has a missing image icon at the top and leads with this text:
Sunday, December 25, 2005
Bluetooth problem with managed user in OS X
Weird. I disable Bluetooth on my iMac. Don't need it. Lately the kids session (managed user) was running very slowly. Bluetooth (blued process) was sucking resources. Turns out it was enabled in that session, even though that user can't alter network prefs. The menubar icon showed bluetooth was on. I disabled it.
Session is now useable, but still a bit sluggish. Odd. I suspect a glitch; I don't think Apple thoroughly tested how things work with a limited-privilege user.
Session is now useable, but still a bit sluggish. Odd. I suspect a glitch; I don't think Apple thoroughly tested how things work with a limited-privilege user.
Spotless: Beat the Spotlight beast for a mere $8 US
Spotless is a $8 OS X utility that lets one delete spotlight (oh wretched implementation) indices and disable spotlight indexing.
In theory Spotlight has a mechanism for excluding drives from indexing. In practice it doesn't work. OS X is perpetually trying to index an external backup drive -- no matter how often I tell it not to. Spotless claims to have disabled that indexing and to have deleted the files.
Unless 10.4.4 finally fixes that blasted bug, and assuming my problems with that drive resolves, I'll happily register spotless.
Oh wretched Apple that three bug-fix releases of the 10.4 have not fixed this problem.
In theory Spotlight has a mechanism for excluding drives from indexing. In practice it doesn't work. OS X is perpetually trying to index an external backup drive -- no matter how often I tell it not to. Spotless claims to have disabled that indexing and to have deleted the files.
Unless 10.4.4 finally fixes that blasted bug, and assuming my problems with that drive resolves, I'll happily register spotless.
Oh wretched Apple that three bug-fix releases of the 10.4 have not fixed this problem.
Friday, December 23, 2005
Emergency fixes for bad photos: Putting Photoshop to good use
This MacWorld article relies on Photoshop for most of its fixes. I liked it because it puts some moderately advanced image editing features in a problem solving context: Macworld: Feature: Emergency fixes for bad photos. Once I buy Aperture, it will be interesting to see how many of these fixes can be implemened in Aperture. The thing I most need to learn is how to rescue underexposed regions without blowing out highlights. I hate to think I have to buy Photoshop Elements, it's a notoriously ill-behaved OS X application (won't install/run except as Administrator, an egregious flaw).
Aperture: Perhaps the best review so far
Aperture Review < Main < Frostbytes.com is evolving as the author, a professional photographer, uses it in his work. He leads with an issues list that feels reasonably comprehensive, then concludes he's pleased with his purchase. The good outweights the bad, the bad looks fixable, and the alternatives aren't so great.
I'm thinking I may move to Aperture in the springtime.
I'm thinking I may move to Aperture in the springtime.
Thursday, December 22, 2005
Import Microsoft Access tables into Filemaker Pro
(For related comments on FMPro 8, see my review.)
This is pretty obscure. The official documentation, Querying an ODBC data source from FileMaker Pro, isn't all that helpful.
If you're ever stuck with this problem, here are some tips.
First create an OBDC data source pointing to the Microsof Access file you're importing from.
This is pretty obscure. The official documentation, Querying an ODBC data source from FileMaker Pro, isn't all that helpful.
If you're ever stuck with this problem, here are some tips.
First create an OBDC data source pointing to the Microsof Access file you're importing from.
1. In XP's control panel you'll find something called 'Data Sources (ODBC)'.Now, in FileMaker choose File Open:ODBC source then ...
2. Open it and create a new data source, choose Microsoft Access driver.
3. In the driver dialog name the source then use the Database select dialog to select it.
1. Select the data source you create above.Wouldn't it be nice if FMPro could just import from the file directly?
2. Enter username and password for Windows account.
3. Write SQL (for an entire table just do "select * from table_name"). Yes, that's not very user friendly. FileMaker is not the program it once was.
4. FMPro imports the Access data. In my experiment everything came in as text, except a boolean that was translated to a number. Dates in Access were imported as text. The latter didn't impress me.
Subscribe to:
Posts (Atom)