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

Reorganized PCjs settings

Browse source
This commit is contained in:
Jeff Parsons 2015-12-14 08:22:07 -08:00
commit 8fcdff0a3e
11 changed files with 107 additions and 94 deletions
Download patch file Download diff file Expand all files Collapse all files

4
_posts/2014-04-14-node-express-safari.md
View file

@ -9,12 +9,12 @@ permalink: /blog/2014/04/14/
There's something very odd going on with between Node+Express and Safari, resulting in blank web pages.
Don't believe me? Just ask [Google](https://www.google.com/#q=node+express+safari+blank+page).
[{{ site.pcjs_domain }}]({{ site.url }}/) contains a lot of XML files that are rendered as web pages using XML
[{{ site.pcjs.domain }}]({{ site.url }}/) contains a lot of XML files that are rendered as web pages using XML
stylesheets. And occasionally Safari -- and ONLY Safari -- will render those XML files as blank pages.
For example, here's the
[machine.xml](/devices/pc/machine/5150/mda/64kb/machine.xml) file that's also embedded on the
[{{ site.pcjs_domain }}]({{ site.url }}/) home page.
[{{ site.pcjs.domain }}]({{ site.url }}/) home page.
When Safari fetched that XML file from an Apache web server (what I used before switching to Node),
the request would look like:

4
_posts/2015-01-17-pcjs-uncompiled.md
View file

@ -11,7 +11,7 @@ machines:
uncompiled: true
---
Most machines on [{{ site.pcjs_domain }}](/) run with a compiled version of PCjs, which is produced
Most machines on [{{ site.pcjs.domain }}](/) run with a compiled version of PCjs, which is produced
by running PCjs JavaScript source code through Google's Closure Compiler, yielding a smaller (minified)
version that loads and runs much faster than the original source code.
@ -21,7 +21,7 @@ or file location). Once the BACKTRACK feature is finished, it will be folded in
then, the only way to experiment with it is by running the uncompiled code.
To make it easier to launch machines with uncompiled code, a PCjs machine definition can now set `uncompiled`
to *true*, overriding the value of `site.pcjs_compiled` in **_config.yml**.
to *true*, overriding the value of `site.pcjs.compiled` in **_config.yml**.
Here's what a typical Markdown file would look like:

2
_posts/2015-12-10-rebuilding-the-pcjs-website.md
View file

@ -71,7 +71,7 @@ and `id` can be any identifier you want to use to embed the machine. You may al
configuration file if not using the default `machine.xml`; `template` to specify an alternate XSL template file if not
using the default `components.xsl` file; `state` to specify a JSON-encoded machine state file if the machine requires a
predefined state; and `uncompiled` may be set to *true* to force a machine to use uncompiled sources, overriding the
value of `site.pcjs_compiled` in **_config.yml**.
value of `site.pcjs.compiled` in **_config.yml**.
For example, the PCjs home page contains two machines, and so this appears at the top of the root [README.md](https://raw.githubusercontent.com/jeffpar/pcjs/gh-pages/README.md):