Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fixed a variety of broken links

Browse source
This commit is contained in:
Jeff Parsons 2017-02-08 20:33:13 -08:00 • committed by Jeff Parsons
commit b25c2dbdb7
9 changed files with 36 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/c1pjs/embed/README.md
View file

@ -21,13 +21,13 @@ If you want to read as little as possible, then just paste the following code on
```html
<div id="myC1P"/></div><div style="clear:both"></div>
<script type="text/javascript"
src="http://www.pcjs.org/versions/c1pjs/1.21.6/c1p.js">
src="http://www.pcjs.org/versions/c1pjs/1.34.0/c1p.js">
</script>
<script type="text/javascript">
window.embedC1P(
"myC1P",
"http://www.pcjs.org/devices/c1p/machine/8kb/embed/machine.xml",
"http://www.pcjs.org/versions/c1pjs/1.21.6/components.xsl"
"http://www.pcjs.org/versions/c1pjs/1.34.0/components.xsl"
);
</script>
```
@ -44,7 +44,7 @@ The order of the XML elements also determines the layout of the associated HTML
**&lt;keyboard&gt;** element appears before the **&lt;video&gt;** element, then the keyboard controls will be
displayed *above* the video display instead of *below*. There's an extensive set of attributes that you can add
to any of the elements below to style and position them, including the usual *style* attribute, but at present,
there's no documentation beyond the sample XML files and the default [XML stylesheet](/versions/c1pjs/1.21.6/components.xsl).
there's no documentation beyond the sample XML files and the default [XML stylesheet](/versions/c1pjs/1.34.0/components.xsl).
The example at the top of this page uses an [XML file](/devices/c1p/machine/8kb/embed/machine.xml) that looks like:
@ -81,7 +81,7 @@ Machine configuration files can also be "self-starting" if they contain the foll
top of the file:
```xml
<?xml-stylesheet type="text/xsl" href="http://www.pcjs.org/versions/c1pjs/1.21.6/machine.xsl"?>
<?xml-stylesheet type="text/xsl" href="http://www.pcjs.org/versions/c1pjs/1.34.0/machine.xsl"?>
```
For example, here's a self-starting [machine.xml](/devices/c1p/machine/8kb/large/machine.xml) configuration.
@ -130,11 +130,11 @@ Step 3: Add the C1Pjs Simulator to your web page
Somewhere on your page, you need to add the following **&lt;script&gt;** element:
```html
<script type="text/javascript" src="http://www.pcjs.org/versions/c1pjs/1.21.6/c1p.js"></script>
<script type="text/javascript" src="http://www.pcjs.org/versions/c1pjs/1.34.0/c1p.js"></script>
```
To include the C1Pjs Debugger, use [c1p-dbg.js](/versions/c1pjs/1.21.6/c1p-dbg.js) instead of
[c1p.js](/versions/c1pjs/1.21.6/c1p.js), and include some additional definitions in your machine
To include the C1Pjs Debugger, use [c1p-dbg.js](/versions/c1pjs/1.34.0/c1p-dbg.js) instead of
[c1p.js](/versions/c1pjs/1.34.0/c1p.js), and include some additional definitions in your machine
definition XML file:
```xml
@ -171,7 +171,7 @@ The **embedC1P()** function accepts three parameters:
- the *id* attribute of the HTML element that will contain the simulator (eg, 'myC1P');
- the URL of your machine definition XML file (eg, 'embed.xml', since it's on the same server);
- the URL of an XML stylesheet; unless you've created your own stylesheet, it's recommended you omit this
parameter and use the default [XML stylesheet](/versions/c1pjs/1.21.6/components.xsl).
parameter and use the default [XML stylesheet](/versions/c1pjs/1.34.0/components.xsl).
Step 5: Enjoy!
---
@ -179,7 +179,7 @@ All I ask is that any page that embeds the simulator also includes attribution,
> [PCjs](http://pcjs.org) © 2012-2017 by [Jeff Parsons](mailto:Jeff@pcjs.org) ([@jeffpar](http://twitter.com/jeffpar))
If you use the default [XML stylesheet](/versions/c1pjs/1.21.6/components.xsl), attribution is automatically inserted,
If you use the default [XML stylesheet](/versions/c1pjs/1.34.0/components.xsl), attribution is automatically inserted,
which relieves you from including it yourself.
Feel free to copy any or all of the files listed above to your own server (it's probably better to share the server