[x] make a link to the github repository interface and issue tracker.
[x] add a "help icon" to each page that points to the CorTeX wiki on
github (these pages can be initially empty).
[x] add a "bug icon" that points to the github issue tracker.
That would streamline the feedback and documentation cycle.
and Bruce:
[ ] on corpus-report, the statistics pulldown should default
to "modern" if that's the only choice.
[ ] I'm getting scroll bars when none really should be needed;
probably too many fixed widths in laying out the table?
[ ] The numbers in the columns, since they have fixed decimal,
should be right justified.
[ ] Another quibble: CSS this time; I love the hover over box, but (having just fixed (I hope)
such a bug in DLMF),
when you add a couple of pixels border, you want to subtract the same
dimension in padding or margin; otherwise the whole page
"breathes" as you move the mouse around.
Cool the first time you see it, disturbing afterwards...
[ ] ALSO, the whole row gets "highlighted", but only the icon is clickable,
which is a sort of misdirection.
[x] Now I bore down to fatals and I can see a bunch of the reports
at the same time! This looks quite useful!
Particularly for the "major rewrite introduced lots of little bugs"-mode
[ ] However, a bunch are "timeout", but just listed under "Perl died";
Hmm.... but those have an explicit "Fatal:conversion:timeout" so
shouldn't those have been classified?
[ ] I also see a couple of "alarm" but that appears to be timeout code?
[ ] Another quibble is that your page (apparently) has arranged for it's own
scrollbar (I don't think you're using frames, are you?)
But that scrollbar appears at the bottom of a really long list of error reports
which are all scrolling off the RHS. Effectively, I can't scroll to see
the whole report, since the scrollbar isn't visible.
But wouldn't it be better to just leave the scrollbar up to the browser?
[ ] Hmm... [.tex] button is gives me a file named "browse" with no mimetype!
Too much javascript;
Just use a link to the file, then you get a sane filename, and extension
so that my browser knows what to open the file with.
[ ] For that matter, might be better to fold the [tex][html][log] into
the first couple of columns, where there's lotsa space rather than
off the right screen edge.
But maybe I need to see non-error reports first...
[ ] When you bore down through the tree, expanding, closing, etc;
It takes a little time (using ajax, I assume?); That's forgivable,
but when you select a report detail
(ie. show all docs with that particular state),
and THEN go back; the tree's collapsed; that's both disorienting
if you can't quite remember how you got there, and time consuming
to reopen. I know that javascript doesn't make it easy to remember such state;
but reporting that it is awkward from a user perspective.
A batch of UI feedback from Michael:
and Bruce: