Solipsism Gradient

Things are going well. I now have some confidence that I’ll be able to show a working alpha of XRay II at WWDC. Details later…

Also, I found this EgoSurf thingy on Mike Zornek’s blog. It’s some sort of link rank, so here it is without further warranties:

Since yesterday, we’re safely ensconced at a nice hotel in downtown San Francisco, where we’ll stay for 4 weeks – leaving just after WWDC.

The trip up to Corvallis (OR) was marvellous, especially the visit to Crater Lake. It’s the prettiest lake I’ve ever seen, and I’ve seen quite a lot. All this took a little more time and energy than we’d budgeted for, and after visiting with some friends we passed up a chance to see the famous DaVinci Days Festival. Instead, we opted to just walk around the beautiful Oregon State University campus, which was well worth the visit.

Going south the next day we opted for the more scenic 101 route (instead of the 5, which we’d driven up on), and it also was great. The Pacific shore is always beautiful and we also had an opportunity to revisit Ferndale, where we’d been on a previous Los Angeles-Vancouver trip.

So, everything’s settling down and for the next 3 weeks I’ll try to do some extra work on XRay II. Hopefully I’ll have a working alpha to show off at WWDC. Or at least a T-Shirt…

In a motel in Ashland, Oregon, where we’ve been visiting friends and having an excellent time.

The trip started out on a quite negative note – our first flight (CFG-GRU) was over two hours late, making us miss our connection to Dallas. We usually never book connections so close, in order to forestall this sort of thing, but our travel agent, who’s aware of this, was on vacation and we changed (temporarily) to another agency. Turns out all flights in the chain were a few hours late except for that most important one, which we missed by30 minutes. So the airline had to put us up in a hotel and, early the next day we went to San Francisco on the red-eye flight starting at New York.

To cap this, when we went to get our rental car, we were informed our reservation had been canceled by the travel agency – strangely enough, not by ours, but by yet another one we never use. After some negotiations with the manager we were informed they were all out of compacts, but we could get a larger car at a slight price increase. OK, reasonable enough…

…but when we got to the parking garage the attendant pointed at an empty lot and said all those cars had already been rented out! So back to the rental office… where after some more waiting we were issued a Buick Lacrosse GNX (GLX? VGX? VGA? something like that). With leather seats and other knicknacks, and most usefully, a GPS locator, which proved invaluable in our sidetrips.

We drove straight up Interstate 5 to Ashland and stayed at a motel near the intersection with Route 66. Ashland is a marvelous little town – lots of greenery, nice shops and very friendly people. We leave today for Corvallis, which lies northwards, but I’ll give some more details tomorrow.

All’s packed and ready for our trip to San Francisco (with a shorter visit to Oregon). We’ll be home after WWDC. I’ll be online most of the time, I hope. More as it happens!

I’ve finally solved a vexing problem that has been affecting version checks for my software.

Basically, checking for updates inside of XRay and Zingg! asks my webserver for a .plist file which contains the latest versions of everything, along with a brief message. On the server, however, this is actually a PHP script which also stores the user’s system version – which is appended to the URL – into a small database.

Since I changed over to DreamHost, my server has been set to gzip everything it sends if the receiver is capable of decoding gzipped files. However, for some time – not sure when that changed – this has messed up my version checking, and users would get a “website was unreachable” error. I did get some reports about this every couple of months, but always had attributed it to a network glitch somewhere… until I tried it myself and got consistent errors.

I read the .plist file directly using +[NSDictionary dictionaryWithContentsOfURL:]. Some combination of Cocoa, php and server parameters now causes the result to be gzipped, and NSDictionary doesn’t understand that format. Anyway, once I figured it out, I had to find a way to turn gzipping off for this particular file only, as I can’t change all the old software versions that are out there.

So, for now, adding this statement at the front of the php part of the file solved it:

header('Content-Encoding: UTF-8');

Strangely enough, rfc2616 says:

The Internet Assigned Numbers Authority (IANA) acts as a registry for content-coding value tokens. Initially, the registry contains the following tokens:

gzip…

compress…

deflate…

identity The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept- Encoding header, and SHOULD NOT be used in the Content-Encoding header.

…and that’s it. No “UTF-8” is mentioned, so why is it working now? I tried “identity” (before seeing the SHOULD NOT comment) and it had no effect at all. I suppose I should try to debug this on my local server adn see where the problem lies, but time is short…

I don’t plan to use this method in XRay II, so it’s not urgent. I’ll probably use Andy Matuschak‘s Sparkle, of which I’ve had good references.

Posted by gracion:
AppleScript – good! Yes, I’ve used SuiteModeler for a couple of projects and it’s invaluable.

How about a “Save changes as AppleScript” command? After setting a creator, permissions, etc in one file, this would create an AppleScript that is ready to use on a batch. You’d have to track the changes of course (maybe as part of your undo module), but this might be very useful.

For example, Stone Software’s terrific Create page layout software has this kind of command – You can actualy save a document as an AppleScript. I think that’s more useful (and easier to implement) than recordability.

The other thing that’s important is to have a good object model – it takes some study to grok this area of script support, but think of the extra endorphin kick from learning all that

Yes, AppleScript can be very frustrating to write in. It’s really not one language, it’s N languages, where N = the number of AppleScriptable apps you use. I pretty much have to find sample code to get terms and syntax (especially coersions) right.

Leonardo Burci wrote:

you might also want to take a look at:

http://homepage.mac.com/donbriggs/

Thanks Leonardo, the #macsb folks also directed me to that page, and I’ll be checking it out.

Posted by Leonardo Burci:
Rainer,

you might also want to take a look at:

http://homepage.mac.com/donbriggs/