I’m Not Dead; Let’s Talk Rogue Trader

By Christopher Pye at 2009-10-18 – 9:00:03 | Comments (0) |

If you’ve gotten so lazy that you haven’t updated your blog in almost half a year, you’ve gotten pretty lazy. The last thing I posted was An Early Look at Rogue Trader Characters. Well, since then Rogue Trader has actually been released. Let’s have a look at the process of rolling-up a Rogue Trader character. Read More »

An Early Look at Rogue Trader Characters!

By Christopher Pye at 2009-06-18 – 22:17:03 | Comments (4) |

Breaking news, Dark Heresy and Rogue Trader fans!  Recently posted to the Rogue Trader official website are two bonus characters for Forsaken Bounty (the introductory Rogue Trader adventure, available freely on June 20th at Friendly Local Game Stores participating in Free RPG Day).  The two characters included in the PDF are “Malakai, a Missionary from the death world of Mortressa, and Dominik Van Goren, a nobly-born Void-Master and expert pilot.”  My anticipation grows!

Read More »

Radical’s Handbook and Rogue Trader News

By Christopher Pye at 2009-06-17 – 15:16:11 | Comments (0) |

Hello again, everyone!  Yes, I’m late with the conclusion to the Inquisitor’s Handbook review.  I promise that it is forthcoming, but things are a little hectic here now.  This quick little post should hold you over until I then.

Read More »

WordPress 2.8 Breaks XHTML1.0 Strict

By Christopher Pye at 2009-06-15 – 15:41:30 | Comments (2) |

See the title.  Patrick brought this to my attention earlier today, and I spent the better part of an hour hunting down the file that contained the erroneous snippet of wayward code.  It’s in the file wp-includes/general-templates.php, starting on line 124, and it looks something like this:

$form = ‘<form role=”search” method=”get” id=”searchform” action=”‘ . get_option(‘home’) . ‘/” >
<div><label for=”s”>’ . __(‘Search for:’) . ‘</label>
<input type=”text” value=”‘ . esc_attr(apply_filters(‘the_search_query’, get_search_query())) . ‘” name=”s” id=”s” />
<input type=”submit” id=”searchsubmit” value=”‘. esc_attr__(‘Search’) .’” />
</div>
</form>’;

(please forgive the formatting, I’ve got to add some new things to the stylesheet for code snippets)

See that role=”search” bit?  Non-compliant with the XHTML 1.0 Strict standard.  If its giving you trouble as well just remove it.  I didn’t find anything else that breaks the Strict standard for my particular site, but if i do you can be sure I’ll complain about it here.

WordPress 2.8 – Pretentiousness You Can Cut With a Knife

By Christopher Pye at 2009-06-10 – 23:05:43 | Comments (3) |

So I was staring idly at my WordPress dashboard when I noticed a link to this video detailing some of the changes in WordPress 2.8Holy Shit.  They’ve got some nameless soft-spoken Englishman opening by comparing WordPress releases to jazz musicians, all while some jazz music is playing.  When the hell did my blogging software start shipping from the back room of a Starbucks?

All snarkiness aside, this looks good.  What remains to be seen, however, is whether or not they’ve had the good sense to stop shipping code that breaks standards compliance.  Just yesterday I had to manually edit the CSS file for Thickbox (no clue what it’s for, I only know it was breaking the CSS 2.1 compliance of my site).  Is that too much to ask?  I know that they can’t do anything about the javascripts or CSS files that third parties include with their plugins or themes (Sociable, I’m looking at YOU), but they could at least bother to be standards-compliant themselves (c’mon guys, set an example).

How’s this for a feature request?  Include a setting with WordPress that keeps track of whether or not I want to see standards-breaking plugins and themes when I search for them.  Is that so hard?  Just search the contents of whatever $developer uploads and scan any CSS files for nonsense like browser-specific element properties and CSS3-only properties and flag $developer’s package as bad and not worth using non-compliant, if appropriate.