Get Info: #system7

Adding the “Move to Trash” function to System 7.1

by Matt Sephton — Fri, 12 Apr 2024 22:08:00 +0000

First, a little bit of Macintosh History. You probably know that on modern macOS you can select a file in Finder, on your Desktop, or in an app, and send it to the Trash by choosing the Move to Trash menu item, or by pressing Cmd+Backspace/Delete. This keyboard shortcut was added in System 7.5.3 where it was largely unadvertised and somewhat of a secret feature, but quickly became indispensable for those who knew. Of course, these days it is proudly displayed in macOS Finder menu.

Fast forward to today, when James Wages asked about a good way to do this on System 7.1, and posed a partial solution along with a challenge. But we’ll get to that in a moment. Since I regularly use System 7 on my iPad Pro I’d also missed this function and had come up with a few different workarounds to map Move to Trash to Cmd+Backspace/Delete.

KeyQuencer
FinderHack & KeyQuencer
FinderHack & HexEdit
Bonus:
KeyQuencer, Redux

KeyQuencer

The first workaround was to script a KeyQuencer macro to simulate the mouse drag of the selected item to the trash can. This relied on you positioning the mouse pointer over the selected file and also making sure the Trash icon was always in the required position on screen. It worked, but it was less than ideal because it was far too fragile. I’ll leave reproducing this as an excercise for the reader.

KeyQuencer is one of my favourite and most used classic Macintosh apps, written by prolific Italian developer Alessandro Levi Montalcini who is still developing useful things today! Anyway, it could be used for a wide variety of macro and automation purposes. It was very versatile as it contained its own scripting language and a dictionary of functions that touched most aspects of System 7. I use it to map all sorts of esoteric functions to hotkeys, like changing screen resolutions and colour depth, or performing complicated multi-step tasks on a single key stroke. An equivalent for modern macOS is Keyboard Maestro, which is no doubt more capable but also more difficult to use.

FinderHack

So, James mentioned FinderHack which is a system Extension that gave earlier versions of System 7 a similar set of Finder features to those introduced in 7.5.3. But, crucially, it mapped the Move to Trash hotkey to Cmd+T, which is different enough to become annoying as you can no longer rely on muscle memory. The challenge: how can we map this to the modern Cmd+Backspace/Delete shortcut?

So, I turned to KeyQuencer once again and created a short macro which would type the Cmd+T key combination and I assigned it to Cmd+Backspace/Delete. It worked! Pressing my hotkey typed the FinderHack hotkey.

So we already have a good solution but resources are often scarce on classic Macintosh, so I wondered if I might be able to cut out the middleman and change the keyboard shortcut by modifying FinderHack directly. James had noticed that ResEdit would not allow you to type the Backspace character. I confirmed the same was true in Resorcerer. So, what to do?

HexEdit

Opening FinderHack directly in HexEdit we can scroll down a little to find the menu definitions, find “Move to Trash” and can change the following hex value from 54 (“T”) to 08 (“Backspace/Delete”), those being ASCII values, and reminding ourselves that the Backspace/Delete key is different than Forward Delete key on some Apple keyboards that have both.

The final modified file is up over at Macintosh Garden: macintoshgarden.org/apps/finderhack

Removing the confirmation alert

I used a disassembler to figure out the code that was responsible for showing the confirmation alert that appears after pressing the hotkey, but I wasn’t sure how best to remove it. So I asked on 68KMLA.org and user cheesestraws came up with a solution (thanks!) that involved NOPing out the Alert syscall setup, invokation, and return, and making the comparison that usually checks the alert button always default to the OK. I was so close to figuring out this solution myself, but I lacked a key bit of knowledge for how to figure out the hex code for a totally new instruction. Well, now I know how to do that! Here’s all the details of how to change the machine code. I could have and probablt should have used Ghidra to figure out this edit to the code.

Once this was done it became obvious how much of a hack FinderHack really is. After deleting the file the icon of the now missing file persists in Finder for up to a few seconds on my emulated Mac, and up to 20 seconds on period hardware! This is unacceptable, so I had to go deeper.

KeyQuencer, Redux

I went back to old faithful, KeyQuencer, to see if there was a way I could force Finder to refresh the icon more quickly. Whilst I was reading the docs I saw the following:

What Is KeyQuencer?

KeyQuencer is a utility that lets you create shortcuts, called macros, that
perform a series of tasks with a single keystroke. A macro is a set of
instructions that KeyQuencer uses to perform a task on a computer, for
example you can use KeyQuencer macros to:

   * Apply shortcuts directly to the current Finder selection, like moving
     items to the Trash.

Well! It turns out KeyQuencer could have solved our problem from day one! Lesson learned: RTFM.

So, how do we go about setting up KeyQuencer to enable this feature? Well, before we get to that let’s talk about how KeyQuencer does its thing. It consists of three main parts:

KeyQuencer Engine
one or more KeyQuencer Extensions
KeyQuencer Panel and/or KeyQuencer Editor
one or more KeyQuencer Macros

The beating heart of KeyQuencer is the KeyQuencer Engine system extension that lives in the usual System/Extensions folder, along with a folder in System called KeyQuencer Extensions that contains KeyQuencer’s own type of extensions. Still with me?

Inside the KeyQuencer Extensions folder you put any KeyQuencer Extension files that you want to use, by copying them from the KeyQuencer installation folder. This was a method to keep memory usage low by only loading the functions you’re using rather than the whole suite. So if you’re using a function from the File category, you copy the “File” KeyQuencer Extension in there.

Once all that is set up you can create/add KeyQuencer Macros, using either KeyQuencer Panel or KeyQuencer Editor. There are lots of sample macros included with the app to get you started, and many were made and shared by the community. The app also includes detailed command help so you know exactly what is possible and how to make it so. Eventually you can construct your own macro, which is what I’ll do here.

Step by step: words

Download KeyQuencer 2.5.6 which gives us a folder called KeyQuencer 2.5.6 99/07/18 and copy the following files to their destinations:
- KeyQuencer Engine goes in System/Extensions
- KeyQuencer Panel goes in System/Control Panels
- KeyQuencer Extensions/Archive and Files/File goes in System/KeyQuencer Extensions (create the destination folder)
Install AppleScript 1.1 Finder Scripting Software (this is the updated Scriptable Finder 7.1.3 and Finder Scripting Extension)
Restart the Macintosh when prompted
Create the Macro (you could also copy and paste it from a sample macro file):
- Open KeyQuencer Panel control panel
- Inside the panel choose File > New Macro
- Give the macro a name: “Move to Trash”
- Give the macro a hotkey: Cmd+Backspace/Delete
- Enter the macro script: File move selected to trash enforce by pasting, typing, or using the gui
- Click OK
Select some files and press Cmd+Backspace/Delete to move them to the trash!

Step by step: video

Here’s a screen recording of me doing the above on a fresh System 7.1:

Japanese language support on Classic Macintosh

by Matt Sephton — Tue, 07 Nov 2023 12:50:00 +0000

Collecting Japanese Macintosh Magazine Media was not without its challenges. After buying those discs, and figuring out a way to index the content, I wanted to run some of that software! So I needed a way to work with Japanese files and display them correctly in a real Classic Macintosh environment. For the reasons outlined below I decided to use only System J7.5.3 and Mac OS 9.

System 6

You’d install a third party solution like SweetJAM or GomTalk. This method only for the truly hardcore!

KanjiTalk

You could install KanjiTalk 7 on top of US System 7. It includes all the features of System 7, plus utilities for entering and displaying Japanese.

Native Japanese System 7

Later you could get official Japanese installers for System 7. I’ve found that it’s easiest to install System J7.5.3 and dual boot to it using System Picker. This allows full display of Japanese text, opening of Japanese documents and you can still type in English when you need to, by using the language input method icon in the menu bar.

Language Kits

For later versions of the system you can install Language Kits provided by Apple. For System 7 and 8 the Language Kits had to be bought. For OS 9 they came for free.

Example: Mac OS 9

After installation the process requires some additional steps: set your system to a specific font, and register specific apps to display in Japanese (if they don’t automatically).

Install “Language Kits” Result:
- You’ll gain the language input menu
- You’ll be able to see Japanese in Text control panel
Set “Control Panels -> Appearance -> Fonts -> Views Font” to Osaka Result:
- You’ll be able to see Japanese in Finder
Use “Language Register” to set Japanese on a per-app basis Result:
- You’ll be able to see Japanese in the app menus and windows

Further details at Japanese-ization of OS (Mac OS 9 edition).

About the interoperability of System 7 and iOS

by Matt Sephton — Mon, 03 May 2021 00:00:00 +0000

It never fails to amaze me how at home System 7 feels on an iPad. In fact, I’d go so far as to say I’ve never felt more capable than when I’m using it this way. What a time to be alive!

Still, there are times when it makes sense to lean on the features of the host device to get your job done more easily. In this post I detail common tasks that involve “crossing the streams”.

File Conversions

When transferring files to/from System 7 you’re going to need to convert them to/from suitable formats to make your life easier. Below I’ve listed my approach to the most common file types. Of course, your task may differ but I hope this gives you some useful hints.

Bitmap files

I use Pixaki which is a fantastic native iPad app for creating pixel art. It will load either layered Photoshop or flat PNG files, both of which are easy to generate in System 7:

PSD: Photoshop 3.0
PNG: GraphicConverter 4.1

Vector files

Dealing with vector artwork produced in the Deneba apps that I use is a little trickier. We have to jump use a stepping stone or two. First we export a file that keeps the vector data—I tend to choose Illustrator 88—and then we load that into the majestic FreeHand and export an EPS from there.

I88: Illustrator 88 (aka version 1.7)
EPS: FreeHand 3/4/5

Textual data

I generally type in Markdown so plain-text TXT files work just fine and require no conversion. Programming source code files such as C, Pascal, or otherwise also transfer without incident.

You may have some luck with Rich Text RTF files, and also with some versions of the Microsoft Word DOC file format, to transfer formatted text both ways without having to convert it to other file formats.

More exotic document formats will be trickier, but LibreOffice can open number of older formats as read-only files. Examples are: AppleWorks, ClarisWorks, Nisus Writer, WordPerfect, and more.

Tabular data

Excel 4.0 has you covered for CSV, XLS and more.

File I/O

To get files out of System 7 simply drop them onto the File Sharing drive, open Files, and long press on the file to get a list of the available actions. The exact options that iOS will give you will depend on the apps you have installed. Don’t be a stranger over at the App Store!

Printing

To print any type of document from System 7, I make use of software that allows printing to a PDF. It’s worth noting that the result is a bitmap PDF, not vector, but it’s good enough to get hold of a quick hardcopy.

PDF: Acrobat PDFWriter 3.0

Of course, if you are working with vector files you’ll have a proper scalable vector PDF file that you can print in exactly the same way.

Once the PDF is in File Sharing, use iOS to print it wirelessly to an AirPrint compatible printer.

Multitasking

iOS is only a swipe away, so remember that you can access iOS apps and services and swipe System 7 away at any time.

Split View (if you enabled it when building BasiliskII) for side-by-side browsing in Safari
Slide Over for quick access to Files, Photos, Safari, etc.
Background to listen to Music or Podcasts
Picture-in-Picture for YouTube or other video playback

Downloading files

Safari will let you download classic Macintosh file formats. Even though it doesn’t know how to handle them, they will automatically be saved on your iPad in Downloads.

From there you can use Files to copy the file into BasiliskII’s File Sharing folder, or use the iOS Share Sheet to copy the file into BasiliskII and simultaneously open the emulator! Very handy. I use one or the other depending on my goal.

Some file formats you are likely to come across:

.hqx—BinHex file
.bin—MacBinary file
.sit—StuffIt archive
.cpt—CompactPro archive
.sea—self-extracting archive

The above files can be converted or extracted using StuffIt, MindExpander, or CompactPro. You might also see files with more than one extension, in which case don’t worry the file has been treated twice for good measure, you may have to open it twice in System 7 to get it into its final/original form.

.dsk—disk image
.img—disk image
.smi—self-mounting disk image

The above disk images can be mounted using StuffIt, ShrinkWrap, DiskCopy 6. You could also mount them in the BasiliskII interface, but I tend not to do so for disk images that I won’t have mounted for very long.

.iso—standard CD-ROM disk image
.toast—proprietary CD-ROM disk image

The above optical disk images should be mounted using the BasiliskII settings interface (shown at first launch, or whenever you shake your device). Disks mounted in this way will be available at every boot, and can only be removed by shutting down the system and restarting the emulator.

Turning an iPad Pro into the Ultimate Classic Macintosh
How to install BasiliskII on your iPad
Exploring Custom Keyboards and Automation
Optimising Macintosh app toolbars for touch
Macintosh drawing software compared
Mixing External Tools across Deneba software
My System 7 software choices
About the interoperability of System 7 and iOS

My System 7 software choices

by Matt Sephton — Fri, 30 Apr 2021 00:00:00 +0000

System 7 is a great operating system. The experience using it today remains very close to modern macOS. It’s surprising how little has changed on our Desktop in the 30 years since. That said, the experience can be improved with the judicious use of additional software.

When adding things to the system my goal is always to increase quality of life and improve user experience. Functionality is key and nothing is added without careful consideration. If I can install one package to add several functions I’d rather do that than add several individual packages. If I can install software to match modern macOS features or muscle memory then I’ll do so.

Below are my personal choices that improve my time spent using System 7.

Control Panels

Better Edit Keys - adds modern text editing and selection keyboard controls, such as the ability to grow the selection by word
Capture - screen grabbing software
Capture AE - logger for Apple Events calls
Desktop Makeover - provides custom Finder features such as menu shortcuts, enhanced diskette icons, allows you to hide Balloon Help
DragAnyWindow - adds solid dragging of any window, apps can be excluded
Hidden Finder Features - enables hidden Finder keyboard shortcuts to create aliases by dragging, reveal alias original, and move file to Trash
KeyQuencer - macro and automation utility, the ultimate tool for power-users
PopupFolder - allows access to folder contents from hierarchical pop-up menu without having to drill down into folders
QuicKeys - macro and automation utility, I use it only for composing Apple Event calls
Smart Scroll - live scrolling and proportionally sized scrollbar thumb
SmartLaunch - application launcher, I launch this using Cmd+Return KeyQuencer macro
Snitch - Get Info extender, can do batch type/creator changes by summoning whilst holding Shift
Symbionts - occasionally used to troubleshoot Control Panels and Extensions
WindowShade - collapse a window into its title bar by double-clicking
YesNoCancel - adds modern keyboard control to dialog boxes

Extensions

2020Patch - fixes year 2020 date bug
About - replacement for About This Macintosh window, with task manager features
Apollo - pop-up menu at any location to select and launch apps
CopyPaste - multiple clipboard manager, works everywhere but ResEdit!
DirtyDesk - disables Clean Up Desktop menu item
Natural Order - improves sorting order in Finder

Text Editors

Alpha - programmer’s editor, includes TCL scripting
Anarcho - has a few unique features
BBEdit - packed with features
Eddan - has a way to summon THINK References

Word Processors

Take your pick of the best:

Other Utilities

CompactPro - file compressor/decompressor
GraphicConverter - image file converter
DiskTop - file manager desk accessory
Greg’s Browser - file manager with StuffIt integration
MasterFinder - multi-column file manager
MindExpander - file decompressor
(Super) ResEdit - resource editor with built-in code viewer
Resorcerer - resource editor with built-in code viewer
ShrinkWrap - disk and archiving helper
ShowSizes - disk usage analyser
Type Resolve - drag-and-drop type/creator changer

Operating System

System 7.5.3 plus updates - Apple released this version for free!
Japanese Language Kit - adds support for Japanese, I use this on a duplicate System folder
System Picker - choose which system folder to boot from
AppleScript 1.1 - to enable Finder Scripting on System 7.1

Changing the text size of a list using Resorcerer

by Matt Sephton — Wed, 28 Apr 2021 00:00:00 +0000

I sometimes use an app called KeyQuencer Launcher that is part of the KeyQuencer software. The app presents a simple window containing a list of macros allowing quick and easy access.

The text in the window is very small, which makes sense as you want to see multiple macros in as little space as possible. However, my use case in System 7 on iPad is a little different as I’d like to see fewer, larger items that are easy to select by touch.

Knowing a little about how Macintosh apps are put together I thought it should be easy enough to change the text size in the window by modifying the app’s binary code directly. This can be done using a tool called Resorcerer (you could also use Super ResEdit, or ResEdit with the CODE viewer resources installed).

By searching for 0xA88A (the _TextSize toolbox call) I was lucky enough to find a single place in the app where the text size is set. I changed the value passed to the preceding move.m from 0E (decimal 14) to 12 (decimal 18) and the text size was increased.

