More README updates

This commit is contained in:
Jeff Parsons 2015-12-11 09:26:19 -08:00
commit 78267b2e92
22 changed files with 188 additions and 48 deletions

View file

@ -1,3 +1,9 @@
---
layout: page
title: Application Archives
permalink: /apps/
---
Application Archives
---
Browse classic [IBM PC](pc/) and [Challenger 1P](c1p/) software that you can run with [PCjs](/docs/about/pcjs/)

View file

@ -1,8 +1,16 @@
---
layout: page
title: Challenger 1P Applications
permalink: /apps/c1p/
---
Challenger 1P Applications
---
See [GitHub](https://github.com/jeffpar/pcjs/tree/gh-pages/apps/c1p) for program listings and configuration files.
The C1P serial port has no configurable hardware features. However, there is a "demo" property that can
be set, causing the machine to load some built-in demonstration code via the serial port when it starts up.
The purpose of these configuration files is to create UI controls that allow you to choose from a set of programs
The purpose of the configuration files is to create UI controls that allow you to choose from a set of programs
(eg, BASIC programs, 6502 machine code files) and send them to the C1P through the serial port.

View file

@ -1,3 +1,19 @@
---
layout: page
title: "VisiCalc (1981)"
permalink: /apps/pc/1981/visicalc/
machines:
- type: pc
id: ibm5150
config: /devices/pc/machine/5150/mda/64kb/machine.xml
state: /apps/pc/1981/visicalc/state.json
---
VisiCalc (1981)
---
{% include machine.html id="ibm5150" %}
VisiCalc History
---
See [http://www.bricklin.com/history/vcexecutable.htm](http://www.bricklin.com/history/vcexecutable.htm)

View file

@ -0,0 +1,15 @@
---
layout: page
title: "Executive Suite (1982)"
permalink: /apps/pc/1982/esuite/
machines:
- type: pc
id: ibm5160
config: /devices/pc/machine/5160/mda/256kb/fake188/machine.xml
state: /apps/pc/1982/esuite/state.json
---
Executive Suite (1982)
---
{% include machine.html id="ibm5160" %}

View file

@ -0,0 +1,15 @@
---
layout: page
title: "Rogue (1985)"
permalink: /apps/pc/1985/rogue/
machines:
- type: pc
id: ibm5160
config: /devices/pc/machine/5160/cga/640kb/machine.xml
state: /apps/pc/1985/rogue/state.json
---
Rogue (1985)
---
{% include machine.html id="ibm5160" %}

View file

@ -0,0 +1,15 @@
---
layout: page
title: "ThinkTank (1987)"
permalink: /apps/pc/1987/thinktank/
machines:
- type: pc
id: ibm5160
config: /devices/pc/machine/5160/cga/640kb/machine.xml
state: /apps/pc/1987/thinktank/state.json
---
ThinkTank (1987)
---
{% include machine.html id="ibm5160" %}

View file

@ -0,0 +1,9 @@
---
layout: page
title: "The Dungeons of Moria (1988)"
permalink: /apps/pc/1988/moria/
---
The Dungeons of Moria (1988)
---

View file

@ -0,0 +1,15 @@
---
layout: page
title: "The Dungeons of Moria (1992)"
permalink: /apps/pc/1992/moria/
machines:
- type: pc
id: ibm5160
config: /devices/pc/machine/5160/cga/640kb/machine.xml
state: /apps/pc/1992/moria/state.json
---
The Dungeons of Moria (1992)
---
{% include machine.html id="ibm5160" %}

View file

@ -1,3 +1,9 @@
---
layout: page
title: IBM PC Application Demos
permalink: /apps/pc/
---
IBM PC Application Demos
---
@ -15,7 +21,7 @@ Learn more about
[Application Demos](https://github.com/jeffpar/pcjs/tree/master/apps/pc) in the
[PCjs Project](https://github.com/jeffpar/pcjs) on [GitHub](https://github.com/).
<!--BEGIN:EXCLUDE-->
{% if page.developer %}
### Developer Notes: How To Produce A Demo
@ -61,4 +67,5 @@ the &lt;machine&gt; entry in the [Manifest](1981/visicalc/manifest.xml):
It's important to use a state file *only* with the machine configuration it was created with; in this case, we're OK,
because the only difference between the two chosen Model 5150 machines is the addition of the Debugger.
<!--END:EXCLUDE-->
{% endif %}