y.st./source/pages/en/weblog/2015/07-July/09.xhtml

<?php
/**
 * <https://y.st./>
 * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => 'More Minetyst work',
	'body' => <<<END
<p>
	PayPal hasn&apos;t written back about the donation on behalf of the website yet.
</p>
<p>
	The first minetest_game module I started work on converting today was screwdriver.
	It seemed pretty easy to make work with Minetyst at first, but when I went to test the thing, I found an oddity.
	The singular tool created by this module, when run through libtools, could not be placed as a node! It seems that while I was away, screwdriver undertook a major upgrade.
	Instead of cycling through four different tools, each with a different capability, all the functionality has been stuffed into two distinct actions.
	A single screwdriver tool implements one of these functions upon left clicking (normally used for digging) and the other upon right clicking (normally used for placing nodes).
	Because the right click function was tied up, the tool could not be placed normally.
	It&apos;s not the cleanest workaround, but I&apos;ve modified the screwdriver to allow itself to be placed if the player is holding the shift key when attempting to place it.
</p>
<p>
	In the process, I ended up completing my libtools module.
	Now, the attached_node group is implemented, and tools no longer float in mid air when the node they are resting on is removed.
	The catch is that I had to override one of the built-in functions with a slightly-modified version of itself.
	The reason I don&apos;t like doing this is that if this function is changed in the main engine at some point, I may not notice right away and continue using the copy of the old code now present in my module.
	It&apos;s not clean, but for now, it&apos;s the best I can come up with.
</p>
<p>
	Third, I built a new module called <code>debug</code> and modified every module to have a soft dependency on it.
	For now, all it does is enforce that all modules that load after it create, at most, a single global variable, and this global variable must have a very specific name based on the name of the module that defines it.
	I think it also throws errors if you try to access undefined variables, but I have yet to test this.
	Even if it works, I may remove it later.
	The intent is to include any debugging code here that helps make sure the rest of my code is as error-free as possible.
	In theory, once code is written to function with the debug module, removing the debug module will have no effect.
</p>
<p>
	Yesterday, a coworker of mine set up a joke for the rest of us.
	Our new refrigerator has a label that says &quot;IB Imperial Brown&quot;.
	Guessing by the fact that this label inhabited a hole in the protective plastic before the plastic was fully removed, I thing the hole was torn to add the label.
	The label therefor may not be the brand of the refrigerator, but instead, the company that installed it.
	Anyway, this coworker taped a printout of a sketch of Doc Brown from Back To The Future and covered the word &quot;Imperial&quot; with the word &quot;Doc&quot;.
	It now reads &quot;IB Doc Brown&quot; (said out loud as &quot;I be Doc Brown&quot;, as if he is introducing himself using bad grammar).
	Hoping to have my mobile on hand next time I run into the guy, I bought <a href="https://professorshyguy.bandcamp.com/album/80s-ep-magprom">80s Ep (MAGProm)</a>, as it contains a cover of (one of?) the cover song(s?) from the same movie.
	I won&apos;t watch the movie again, as I have left proprietary media behind, but Professor Shyguy&apos;s cover is under {$a['CC BY-SA 3.0']}, so I don&apos;t mind keeping it with me and playing it.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
END
);