y.st./source/pages/en/weblog/2015/04-April/12.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' => 'The weblog index is complete',
	'body' => <<<END
<p>
	I updated the &quot;weblog&quot; link to point directly to <code>/weblog/2015/</code> instead of <code>/weblog/</code>, as there are no other files in that directory yet, and there won&apos;t be for some time.
</p>
<p>
	$a[PHP]&apos;s <code>dir()</code> function returns an object that cannot be iterated over.
	The intuitive thing to do is to iterate over the directory with a <code>foreach</code> statement, but that simply cannot be done.
	Instead, every time I need to iterate over a directory in $a[PHP], I have to look up the proper method to do it again.
	Tired of this, and still trying to build up my $a[PHP] toolbox, I built a simple generator function that can be used in the intuitive way.
	However when I tested it, I was quickly reminded of the fact that $a[PHP] does not return the contents of a directory in the intuitive (alphabetical) order.
	Instead, the directory contents are returned in whatever order they are stored in on disk.
	For many use cases, this doesn&apos;t matter, but in some, it&apos;s a pain to deal with.
	I reworked the function, changing it from a generator function to a regular function that returns an array of alphabetized file names.
</p>
<p>
	After coding that much-needed function, I set about trying to figure out how I wanted to parse month information out of directory names.
	I ended up deciding that anything I came up with would cost more computational power than just hard coding the names I use for month directories into my script.
	It seems messy to do that, but everything else I could come up with was messier.
	As a result, I ended up not needing the alphabetizing of directory contents for the time being, though it is still nice to have for later.
	You can&apos;t predict what order things will land on the file system, but you can predict the results of an alphabetized listing.
</p>
<p>
	Using $a[CSS] a flex box, I set the $a[ASCII] calendar pages to display side by side on weblog year index page.
	At this point, the weblog month index pages are pretty much deprecated.
	The will continue to exist in case there are any existing links to them and in case someone tries to reach them by deleting the file name from the $a[URI] of a weblog entry page, but no links to them will exist on my site any more.
	Using a flex box introduced a bug in the mobile version of the site due most likely to the mobile browser not supporting flex boxes.
	This seems strange to me, as small screens are where you would need flex boxes the most.
	Adding a <code>text-align</code> attribute (which is ignored by Web browsers that support flex boxes) made the mobile version of the site display better, though I don&apos;t think it will provide the desired results on larger mobiles, such as tablets.
</p>
<p>
	I did a little experimenting today, and found that Cricket has indeed cut off my telephony properly.
	However, they have not cut off my data access, and I still have full Internet connectivity.
	This seems like a huge oversight in their system to me.
	Personally, I never use telephony if I can at all avoid it.
	The value of the connection to me lies entirely in the Internet access.
	I don&apos;t know why their system has not cut me off, but I know this is too good to last forever.
	My guess is that the connection will die completely after the 60 day suspension period has ended.
</p>
<p>
	Another benefit of the new calendar setup for the weblog index is that it acts as a sort of second <a href="/a/canary.txt">canary</a>, though this was not at first the intention.
	I write in my weblog every day, so if any day is missing from the calendar, it will stick out like a sore thumb.
</p>
END
);