<nadpis>Release v0.17</nadpis>

	<m:release>v0.17</m:release>

			This release improves and standardizes the CLI interface of several tools, brings a new output module + several smaller improvements.

				<strong>The <code>relpipe-in-cli</code> module has changed CLI interface</strong>: see details below

			</li>

				<strong>The <code>relpipe-in-csv</code> module has changed CLI interface</strong>: see details below

			</li>

			<li>

				<strong>The <code>relpipe-out-csv</code> module has new CLI interface</strong>: see details below

			</li>

				<strong>The <code>relpipe-out-tabular</code> module has new CLI interface</strong>: see details below

			</li>

				<strong>The <code>relpipe-tr-guile</code> was renamed to <code>relpipe-tr-scheme</code></strong>: see details below

			</li>

			<li>

				<strong>New tool <code>relpipe-out-jack</code> for generating MIDI through JACK</strong>: see details below

			</li>

		<h2>New CLI interfaces</h2>

			Several earlier tools have non-standard CLI interface and does not conform with <m:a href="principles">principle</m:a> „Use --long-options“.

			Posistional parameters might be shorter but they are also cryptic and less flexible.

			In this release the <code>relpipe-in-cli</code>, <code>relpipe-in-csv</code> tools dropped their old CLI interface

			and got a new one based on named parameters and long options.

			The <code>relpipe-out-csv</code> and <code>relpipe-out-tabular</code> had no parameters in previous versions and now have standard CLI interface.

			In <code>relpipe-out-tabular</code> we can now optionally omit several parts:

			<code>--write-record-count false</code>,

			<code>--write-types false</code>,

			<code>--write-relation-name false</code>

			and thus simplify the output if we do not need given information.

		<pre><![CDATA[ ╭───────┬────────╮

 │ first │ second │

 ├───────┼────────┤

 │     1 │ abc    │

 │     2 │ def    │

 ╰───────┴────────╯]]></pre>

		<p>

			These options may be set globally or for particular relation using the <code>--relation</code> option with pattern parameter.

			Thus we may e.g. print some relations with data types and some without them.

		</p>

			Remaining tools that will be transformed in the same way: <code>relpipe-tr-grep</code>, <code>relpipe-tr-cut</code>, <code>relpipe-tr-sed</code>

			and will get standard CLI interface.

		<h2>JACK (MIDI) output module</h2>

		</p>

		<p>

			In the <m:a href="release-v0.16">v0.16</m:a> release, the <code>relpipe-in-jack</code> was introduced.

			This tools allowed capturing the MIDI events from JACK and sending them to the relational pipeline.

			Now, in v0.17, we introduce the counterpart tool <code>relpipe-out-jack</code> that reads relational data

			and sends SysEx messages, MIDI notes and other events to the JACK pipeline.

		<m:img src="img/jack-connections-2.png"/>

			We can join the JACK graph with <code>relpipe-out-jack</code> command.

			It does not produce anything on STDOUT, it sends MIDI events to JACK instead, so no other output data are needed.

			Besides capturing and playing the MIDI, we can use the <code>relpipe-in-jack</code> and <code>relpipe-out-jack</code>

			to tak a snapshot of the JACK graph (connections between ports) and recreate it later.

			Or establish any new connections or break existing ones.

			Either through CLI commands of <code>relpipe-in-jack</code> or through relational data (list of connection and disconnection commands)

			sent to <code>relpipe-out-jack</code>.

		</p>

		<p>

			Both commands have also the <code>--required-connections</code> and <code>--connect-to</code> parameters,

			so they can react on reaching particular connection count or automatically connect their port to another one specified on the CLI.

			The bash-completion suggests available port names.

		</p>

		<p>

			More details in the examples:

			<m:a href="examples-jack-ports">Working with JACK ports</m:a>

			and <m:a href="examples-jack-midi-generating-1">Generating and sending MIDI messages</m:a>.

			<li m:since="v0.10">scheme: filtering and transformations defined in the Scheme language using GNU Guile</li>

			<li m:since="v0.17">JACK</li>

			<li><m:a href="examples-jack-ports">Working with JACK ports</m:a></li>

			<li><m:a href="examples-jack-midi-generating-1">Generating and sending MIDI messages</m:a></li>

			The <code>relpipe-tr-guile</code> has been renamed to <code>relpipe-tr-scheme</code>, so it is necessary to modify existing scripts.

			However the CLI interface has not been changed, thus it can be simply updated e.g. by:

		<m:pre jazyk="bash">sed s/relpipe-tr-guile/relpipe-tr-scheme/g -i script.sh</m:pre>

			The reason behind this rename is that Scheme is a programming language and Guile is one of implementations of this language.

			And we prefer <a href="https://sane-software.globalcode.info/v_0/#a0f42ec9-5032-4f6d-a50a-4b7bddde77f0">depending on interfaces</a> rather than on particular implementations.

			Similar situation is <code>relpipe-tr-sql</code>: this module is also named after the language (SQL), not after the default implementation (SQLite)

			and this module can use <m:a href="examples-tr-sql-odbc">any SQL engine</m:a>.

			The CLI interface of the <code>relpipe-in-cli</code> tool has been standardized and made consistent with other tools.

			Now, it uses named parameters instead of cryptic positional ones.

			The format of the STDIN stream remains unchanged (values separated by <code>\0</code> byte).

		</p>

		<m:pre jazyk="bash"><![CDATA[# Old syntax before v0.17:

relpipe-in-cli generate "relation_from_cli" 3 \

	"a" "integer" \

	"b" "string" \

	"c" "boolean" \

	"1" "Hello" "true" \

	"2" "World!" "false"

# New syntax:

relpipe-in-cli \

	--relation "relation_from_cli" \

		--attribute "a" integer \

		--attribute "b" string \

		--attribute "c" boolean \

		--record "1" "Hello" "true" \

		--record "2" "World!" "false"

]]></m:pre>

		<p>

			We can repeat these parameters and generate several relations (that was not possibel in the older version).

			One relation may be filled with values from STDIN: <code>--records-on-stdin true</code> (replaces the old <code>relpipe-in-cli generate-from-stdin</code> syntax).

			And the last relation may be filled with values from remaining CLI arguments: <code>--records "1" "Hello" "true" "2" "World!" "false"</code>.

			The demo (<code>relpipe-in-cli demo</code>) has been removed (sample data can be easily generated by setting the CLI arguments).

		</p>

		<p>

			The CLI interface of the <code>relpipe-in-csv</code> tool has also been standardized and made consistent with other tools.

			If we have attribute names on the first line of the CSV file (which is quite common), the usage is same as in previous versions:

		</p>

		<m:pre jazyk="bash"><![CDATA[cat file.csv | relpipe-in-csv]]></m:pre>

		<p>If we have only data in the CSV file (no headers) and thus want to specify them on CLI, the syntax is different:</p>

		<m:pre jazyk="bash"><![CDATA[# Old syntax before v0.17:

cat file.csv | relpipe-in-csv "my_relation" "a" integer "b" boolean

# New syntax:

cat file.csv | relpipe-in-csv \

	--relation "my_relation" \

		--attribute "a" integer \

		--attribute "b" boolean

]]></m:pre>

		<p>Bash-completion scripts for all tools are provided.</p>

		<p>

			Future versions should allow optionally storing the attribute data types in the CSV header and parsing them back (together with the attribute names).

		<m:pre src="examples/release-v0.17.sh" jazyk="bash" odkaz="ano"/>