easier to read when you are using a color capable browser.
This will not impact a text-only browser.
Changes include:
o Code cleanup
o Add CSS style's.
o Use the new CSS style's.
o Move double quotes to quotes where needed.
o Made the HTML (except for the header) html-compliant.
The usage of CSS makes it easy to merge later when/if needed.
Discussed on: www@
No objections from: www@
Submitted by: Daniel Gerzo <danger at rulez dot sk>
some bugs of the text-mode listings of the Gnats database:
- Shave 2 characters out of the submission date, by removing the
enclosing [] pair.
- Increase the width of the tracker field. It should now be wide
enough until PR standards/999999 (which is, hopefully, a very
long time).
- Decrease the width of Resp. to 10 characters, as the longer name
is now a bit shorter (after the removal of 'freebsd-' a while
back).
- Shorten the 'Description' a bit, to keep the entire listing at
less than 79 columns (which IIRC was broken by me in revision
1.45, during the split of HTML/text output in separate functions).
the last suggestion of Jie Cao from www/69780:
``3. If we strip the spaces at the beginning of the lines, we
can reduce the size with a further 90000 bytes.''
PR: www/69780
Submitted by: Jie Cao (gaoj (at) cpsc (dot) ucalgary (dot) ca)
database queries once again, because I've received complaints that the
HTML output mode of the PR query scripts outputs huge, bloated tables
after the style changes I made to beautify HTML output.
This moves all the visual tweaks of the output in a CSS stylesheet and
add a $t_style option to the common cgi-style.pl script. If not set,
the style defaults to empty, but users of cgi-style.pl can set this to
a local CSS style like this:
$t_style="<style type=\"text/css\">...</style>";
or use it to refer from the header of the HTML output to an external
CSS stylesheet.
The HTML output size is substantially reduced now (at least 50% of the
size was caused by many repetitions of style="" attributes), but it's
still larger than the preformatted <pre> output because of all the
<tr> and <td> tags.
- Use a <table> to align data for HTML output similar to the one used by
CVSweb to list directory contents. This helps the eye to pick the
right line to click on when picking PRs to read from a long list.
Approved by: ceri, linimon, simon, silence on -www
freebsd-bugs already.
Add a micro-optimization to this test, which should just about make
up for checking two strings instead of one for most pr's.
Reviewed by: ceri
pull-down box that defaults to "All", but has options for
"Pre-5.x", "4.x", "5.x", "3.x" and "2.x".
Give query-pr.cgi the full PR path. This will allow a future
query-pr.cgi to skip looking through the whole GNATS index to
display a PR.
This allows us to search for all those PRs assigned to 're' without
adding the ones assigned to 'reg', or 'mi' and 'mike', etc.. Finally
I hope to have PR email that only contains the PRs that were really
meant for me.
Now that we have 5-number PRs and a 5 letter category, we also had run-on words.
o [1999/02/12] ports/10036billf New port - fltk
is now
o [1999/02/12] ports/10036 billf New port - fltk
Get bug categories from gnats directly (remove hard coding)
Create project/mailing list definitions and use them.
Make some of the perl code cleaner (my fault for bad original coding styles).
