Converting Mac OS 9 .pict screenshot files to jpegs

The Shift+Cmd+4 key combo is common from all the way back to Mac OS 9 (and maybe earlier?) to all Mac OS X and current MacOS versions and takes a screenshot of a selected area on the screen. On current MacOS versions the file saved to your desktop is in png format (Mac OS X versions around 10.4 saved screenshots in .tiff format), but on OS 9 it’s in a less common .pict format.

By today’s standards the .pict file format is even more unusual as it uses Classic Mac OS file system features called a ‘resource fork‘ and a ‘data fork’. The issue with copying these .pict files from a Classic Mac OS filesystem to a modern file system is described here – when you copy the file you get the ‘resource fork’ but lose the ‘data fork’, in this case losing most of the image file data. When I tried this and viewed or converted the file on MacOS each of the files only has a section of the image, or none at all.

To convert to a jpeg or other more commonly used format today, this post suggests using the Resize! app, which is still downloadable from kstudio.net.

The trouble with this approach is if you’ve already copied the .pict files from OS 9 to a SMB network drive, you’ve already lost part of the file and it won’t convert as expected.

The best option as described in the first post is to convert to a jpeg or gif on OS 9 before moving elsewhere. I’ve seen posts suggesting to use Quicktime Viewer, but the version I have on mg G4 running OS 9.2.2 doesn’t have a Save As or Export feature, not that I could find anyway.

Instead what I found that worked for me was to download GraphicsConverter from Mac Garden here and use Save As changing the file extension to .jpg

Move MacOS Dock between monitors

When using multiple monitors on my Macs I would do this by mistake and thought it was some weird bug 🙂 Turns out, if you pull down your mouse at the bottom of the screen, this moves the Dock to that screen.

Useful when you use multiple monitors, annoying if you do it by accident and don’t know the feature exists 🙂

The spectrum of note taking options for software developers

All software developers should take notes. That’s a given. There’s far too much information we come across daily that it’s impossible to remember everything without taking notes.

Ok, so what approach should you take for your note taking? As software developers, building your own note taking app would be an interesting side project for learning a new language or framework. Before you jump to that extreme though, consider some of the simpler alternatives first.

Going from simpler to more complex, here’s some options:

  • A notebook
  • Index cards
  • Notes on loose sheets of paper, grouped by topic and filed in a folder, binder, or filing cabinet
  • Online note taking app: OneNote, EverNote
  • Note taking on a PDA (remember those?)
  • Hosted blog online (e.g. WordPress, Ghost)
  • Hosting your own blog online
  • Building your own blogging app

Using Route 53 to create subdomain names for your projects

If you create and deploy your own software projects to the cloud, at some point you probably end up with a number of things deployed to various places and unless you spend time maintaining your bookmarks to all these projects, it becomes hard to keep track after a while.

One of the interesting things about Route 53 is that you can create A records that resolve to IP addresses either within AWS or hosted elsewhere. If you have you own domain setup in Route 53, you can easily create subdomains with A records pointing to where ever these projects are hosted. e.g.

example1.youdomain.com -> x.x.x.x

example2.yourdomain.com -> y.y.y.y

A while back I deployed my Sudoku Solver React app to an S3 bucket hosting the website, and I can never remember the S3 endpoint name. But using a Route 53 Alias to the S3 endpoint, you can create whatever subdomain you need to point to the target resource. Here’s what it looks like setting up an alias:

Notes:

  • when you click in the Alias Target box you should see your S3 bucket already listed (if not, check you’ve enabled Static Website Hosting)
  • the recordset name must be identical to the first part of your bucket name (e.g. ‘example’)
  • the S3 bucket name must be the subdomain name plus full domain, e.g. example.yourdomain.com