That was enough of a solution for me, though it is possible to change the font or to increase text size more dramatically if required.

Turning an iPad Pro into the Ultimate Classic Macintosh
How to install BasiliskII on your iPad
Exploring Custom Keyboards and Automation
Optimising Macintosh app toolbars for touch
Macintosh drawing software compared
Mixing External Tools across Deneba software
My System 7 software choices
About the interoperability of System 7 and iOS

Mixing External Tools across Deneba software

by Matt Sephton — Sun, 25 Apr 2021 00:00:00 +0000

One of the most interesting things about Deneba’s early 1990s Macintosh drawing apps is that they were built in a modular way with additional files adding specific features. These days we call those Plugins but back in 1990 Deneba referred to them as External Tools.

They are first seen in UltraPaint and later in Canvas 3.0, artWORKS and Canvas 3.5. Tools are categorised as several types: Effect, I/O, Manager, Modifier, Object, Setting and Other. Each adds functionality and/or user interface to the app in its own way.

Amongst the Deneba material on an AppleLink archive disk from Spring 1993 there are a bunch of “non-shipping” tools labelled for use with Canvas 3.0. Interestingly, they are listed individually and also as a combined set. If we extract the combined set of tools there’s a single additional tool that is somewhat out of place: the Waco Tool (for Wacom pressure sensitive pen) which is marked with UltraPaint’s type and creator information.

I can confirm this that this tool - which I don’t believe was ever included with UltraPaint - allows my Wacom ArtPad II to work. Bonus! But why was this tool meant for UltraPaint included in a download for Canvas. Could it work in Canvas?

I put the additional files in the Canvas Tools folder and started the app with the Space Bar held down. This starts the Tool Picker allowing you to select which tools you want to use for that session.

Boom! There it was.

Experimentation

I tried copying some tools from Canvas to UltraPaint and artWORKS. They didn’t work. What was the difference? In ResEdit they looked largely the same. On a whim I looked at the type/creator codes using Snitch’s Get Info extension. I noticed that disabled tools had a different type code. If the app is using type to store information like that, maybe it’s only accepting certain type codes?

So I copied a tool from Canvas over to artWORKS, being careful to pick one that already exists so it was as much like for like as it could be. It didn’t show up. Then I changed the type/creator codes and… it did show up! And not only that, but the tool worked in the app!

I was surprised, and also impressed. Deneba did a really great job with the architecture and API of these apps for things to remain this compatible over the course of several years. All three apps share code and resources. If you take a look at both UltraPaint and artWORKS in ResEdit you’ll see that they share a lot of DNA, artWORKS is basically an enhanced version of UltraPaint. I’d bet all three apps were built from the same code base.

How far can we go?

Some questions remained: how many tools could this be done with? Would they install and function? Could I use tools in artWORKS that were meant only for the more expensive Canvas? There was only one way to find out: try all the tools!

I set about copying the tools from one app to artWORKS, my favourite app, changing the creator and type codes to match. To make bulk changes to type/creator I used Get Info (with Snitch) on multiple items, but I could have used software such as FileTyper.

Year	Software	Type	Creator
1990	UltraPaint	TOOL	ULTR
1992	Canvas 3.0	TOL2	DAD2
1993	artWORKS	TOL4	DAD3

Very far!

The result was quite amazing with artWORKS total tools increasing from 59 to 92—that’s 33 additional tools! This is not counting a handful of tools that install but do not present themselves in the user interface. I’ll need to investigate those further at a later date.

Doing the same for Canvas 3.0 takes us from 74 to an even higher total of 97 tools! It’s worth noting there are a couple of tools that go by the same internal name: PANTONE™ Colors (Color Manager) and Separations (PostScript) but I’ve chosen not to merge those rows of the table as there are some subtle differences in their capabilities. Also the functionality of the Grids & Rulers tool is built-in.

The table below shows tools present in each of the apps, each with their own symbol, and then the final combined column shows all tools that are compatible with artWORKS with the symbols showing which app that tool originated from.

External Tools

