Autopower support in place

This commit is contained in:
Jeff Parsons 2016-02-10 10:28:11 -08:00
commit f2bfecd83f
5 changed files with 41 additions and 14 deletions

View file

@ -1,5 +1,6 @@
{% comment %}
As documented in /modules/markout/lib/markout.js, the following machine properties are recognized in Front Matter:
As documented in /modules/markout/lib/markout.js, our Node web server recognizes the following machine properties
in the Front Matter of Markdown files, for compatibility with the Jekyll web server:
'id' (eg, "ibm5150")
'name' (eg, "IBM PC (Model 5150) with Monochrome Display")
@ -9,25 +10,24 @@ As documented in /modules/markout/lib/markout.js, the following machine properti
'uncompiled' (eg, true)
'parms'
and the following properties (along with any property not listed above) will be added to the 'parms' property:
And the following properties (along with any property not listed above) will be added to the 'parms' property:
'autopower' (eg, "true")
'automount' (eg, {"A":{"name":"OS/2 FOOTBALL Boot Disk (v7.68.17)","path":"/disks/pc/os2/misc/football/debugger/FOOTBALL-7.68.17.json"}})
'state' (eg, "state.json")
'messages' (eg, "disk")
Of all the above properties, the following are purely cosmetic:
'name' (used by machine.html, not machine-engines.html)
And all our JavaScript components expect multi-word property names to use camelCase, so that conversion happens both
here and in markout.js. Examples include 'autopower' ('autoPower') and 'automount' ('autoMount').
{% endcomment %}
{% for machine in page.machines %}
{% capture machine_embed %}window.embed{{ machine.type | remove:'-dbg' | upcase }}{% endcapture %}
{% unless machine.autopower %}
{% if machine.autopower == nil %}
{% assign machine_autopower = "true" %}
{% else %}
{% capture machine_autopower %}{{ machine.autopower }}{% endcapture %}
{% endunless %}
{% endif %}
{% unless machine.config %}
{% assign machine_config = "machine.xml" %}
{% else %}