2021-07-07 00:04:02 +00:00
|
|
|
import { debug } from '../js/util';
|
|
|
|
import { jsonDecode } from '../js/formats/format_utils';
|
|
|
|
import {
|
|
|
|
createDisk,
|
|
|
|
createDiskFromJsonDisk,
|
|
|
|
} from '../js/formats/create_disk';
|
|
|
|
import {
|
|
|
|
FormatWorkerMessage,
|
|
|
|
DiskProcessedResponse,
|
|
|
|
DISK_PROCESSED,
|
|
|
|
PROCESS_BINARY,
|
|
|
|
PROCESS_JSON_DISK,
|
|
|
|
PROCESS_JSON,
|
Floppy controller refactorings 1 (#155)
* Add `DiskMetada` to the `Disk` interface
Before, metadata about the image, such as name, side, etc. was mixed
in with actual disk image information. This change breaks that
information into a separate structure called `DiskMetadata`.
Currently, the only two fields are `name` and `side`, but the idea is
that more fields could be added as necessary, like a description, a
scan of the disk or label, etc. In a follow-on change, the default
write-protection status will come from the metadata as well.
The current implementation copies the metadata when saving/restoring
state, loading disk images, etc. In the future, the metadata should
passed around until the format is required to change (like saving one
disk image format as another). Likewise, in the future, in may be
desirable to be able to override the disk image metadata with
user-supplied metadata. This could be use, for example, to
temporarily add or remove write-protection from a disk image.
All existing tests pass and the emulator builds with no errors.
* Rename `writeMode` to `q7`
Before, nibble disk emulation used the `writeMode` field to keep track
of whether the drive should be read from or written to, but the WOZ
emulation used `q7` to keep track of the same state.
This change renames `writeMode` to `q7` because it more accurately
reflects the state of the Disk II controller as specified in the
manuals, DOS source, and, especially, _Understanding the Apple //e_ by
Jim Sather.
* Remove the coil state
Before, `q` captured the state of the coils. But it was never read.
This change just deletes it.
* Use the bootstrap and sequencer ROMs with indirection
Before, the contents of the bootstrap ROM and sequencer ROM were set
directly on fields of the controller. These were not saved or
restored with the state in `getState` and `setState`. (It would have
been very space inefficient if they had).
Now, these ROMs are used from constants indexed by the number of
sectors the card supports. This, in turn, means that if the number of
sectors is saved with the state, it can be easily restored.
* Split out the Disk II controller state
This change factors the emulated hardware state into a separate
structure in the Disk II controller. The idea is that this hardware
state will be able to be shared with the WOZ and nibble disk code
instead of sharing _all_ of the controller state (like callbacks and
so forth).
* Factor out disk insertion
Before, several places in the code essentially inserted a new disk
image into the drive, which similar—but not always exactly the
same—code. Now there is an `insertDisk` method that is responsible
for inserting a new `FloppyDisk`.
All tests pass, everything compiles, manually tested nibble disks and
WOZ disks.
2022-09-01 01:55:01 +00:00
|
|
|
FloppyDisk,
|
2021-07-07 00:04:02 +00:00
|
|
|
} from '../js/formats/types';
|
|
|
|
|
|
|
|
debug('Worker loaded');
|
|
|
|
|
|
|
|
addEventListener('message', (message: MessageEvent<FormatWorkerMessage>) => {
|
|
|
|
debug('Worker started', message.type);
|
|
|
|
const data = message.data;
|
2022-09-19 07:07:27 +00:00
|
|
|
const { driveNo } = data.payload;
|
Floppy controller refactorings 1 (#155)
* Add `DiskMetada` to the `Disk` interface
Before, metadata about the image, such as name, side, etc. was mixed
in with actual disk image information. This change breaks that
information into a separate structure called `DiskMetadata`.
Currently, the only two fields are `name` and `side`, but the idea is
that more fields could be added as necessary, like a description, a
scan of the disk or label, etc. In a follow-on change, the default
write-protection status will come from the metadata as well.
The current implementation copies the metadata when saving/restoring
state, loading disk images, etc. In the future, the metadata should
passed around until the format is required to change (like saving one
disk image format as another). Likewise, in the future, in may be
desirable to be able to override the disk image metadata with
user-supplied metadata. This could be use, for example, to
temporarily add or remove write-protection from a disk image.
All existing tests pass and the emulator builds with no errors.
* Rename `writeMode` to `q7`
Before, nibble disk emulation used the `writeMode` field to keep track
of whether the drive should be read from or written to, but the WOZ
emulation used `q7` to keep track of the same state.
This change renames `writeMode` to `q7` because it more accurately
reflects the state of the Disk II controller as specified in the
manuals, DOS source, and, especially, _Understanding the Apple //e_ by
Jim Sather.
* Remove the coil state
Before, `q` captured the state of the coils. But it was never read.
This change just deletes it.
* Use the bootstrap and sequencer ROMs with indirection
Before, the contents of the bootstrap ROM and sequencer ROM were set
directly on fields of the controller. These were not saved or
restored with the state in `getState` and `setState`. (It would have
been very space inefficient if they had).
Now, these ROMs are used from constants indexed by the number of
sectors the card supports. This, in turn, means that if the number of
sectors is saved with the state, it can be easily restored.
* Split out the Disk II controller state
This change factors the emulated hardware state into a separate
structure in the Disk II controller. The idea is that this hardware
state will be able to be shared with the WOZ and nibble disk code
instead of sharing _all_ of the controller state (like callbacks and
so forth).
* Factor out disk insertion
Before, several places in the code essentially inserted a new disk
image into the drive, which similar—but not always exactly the
same—code. Now there is an `insertDisk` method that is responsible
for inserting a new `FloppyDisk`.
All tests pass, everything compiles, manually tested nibble disks and
WOZ disks.
2022-09-01 01:55:01 +00:00
|
|
|
let disk: FloppyDisk | null = null;
|
2021-07-07 00:04:02 +00:00
|
|
|
|
|
|
|
switch (data.type) {
|
|
|
|
case PROCESS_BINARY: {
|
|
|
|
const { fmt, options } = data.payload;
|
|
|
|
disk = createDisk(fmt, options);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
|
|
|
case PROCESS_JSON_DISK: {
|
|
|
|
const { jsonDisk } = data.payload;
|
|
|
|
disk = createDiskFromJsonDisk(jsonDisk);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
|
|
|
|
case PROCESS_JSON: {
|
|
|
|
const { json } = data.payload;
|
|
|
|
disk = jsonDecode(json);
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
const response: DiskProcessedResponse = {
|
|
|
|
type: DISK_PROCESSED,
|
|
|
|
payload: {
|
2022-09-19 07:07:27 +00:00
|
|
|
driveNo,
|
2021-07-07 00:04:02 +00:00
|
|
|
disk
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
self.postMessage(response);
|
|
|
|
|
|
|
|
debug('Worker complete', message.type);
|
|
|
|
});
|