Software Name	UltraPaint	Canvas 3.0	artWORKS	artWORKS+	Canvas 3.0+
Tool Loader			■	■	■
ToolPicker	▲	●	■	■	●
Alignment Specs		●	■	■	●
Antialias			■	■	■
Arrowhead Manager		●	■	■	●
Auto Trace	▲	●	■	■	●
Balloon Help		●	■	■	●
Bézier Text		●		●	●
Bind		●			●
Blend Objects		●	■	■	●
Blotter Pen	▲		■	■	■
Brush Manager		●	■	■	●
Canvas 1.0 I/O		●		●	●
Canvas 2.1 I/O		●	■	■	●
CGM I/O		●		●	●
Chalk	▲		■	■	■
Charcoal	▲		■	■	■
Coil		●		●	●
Color Manager	▲		■	■
Combine Objects		●	■	■	●
Concentric Circles		●		●	●
Contrast	▲			▲	▲
Convert To		●	■	■	●
Cube	▲	●	■	■	●
Cylinder		●		●	●
Dash Manager		●		●	●
Dimensioning		●		●	●
Doughnuts		●		●	●
Drawing Size		●	■	■	●
Dropper	▲	●	■	■	●
Duplication Specs		●	■	■	●
DXF I/O		●		●	●
Filters			■	■	■
Fingertip	▲		■	■	■
Fractals		●		●	●
Fuzz lasso/Soften Edges	▲		■	■	■
GIF I/O	▲	●	■	■	●
Gradient Fill	▲	●	■	■	●
Gray Scale Manager	▲			▲	▲
Grid Specs		●		●	●
Grid Tool/Maker	▲	●		●	●
Grids & Rulers			■	■
Hatch Patterns		●		●	●
IGES I/O		●		●	●
Illustrator I/O		●	■	■	●
Imported Filters			■	■	■
Impressionist	▲			▲	▲
Layer Specs		●	■	■	●
Luminance	▲		■	■	■
MacDraw I/O	▲	●	■	■	●
MacPaint I/O	▲	●	■	■	●
Magic Wand	▲		■	■	■
Masking	▲		■	■	■
Mover		●	■	■	●
Multigon	▲	●	■	■	●
NameStamp		●		●	●
Object Specs		●	■	■	●
Object Tint		●		●	●
PANTONE™ Colors		●		○	●
Parallel Lines		●		●	●
Pattern Manager		●	■	■	●
Pen Manager		●		●	●
Place		●		●	●
Point Rotate		●		●	●
PostScript			■	■
Preferences		●	■	■	●
Pressure Pen	▲	●	■	■	●
QuickTime		●	■	■	●
Quill Pen	▲		■	■	■
Registration Marks		●		●	●
Resistor		●		●	●
RGB Color Manager		●		●	●
Rubber Stamp	▲		■	■	■
Ruler Specs		●		●	●
Scale Specs		●	■	■	●
Search & Replace		●		●	●
Selection Specs		●		○	●
Separations		●		○	●
Sharpen and Blur	▲			▲	▲
Size Other			■	■	■
Slides		●			●
Smart Mouse		●		○	●
Sounder		●	■	■	●
Spacing Other			■	■	■
Spelling		●		●	●
Spiral		●		●	●
Split		●	■	■	●
Spray Manager		●	■	■	●
StartupScreen I/O	▲	●	■	■	●
System 7.0 Options		●	■	■	●
Text Ruler		●		○	●
Text Utilities		●		●	●
Textures			■	■	■
Three Color Airbrush	▲		■	■	■
TIFF I/O	▲	●	■	■	●
TimeStamp		●		●	●
Tool Info		●	■	■	●
UltraPaint 1.0 I/O		●	■	■	●
Undo Killer		●		○	●
Water Droplet	▲		■	■	■
Total Tools	30	74	58	92	97

Key:

▲ UltraPaint tool ● Canvas 3.0 tool (○ that installs but doesn’t show any interface) ■ artWORKS tool

Result

So after all this I now have an install of artWORKS (let’s call it artWORKS+) that includes additional tools from both UltraPaint and Canvas 3.0 and I had a ton of fun figuring all this out. And I’m only 30 years late!

Here’s a download of my artWORKS Tools folder containing all the combined tools (use StuffIt! Expander 5.5 to extract): artWORKS-Tools-Combined.sit [1.1MB]

Footnote

A note about later versions of Canvas: version 3.5 provides roughly the same tools as version 3.0. The handful of unique tools in version 3.5 are not compatible with artWORKS. Version 5.0 features similar tools but they’re no longer compatible with the earlier apps.

Turning an iPad Pro into the Ultimate Classic Macintosh
How to install BasiliskII on your iPad
Exploring Custom Keyboards and Automation
Optimising Macintosh app toolbars for touch
Macintosh drawing software compared
Mixing External Tools across Deneba software
My System 7 software choices
About the interoperability of System 7 and iOS

Macintosh drawing software compared

by Matt Sephton — Sat, 24 Apr 2021 00:00:00 +0000

Below is a list of various drawing applications that are available to use with System 7 (68K).

I’m mostly interested in apps that can do both pixel and vector, and that support layers and transparency. The table below might be useful for at-a-glance comparisons. Apps run in both mono or colour, unless stated otherwise.

Deneba artWORKS can do both pixel and vector, has layers and partial transparency. The bottom layer is opaque and all layers on top are transparent. Collections of pixels are managed as a special object, and there’s a limit of 8 layers. The user interface is brilliant.

SuperPaint has two layers: pixel and vector with transparency in all but the base layer. Though it allows cut/copy and paste from the pixel layer to the vector layer at which point those collections of pixels are managed as SuperBits objects and can be edited in isolation.ref

Freehand is king of the vector apps. It really was so much better than Illustrator. Such a shame that it’s no longer around. To use it on iPad is quite something!

Also interesting is how many early versions of successful apps didn’t support layers (Photoshop, Freehand) or full transparency (Photoshop).

Almost every app has only a single level undo, with only Expression and Freehand offering multi-level undo. This is probably why everybody was using Freehand when I started work in graphic design in the mid-late 1990s.

One small disappointment: Macromedia Fireworks requires the PPC architecture so won’t run on my iPad System 7 setup. Sad face. (But we can use infinitemac.org)

APP	PIXEL	VECTOR	LAYERS	TRANSP.	UNDO	NOTES
artWORKS	●	●	●	○		Many layers, many objects
BluePaint	●			○		PPC-only
Canvas	●	●	●	○		Many layers, many objects
ClarisDraw	●	●	●			Pixel drawing within specific objects
Cricket Draw		●
Draw It Again Sam		●	●
Drawing Table		●
Expression		●	●		●	Colour required
Freehand 1.0–2.0		●	○		●	Layers not managed visually
Freehand 3.1–5.5		●	●		●
Illustrator 88–3.0		●
ImageStudio 0.6	●					Custom brushes
LightningPaint	●					Polite palettes
MacDraw Pro		●	●
MacPaint	●
MacroPaint	●			○		Transparent patterns
Photoshop 1.0–2.5	●
Photoshop 3.0	●		●	●		Full alpha channel transparency
PixelPaint	●					Special brush effects
ShareDraw		●	●
Studio/1	●					Animation, 1-bit
Studio/8	●					Animation, 8-bit
SuperPaint	●	●	●	○		Two layers, many objects
UltraPaint	●	●	●	○		Eight layers, many objects
Zeus	●					Animation

