Disassembly of the Apple II Desktop - ProDOS GUI
Go to file
2018-02-02 08:00:42 -08:00
desk.acc project cleanup 2018-02-01 10:00:17 -08:00
desktop point refs 2018-02-02 08:00:42 -08:00
inc project cleanup 2018-02-01 10:00:17 -08:00
res project cleanup 2018-02-01 10:00:17 -08:00
.gitignore DeskTop: Identify bank-switched routines 2018-01-04 12:58:32 -08:00
desktop.inc struct renames 2018-01-30 08:57:36 -08:00
keyboard.md Update keyboard.md 2018-01-21 15:54:00 -08:00
mgtk.inc param blocks 2018-02-01 11:30:03 -08:00
MGTK.md project cleanup 2018-02-01 10:00:17 -08:00
README.md Update README.md 2017-09-21 09:49:06 -07:00

A2D

Work-in-Progress disassembly of Apple II Desktop (a.k.a. A2.Desktop)

Background

A2.Desktop started its life as "Mousedesk" by Version Soft, as a mouse-driven Mac-like "Finder" GUI application for 8-bit Apples with 128k of memory (Enhanced Apple //e, Apple //c) using double-hires monochrome graphics (560x192) and the ProDOS operating system.

Although the history is sketchy, it appears that Apple Computer licensed (or acquired) the software, and released it - rebranded as Apple II Desktop - as the initial system software for the Apple IIgs before 16-bit GS/OS replaced it. The rebranded version still functions on 8-bit Apples.

Overview: http://toastytech.com/guis/a2desk.html

Manual: Apple IIgs System Disk Users Guide (1986) - Chapter 2 “The DeskTop”

A pieced-together history, details of versions, bug reports and feature requests: https://mirrors.apple2.org.za/ground.icaen.uiowa.edu/MiscInfo/Misc/mousedesk.info

Disks can be found at: ftp://ftp.apple.asimov.net/pub/apple_II/images/masters/other_os/gui/

Other GUI environments exist for the 8-bit Apples, including GEOS (which includes productivity applications) and Quark Catalyst. While A2.Desktop is more limited - serving only as a file manager and application launcher - it is (subjectively) more visually appealing and better integrated with ProDOS.

Goal

The goal of this project is to disassemble/reverse-engineer the suite with an eye towards understanding how it functions, and eventually fixing bugs and adding functionality.

Tools

The cc65 tool chain will be used; source files will target the ca65 macro assembler. Cross-development on modern systems will be assumed. (Sorry, Merlin purists! We still love you.)

Code of Conduct

Discussions should be polite, respectful and inclusive, and focus on the code. Harassment will not be tolerated. Keep comments constructive.