Not quite sure about the way I pass the required theme vars in class-wp-themes-list-table.php (line 176), but this way I can pass a subset of the entire theme array, just what I need. Array keys are with capitals and spaces in that file, so we always need a way to convert them to lowercase and underscore versions (to match the object variabels from wp-admin/themes.php).

The alignment on 17944-new-text-active-2.png is slightly strange - I would keep the margin-left created by the theme screenshot and have the text align with the other text above it. Full screenshot rather than crop would be helpful - to get a better idea of information hierarchy.

The alignment on 17944-new-text-active-2.png is slightly strange - I would keep the margin-left created by the theme screenshot and have the text align with the other text above it. Full screenshot rather than crop would be helpful - to get a better idea of information hierarchy.

Added two fullscreen screenshots. I think the alignment is correct this way. To illustrate that, I've added a screenshot of an active Twenty Ten install, where the new paragraph is aligned next to the screenshot. Here you can see that the margin is the same on both sides.

Yep - you're right, I take it back. Looks pretty good to me, only other thing that stands out to me personally is that I would probably opt to say "uses template files from /xxx/" rather than "uses templates from /xxx/" - but Jane will be able to offer better insight on that one as she has a far wider knowledge of the nuances between terms like this throughout the rest of core.

We now hide tags, and bury file locations inside a 'Details' link by default.

I've always thought of these file paths as potentially useful but ultimately extraneous information for the vast majority of users, not to mention an eyesore. Do we honestly need them? I'm not decreeing "No," but I'm suggesting we need to really think about it.

As a practical matter, this needs to be updated to use WP_Theme.

Secondarily, there is the potential that a parent theme is invalid for the current theme on disk (and in WP_Theme) but not for what is the current 'template' option in the DB. This makes for fun failures: 20921#comment:1.