Consolidated /docs into /pubs
This commit is contained in:
parent
9d356c582b
commit
71d117fa02
106 changed files with 350 additions and 317 deletions
|
|
@ -11,7 +11,7 @@ are simple XML files that describe a piece of software (an application, an opera
|
|||
link to a PCjs machine configuration capable of running the software, along with a "ready-to-run" machine state file.
|
||||
Conversely, a PCjs machine XML file can refer back to the manifest, to obtain a list of disk images.
|
||||
|
||||
Here are some [Demos](/apps/pc/) of "ready-to-run" apps on [PCjs](/docs/about/).
|
||||
Here are some [Demos](/apps/pc/) of "ready-to-run" apps on [PCjs](/pubs/about/).
|
||||
|
||||
There have been lots of server-side changes recently, including API improvements that make it easy (well, *easier*)
|
||||
to dynamically create diskette images from a list of files, or even an entire folder (including all subfolders),
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ category: HTML5
|
|||
permalink: /blog/2014/12/05/
|
||||
---
|
||||
|
||||
From the beginning of the [JavaScript Machines](/docs/about/) Project, I've always used an HTML5
|
||||
From the beginning of the [JavaScript Machines](/pubs/about/) Project, I've always used an HTML5
|
||||
[Canvas](https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API) object for both machine output
|
||||
and input. It's the obvious choice for output, because the Canvas provides a 2D drawing API that's
|
||||
essential both for drawing bitmappped graphics and for faithfully rendering individual characters
|
||||
|
|
|
|||
|
|
@ -10,9 +10,9 @@ two annoying problems with the [OS/2 FOOTBALL Boot Disk](/disks/pcx86/os2/misc/f
|
|||
and blank screens.
|
||||
|
||||
A hard-error popup would occur when FOOTBALL tried to initialize a non-existent PRN device. To resolve that, PCjs
|
||||
now provides basic parallel port emulation, in the form of a [ParallelPort](/docs/pcx86/parallel/) component that you
|
||||
now provides basic parallel port emulation, in the form of a [ParallelPort](/pubs/pcx86/parallel/) component that you
|
||||
include in a machine XML file with the <parallel> element, in much the same way you include the
|
||||
[SerialPort](/docs/pcx86/serial/) component with the <serial> element. This [Compaq DeskPro 386]
|
||||
[SerialPort](/pubs/pcx86/serial/) component with the <serial> element. This [Compaq DeskPro 386]
|
||||
(/devices/pcx86/machine/compaq/deskpro386/ega/4096kb/debugger/) machine used to run FOOTBALL has now been updated to
|
||||
include one parallel port.
|
||||
|
||||
|
|
|
|||
|
|
@ -115,7 +115,7 @@ Some notes:
|
|||
<script type="text/javascript">embedPC("ibm5150","machine.xml","components.xsl","{state:null}");</script>
|
||||
```
|
||||
|
||||
While the [PCx86 Documentation](/docs/pcx86/) explains how to create a *new* machine, by writing your own machine
|
||||
While the [PCx86 Documentation](/pubs/pcx86/) explains how to create a *new* machine, by writing your own machine
|
||||
XML file and manually copying all the other pieces, the new **Save Machine** feature is the best way to save
|
||||
any *existing* IBM PC and embed it on any other website.
|
||||
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ All the browsers I've tested so far (Chrome, Firefox, and Safari) support a
|
|||
which eliminates much of the fuzziness that would occur when copying pixels from the lower-resolution *buffer* canvas
|
||||
to the higher-resolution *screen* canvas.
|
||||
|
||||
So I've added a new [Video](/docs/pcx86/video/) property named *smoothing* that can be set to "true" or "false",
|
||||
So I've added a new [Video](/pubs/pcx86/video/) property named *smoothing* that can be set to "true" or "false",
|
||||
and I've set it to "false" for most machines in the project. If *smoothing* is not set, your browser continues to
|
||||
use its default interpolation method.
|
||||
|
||||
|
|
@ -66,7 +66,7 @@ while the right one does not.
|
|||
Aspect Ratio
|
||||
---
|
||||
|
||||
The *smoothing* property joins another recent [Video](/docs/pcx86/video/) property, *aspect*, that was added in a
|
||||
The *smoothing* property joins another recent [Video](/pubs/pcx86/video/) property, *aspect*, that was added in a
|
||||
[release](https://github.com/jeffpar/pcjs/releases/tag/v1.21.5) last month.
|
||||
|
||||
To recap, aspect ratio is display width divided by display height, but the choice of aspect ratio is complicated by
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@ and then embed the machines in the post, each with a single line:
|
|||
{% include machine.html id="vt100" %}
|
||||
{% endraw %}
|
||||
|
||||
For people rolling their own web pages, [the basics](/docs/pcx86/) haven't changed, and adding a serial connection merely
|
||||
For people rolling their own web pages, [the basics](/pubs/pcx86/) haven't changed, and adding a serial connection merely
|
||||
requires adding a *connection* property (eg, `connection:"com2->vt100.serialPort"`) to the *parms* parameter passed to the
|
||||
*embedPCx86()* interface. A similar property (eg, `connection:"serialPort->ibm5170.com2"`) must also be added to the *parms*
|
||||
passed to *embedPC8080()*.
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ I have no recollection of how feasible I thought this challenge was, but I'm sur
|
|||
Perhaps my thinking was that, after all, it's just software, so how hard could it be. In any case, I apparently took
|
||||
the challenge very seriously, because I also made a lot of notes.
|
||||
|
||||
I recently found [those notes](/docs/personal/#dbase-iii-copy-protection), along with copies of the
|
||||
I recently found [those notes](/pubs/personal/#dbase-iii-copy-protection), along with copies of the
|
||||
[dBASE III disks](/disks/pcx86/apps/other/dbase3/1.0/) used. Unfortunately, all the disks contained was my *patched*
|
||||
(unlocked) version of `DBASE.EXE`, and for the sake of a complete archive, I wanted the *unpatched* (locked) version as
|
||||
well. Fortunately, my patching notes also show all the original bytes, so I reproduced the original file by reversing
|
||||
|
|
|
|||
Loading…
Reference in a new issue