Key: ● full support, ○ partial support

Automating interactions using Apple Events

by Matt Sephton — Mon, 19 Apr 2021 00:00:00 +0000

As I’ve previously mentioned, UltraPaint and artWORKS share a lot of DNA so their structure is effectively identical, including the tool palette. This is a good thing as I intend to automate tool selection in both apps and I’ll take any help 30-year-old software wants to send my way!

Chapter 6 in the book “The Automatic Mac” (1992, download) details a number of ways of scripting graphics programs. They use Canvas as an example, which is great because that is a very close relative to the artWORKS and UltraPaint apps that I use. The book informed a lot of what I’m doing here, though my approach differs because of my available tools and personal preference.

Simply Clicking

My first thought was to try the naive way of selecting tools by just clicking them! If the tool palettes are positioned in the same place (this can also be automated) then macros can simply click at specific screen locations to select a tool. This approach works well for both apps. But this is a very fragile way of automating interactions—if windows are inadvertently moved the automation will break. So, there’s definitely room for improvement.

Going Deeper

According to period Apple documentation (PDF, HTML) a means of automation was introduced in System 7:

The interapplication communication (IAC) architecture provides a standard and extensible mechanism for communication among Macintosh applications. The IAC architecture makes it possible for your application to

provide automated copy and paste operations between your application and other applications

be manipulated by means of scripts

send and respond to Apple events

send and respond to high-level events other than Apple events

read and write blocks of data between applications

Sounds perfect—my idea of a good time!

Apple Events

To support AppleScript, apps were required to offer suites of supported messages and mechanisms. These are advertised through the aete resource. ResEdit shows this data as raw hex, unless you install a template to enable it to make sense of it. Resorcerer supports it out of the box. There are a bunch of other tools that can display the data in a human readable way such an Apple-created HyperCard stack, a third-party app called EightyRez, and automation tool QuicKeys to name just a few.

QuicKeys sounded ideal as it lets me query the data, using a set of dropdown menus, and use it to specify automation to try out the Apple Events way of selecting a tool. It worked first time! But it was slow, and there was a distracting loss of window focus as the macro was executed.

In search of something better turned to my favourite classic automation tool: KeyQuencer. I’d previously searched trough various archives for any available macros, so had a vague memory there was something out there I might be able to use. I dug up AESend, an Apple Events extension for KeyQuencer.

I used QuicKeys GUI to set up the initial Apple Events call, as it allows you to pick options from drop-down lists. Then I used the Capture AE control panel to decode the Apple Events call into something human readable that I could adapt for use in KeyQuencer. I’d still take that approach for any new Apple Events.

The result was much faster Apple Events sending and no distracting window focus flickering.

Two-in-One

The end result is a macro of two parts: the first section operates artWORKS using Apple Events, continuing without complaint if the app is not open, and the second section operates UltraPaint using simple mouse clicks.

I plan to adding support for Canvas 3.x at some point as this shares Apple Events support with artWORKS.

Investigation

According to the aete resource description in both artWORKS and Canvas, selection of Internal Tools using Apple Events is limited to 10 seemingly random tools. This made no sense to me, so I tried specifying higher tools and this experimentation proved that all 18 internal tools are indeed available. I guess the description had been truncated at some point?

Some time later I read “The Automatic Mac” again and it shows a more complete list of tool values! The order seems to be based on the tool palette in Canvas.

Even so, I went the extra mile to complete a list of both internal and external tools, shown below.

Internal Tools (btol)

Name	shor
ArcRect	7
Arrow	1
BezierCurve	10
Brush	14
Eraser	17
Free Hand	8
Lasso	11
Line	3
Marquee	12
Oval	6
Paint Bucket	15
Paint Object Creator	18
Pencil	16
Polygon	9
Rect	4
RoundRect	5
Spray Can	13
Text	2

External Tools (etol)

Name	long
Coil	CoiL
Concentric Circles	CCir
Cube	Cube
Cylinder	cyln
Dimensioning	DIMN
Doughnuts	doug
Fractals	Flin
Gradient Fill	ObFl
GridMaker	grid
Mover	MovE
Multigon	NGON
Namestamp	NamE
Parallel Lines	Paln
Point Rotate	PtRt
QuickTime	QkTm
Registration Marks	regP
Resistor	ResT
Sounder	sndT
Spiral	Spir
Split	Splt
Star	STAR
Timestamp	TimE

Turning an iPad Pro into the Ultimate Classic Macintosh
How to install BasiliskII on your iPad
Exploring Custom Keyboards and Automation
Optimising Macintosh app toolbars for touch
Macintosh drawing software compared
Mixing External Tools across Deneba software
My System 7 software choices
About the interoperability of System 7 and iOS

Turning an iPad Pro into the Ultimate Classic Macintosh

by Matt Sephton — Sat, 17 Apr 2021 00:00:00 +0000

I’ve started work on the next in my 1-bit Woodblocks series: “Tekagami” (Ito Shinsui’s “Hand Mirror”). So it’s a good time to talk about how I turned an iPad Pro into the ultimate Classic Macintosh.

Emulators

Both Macintosh emulators available on iOS we’re ported by @maczydeco who has done an amazing job making them feel truly at home on iOS. Many thanks! They need to be built from source using Xcode but it’s a pretty straight forward process.

Mini vMac

Supports System 1.1 to 7.5.5
Limited RAM and CPU emulation
File Sharing via bespoke method
No dynamic screen resolution changing
Odd interface using Control key shortcuts
Source code

BasiliskII

