<ulclass="toc"><li><ahref="M-ui.html#SP1">§1. What Inblorb is</a></li><li><ahref="M-ui.html#SP2">§2. Inblorb at the command line</a></li><li><ahref="M-ui.html#SP3">§3. Inblorb within the Inform user interface</a></li></ul><hrclass="tocbar">
<pclass="commentary firstcommentary"><aid="SP1"></a><b>§1. What Inblorb is. </b>Inblorb is a command-line tool which forms one of the components of the
<pclass="commentary firstcommentary"><aid="SP2"></a><b>§2. Inblorb at the command line. </b>If you have compiled the standard distribution of the command-line tools
for Inform then the Inblorb executable will be at <spanclass="extract"><spanclass="extract-syntax">inblorb/Tangled/inblorb/</span></span>.
<pclass="commentary">The OPTIONS are very simple. Inblorb's predecessor cBlorb needed to be told
what platform it was running on, by specifying <spanclass="extract"><spanclass="ConsoleText-extract-syntax">-osx</span></span>, <spanclass="extract"><spanclass="ConsoleText-extract-syntax">-windows</span></span> or
<spanclass="extract"><spanclass="ConsoleText-extract-syntax">-linux</span></span> at the command line, but these have gone. What remains is:
<pclass="commentary"><spanclass="extract"><spanclass="ConsoleText-extract-syntax">-verbose</span></span> causes Inblorb to print a running narrative of what it's doing;
<pclass="commentary"><spanclass="extract"><spanclass="ConsoleText-extract-syntax">-project X</span></span> tells Inblorb to assume the usual settings for this project,
which means that BLURBFILE is set to <spanclass="extract"><spanclass="ConsoleText-extract-syntax">X/Release.blurb</span></span> and BLORBFILE
to <spanclass="extract"><spanclass="ConsoleText-extract-syntax">X/Build/output.gblorb</span></span>. <spanclass="extract"><spanclass="ConsoleText-extract-syntax">X</span></span> is usually something like <spanclass="extract"><spanclass="ConsoleText-extract-syntax">Whatever.inform</span></span>.
<pclass="commentary firstcommentary"><aid="SP3"></a><b>§3. Inblorb within the Inform user interface. </b>This is the sequence of events when the user clicks Release in the user
</li><li>(3) If no Problems occur, the compiler generates Inform 6 code, and also
two additional files for the project's <spanclass="extract"><spanclass="ConsoleText-extract-syntax">Build</span></span> folder:
<ulclass="items"><li>(a) <spanclass="extract"><spanclass="ConsoleText-extract-syntax">Metadata.iFiction</span></span>, an iFiction record;
</li><li>(b) <spanclass="extract"><spanclass="ConsoleText-extract-syntax">Release.blurb</span></span>, a blurb file of instructions for Inblorb to follow later.
<li>(4) The interface next calls the Inform 6 compiler. The interface calls it
with the <spanclass="extract"><spanclass="ConsoleText-extract-syntax">S</span></span> and <spanclass="extract"><spanclass="ConsoleText-extract-syntax">D</span></span> switches, for strict checking and for debugging, off
</li><li>(5) Inform 6 having returned 0 to indicate success, the interface next calls
Inblorb as follows. Let <spanclass="extract"><spanclass="ConsoleText-extract-syntax">Path</span></span> be the path to the folder containing the Inform
project being released, which we'll call <spanclass="extract"><spanclass="ConsoleText-extract-syntax">This.inform</span></span>. Then the interface
an HTML page to be displayed on the Problems tab. This is <spanclass="extract"><spanclass="ConsoleText-extract-syntax">StatusCblorb.html</span></span>,
in the project's <spanclass="extract"><spanclass="ConsoleText-extract-syntax">Build</span></span> folder. (This is a change made in 2010: in the past,