No description
Find a file
Wolfgang Thaller 67e345fbb2
Merge pull request #9 from agoode/time
Define InsXTime
2024-05-17 16:05:17 +02:00
custom Implement GetVRefNum and FlushVol 2024-04-06 21:43:43 -04:00
defs Define InsXTime 2024-05-10 19:36:38 -04:00
.clang-format Fix duplicate clang-format directive 2024-03-30 14:53:32 -04:00
.gitignore clean up .gitignore 2019-09-24 00:59:20 +02:00
cincludes.rb Generate Timer.h 2024-05-09 20:32:20 -04:00
COPYING add a license 2019-08-31 17:45:41 +02:00
executor.rb C calling convention support for Executor 2022-05-26 21:37:46 +02:00
generator.rb Generate legacy font names under OLDROUTINENAMES 2024-03-30 14:54:58 -04:00
make-multiverse.rb handle "api: carbon" 2019-11-10 17:08:41 +01:00
multiversal.schema.json Generate legacy font names under OLDROUTINENAMES 2024-03-30 14:54:58 -04:00
README.md Fix typos in README.md 2022-03-17 23:19:20 -05:00
uncrustify.cfg add support for some more code formatters, or none at all 2019-09-26 23:23:16 +02:00

Multiversal Interfaces

Interfaces to Apple's classic Mac OS APIs (pre-Carbon, i.e. 20th century), encoded in YAML files along with a Ruby program to convert them

  1. to C/C++ headers for use with Retro68.
  2. to C++ headers for use as part of Executor 2000

The API definition files were automatically generated from the header files that were originally included with Executor 2000. As Executor was a clean-room implementation of Mac OS and is now available under a liberal license, the resulting header files can be used and redistributed freely. The translator program can still be found in the separate multiversal-parser repository.

JSON Schema

A JSON schema definition for the definition files is available in the file multiversal.schema.json. When it's finished, it will serve as documentation for the API definition YAML files.

If you're using vscode to edit the YAML files, you can set up automatic schema validation (= error messages and completion hints as you type) by installing the YAML extension and adding

"yaml.schemas": {
    "multiversal.schema.json": "defs/*.yaml"
}

to your vscode workspace settings (.vscode/settings.json). If you have checked out the Multiversal Interfaces as a submodule of Executor 2000 or Retro68, add the subdirectory to the relative paths:

"yaml.schemas": {
    "multiversal/multiversal.schema.json": "multiversal/defs/*.yaml"
}