Supports System 7.0 to 8.1
Advanced RAM and CPU emulation
File Sharing via mapped folder
Dynamic screen resolutions through Monitors control panel, or automation
Native iOS interface for settings panel, negating all the issues with the desktop GUI
We have a winner!
Source code (use the ios branch)

This works a treat in both emulators, but the experience is better in BasiliskII.

With Mini vMac you need to run a special file import app, and then whilst it’s open use iOS Share Sheet to send a file to Mini vMac. These extra steps are just enough friction to make the emulator annoying to use.

With BasiliskII things are easier as it has a drive mapped to the app’s file sharing folder. You can use the Share Sheet in the same way as Mini vMac, but you can also simply copy/move a file to the BasiliskII folder and it will be accessible inside the emulator. The only gotcha with this approach is that you’re best moving the file to the emulated system’s main disk drive otherwise you’ll encounter various oddities with certain apps that don’t know how to cope with files located on this type of drive.

Screen Resolutions

The original Macintosh had a native screen resolution of 512×342.

Conceptually, the iPad has a logical screen resolution of 1024×768, which when running in pixel doubled mode equates to 512×384. A pretty good match. Specifically, the native resolution varies according to the model of iPad or iPhone you are using.

I use an iPad Pro 12.9” which has a native resolution of 2732×2048, pixel doubled that means 1366×1024, and pixel quadrupled 683×512. Targeting this ballpark of resolution means user interface elements will be around the magic 44pt tappable area, so that fingertip interactions are accurate, predictable and enjoyable.

Of course the iPad can flip between landscape and portrait orientations on demand, which means BasiliskII supporting the Monitors control panel is a big win.

So I added a bunch of custom resolutions to the BasiliskII soure code to add support for both pixel-doubled and pixel-quadrupled resolutions, in both portrait and landscape, with and without room for the software keyboard. I can switch between these resolutions with keyboard shortcuts. Which leads nicely on to…

Custom Keyboards

Both emulators share the same software keyboard mechanism. The keyboard layouts are user-editable as JSON and compiled into a custom format.

So I put together a custom keyboard layout that can be used in either emulator that gives me quick thumb access to tools and shortcuts in my most used apps: artWORKS and UltraPaint. It works for both apps as they are closely related, sharing a lot of code and resources.

With this keyboard layout I’m not only relabelling the function keys, but also replacing some key codes to reposition keys for my own purposes. The apps don’t respond to function keys so I use macros and Apple Events to get things to work as detailed in another post.

How does the experience compare to a real Macintosh?

The most important aspect of this setup is that it runs System 7 and the various apps I use. That is the core of my classic Macintosh experience and the goal I had in mind. The hardware running System 7 is merely a conduit.

That said, the iPad Pro is more portable, reliable and capable than my real Macintosh. That’s 30 years of hardware progress for you.

The iPad’s display in particular is a huge differentiator—it can assume so many different resolutions it should be thought of as a collection of displays rather than just a single one.

Apple Pencil is very similar in feel to my Wacom ArtPad II, but with the single huge improvement that you’re drawing directly on the screen. Drawing with an Apple Pencil on System 7 is every bit as good as drawing in a native iPad app.

iOS is only a swipe away: download classic software using a modern web browser like Safari, expand archives more quickly with Files or Documents, watch videos picture-in-picture, search your Inside Macintosh PDFs in Books, listen to streaming music, and so many other things that aren’t doable (or at least are extremely difficult to do) on a real classic Macintosh.

Bluetooth keyboards just work. The new/recent mouse pointer support in iOS also works. You could even plug the iPad into an external display to go full circle back to a desktop computer.

This setup gives me the best of both old and new worlds, and that’s why I refer to it as the Ultimate Classic Macintosh.

Turning an iPad Pro into the Ultimate Classic Macintosh
How to install BasiliskII on your iPad
Exploring Custom Keyboards and Automation
Optimising Macintosh app toolbars for touch
Macintosh drawing software compared
Mixing External Tools across Deneba software
My System 7 software choices
About the interoperability of System 7 and iOS

Elsewhere

2021-03-29—The Mac Observer
2021-04-18—Hacker News
2021-04-19—Boing Boing
2021-04-19—iDownloadBlog
2021-04-19—The Loop
2021-04-22—FredZone (in French)
2021-04-23—Gizmodo
2021-04-23—Pixel Envy
2021-04-26—iGeneration (in French)

History of DenebaCAD

by Matt Sephton — Fri, 09 Apr 2021 00:00:00 +0000

I recently stumbled across a series of Facebook posts about the origins of DenebaCAD, from humble beginnings as MasterCAD on Atari ST, of all unlikely places. The app still exists today as DCAD VectorSpace. Here I provide the story translated from Spanish into English.

Year	Title	Platform	Distribution
1988	MasterCAD	Atari ST	Retail
1989	User’s CAD	Macintosh	Beta
1991	ArchiDOT 2.0	Macintosh	Retail
1992	ArchiDOT 3.0	Macintosh	Retail
1997	DenebaCAD	Macintosh	Retail

This breakthrough CAD software was created by Hernán Pisani at INDI C.A. (Calle Madrid, Qta. El Pilar, Las Mercedes, Caracas, Venezuela).

The below is taken from Metamorfosis 3D on Facebook with the text presented in full below, albeit translated from Spanish using DeepL.

In 1988 and MasterCAD was sold to the world by several @ATARI distributors. MasterCAD was present in several industrialized countries and version 2.0 was presented at the COMDEX in Las Vegas from November 14 to 19, 1988. In that year the program was reviewed in different specialized publications such as ST WORLD of England, ST INFORMER, STAR, CURRENT NOTES of the United States totaling 17 pages of dedication by them. Due to the limited presence of Atari computers in the professional world, despite the power of the Atari 1040 ST, it was decided to opt for the support of the Apple Latin America initiative for local developers and an agreement was reached with Atari Venezuela leaving them the MasterCAD product in the ATARI environment as far as the development had reached and continue with the technology they had developed in Macintosh, which was undoubtedly a larger market. Thus began the development of a beta version of ArchiDOT which they called User’sCAD, a considerably more powerful and user friendly product.

