Make component/script names match XML device names (specifically, serial and parallel, which used to be serialport and parallelport)

This commit is contained in:
Jeff Parsons 2016-12-29 13:21:22 -08:00 committed by Jeff Parsons
commit ded8f15e86
22 changed files with 913 additions and 925 deletions

View file

@ -21,8 +21,8 @@ begin connecting PCs to terminals.
Below you'll find an 80286-based [IBM PC AT](/devices/pcx86/machine/5170/ega/2048kb/rev3/) connected to an 8080-based
[VT100 Terminal](/devices/pc8080/machine/vt100/) via the PC's **COM2** serial port.
At this point, the connection is *very* thin. The [PCx86](/modules/pcx86/) [SerialPort](/modules/pcx86/lib/serialport.js)
and [PC8080](/modules/pc8080/) [SerialPort](/modules/pc8080/lib/serialport.js) each export exactly two methods:
At this point, the connection is *very* thin. The [PCx86](/modules/pcx86/) [SerialPort](/modules/pcx86/lib/serial.js)
and [PC8080](/modules/pc8080/) [SerialPort](/modules/pc8080/lib/serial.js) each export exactly two methods:
- *initConnection()*
- *receiveData()*

View file

@ -35,7 +35,7 @@ Most of the work remaining is in device management. Like other PCjs emulators,
UNIBUS addresses. During the initial port, I moved all of Paul's original device management code into one "catch-all"
component, [device.js](/modules/pdp11/lib/device.js), which has now been converted to the new I/O registration model.
The first new device component is [serialport.js](/modules/pdp11/lib/serialport.js), which is currently the
The first new device component is [serial.js](/modules/pdp11/lib/serial.js), which is currently the
only means PDPjs has of communicating with the outside world. So you can try
[PDPjs connected to a VT100 Terminal](/devices/pdp11/machine/1170/vt100/), by clicking the **Run** button on the test machine.
The test machine is running [custom boot code](/apps/pdp11/boot/test/), adapted from boot code written by Paul, but due to the