In 1989 the development of the pilot project of a product that was thought to be called user User’sCAD and that later would be launched on the market under the name of ArchiDOT (Architectural Design Oriented Tool) began. Already here it was realized that the development of the product should be oriented only to architectural design and not pretend to solve problems of other engineering, in order not to complicate the tool pretending to also solve different thought processes and running the risk that the tool would no longer be intuitive. The program was based on Mac II and Mac SE hardware with the support of the A.C.E. program of APPLE Corp represented in Venezuela by PLUS SISTEMAS. This development, still in Alpha phase, was presented at the WORLWIDE DEVELOPERS CONFERENCE held in San Jose California in May 1989, receiving comments of praise from the representative of APPLE Latin America and other members of the Apple Staff as well as from the representatives of the Tecnológico de Monterrey.

In 1990 the CADD Room was inaugurated at the Simon Bolivar University. Hernan to date had spent 20,000.00 architect-hours of analysis and 11,000.00 hours of programming accumulated from the origin to User’sCAD, an architecture-oriented CAD. Its version ß3 participated in the Latin American Software contest in May 1990, competing with the finished applications and being in sixth place with mention (first place in CAD), receiving comments of praise from Apple Computer’s staff representatives. In December 1990 it was presented with a booth at the DATA 90 exhibition in Miami, Florida. User’sCAD was selected in 1991 as the resident application in the laboratories of advanced design techniques at the School of Architecture of the Simon Bolivar University, Caracas, as a subject of the curriculum for two quarters. At that time the application, for marketing and identification reasons, the name User’sCAD was replaced by ArchiDOT 2.0 (Architectural Design Oriented Tool). In Venezuela alone, 150 architecture and construction companies successfully produced drawings with the program and successfully with Hernán’s program and consulting services.

In 1992 a work done in ArchiDOT was presented at Harvard University. Diego Diaz, using a Mac IIci of the time and ArchiDOT version 3.0, presented his independent study work as part of his master’s degree at Harvard University and received an evaluation and recommendation of the software by the computer lab of the GSD (Graduate School of Design).

In 1993 CADSOFT, the company founded by Hernan, starts again the international marketing with the opening of the Spanish market and ArchiDOT passes the necessary quality control tests for this demanding market. Our distributor in Spain: The company Microgestió in Barcelona is in charge of distributing the software in their authorized Apple stores. On the other hand, also in 1993, Architect Carlos Pollak (Head of CADD USB Room) recently presented a paper at the World Congress of Architectural Education (Prague 1993) on the use of ArchiDOT in design education. As a result of the good role played by the product, Apple Czech Republic showed interest in distributing it in that country.

Between 1994 and 1995 ArchiDOT was shown to several software houses in the United States and attracted the interest of Deneba Software. ArchiDOT was written up to that time in Symantec Pascal, a good language that was used to its full potential but was clearly insufficient for the development of a world class CAD version. They ported, through the use of the PtoC converter, the Pascal code and the mathematical algorithms of ArchiDOT to the C++ language in its implementation “Code Warrior” of Metrowerks, to give birth to a much superior application in speed and performance, generating laboratory versions that were tested by several users among which I was. It was amazing at that time the image quality that we could achieve with that version that could only be surpassed with render engines years later. The conversion process from Pascal to C++ was in charge of Eng. Federico Zappi. The next step was the development of the new interface that was in charge of Architect Hernan Pisani and Mr. Doug Levy, vice-president of Deneba Software. All this happened after signing a publishing contract with Deneba Software, which gave birth to Deneba CAD.

Changing the size of toolbar items using ResEdit

by Matt Sephton — Sun, 28 Mar 2021 00:00:00 +0000

I just finished increasing the size of toolbar icons in Deneba artWorks from 24x16 to 24x24.

Easily done by finding the dialog that contains these icons, and resizing the canvas of each related PICT.

Several trips between ResEdit and Photoshop (version 1.0!) and I was done.

This is to make the tool buttons easier to tap with my thumb when running System 7 on iPad.

I love this “hackable” nature of early Macintosh systems. Palm OS is very similar in that regard.

Why moan about an app not being to your liking when you can DIY!?

Get Info: #system7

Adding the “Move to Trash” function to System 7.1

KeyQuencer

FinderHack

HexEdit

KeyQuencer, Redux

Japanese language support on Classic Macintosh

System 6

KanjiTalk

Native Japanese System 7

Language Kits

Example: Mac OS 9

About the interoperability of System 7 and iOS

File Conversions

File I/O

Printing

Multitasking

Downloading files

Related posts

My System 7 software choices

Control Panels

Extensions

Text Editors

Word Processors

Other Utilities

Operating System

Related posts

Changing the text size of a list using Resorcerer

Related posts

Mixing External Tools across Deneba software

Experimentation

How far can we go?

Very far!

External Tools

Result

Footnote

Related posts

Macintosh drawing software compared

Related posts

Automating interactions using Apple Events

Simply Clicking

Going Deeper

Apple Events

Two-in-One

Investigation

Internal Tools (btol)

External Tools (etol)

Related posts

Turning an iPad Pro into the Ultimate Classic Macintosh

Emulators

File Sharing

Screen Resolutions

Custom Keyboards

How does the experience compare to a real Macintosh?

Related posts

Elsewhere

History of DenebaCAD

Changing the size of toolbar items using ResEdit