In article<j7n915$u76$1@localhost.localdomain>,
Martin Gregorie<martin@address-in-sig.invalid> wrote:
On Wed, 19 Oct 2011 13:27:30 +0000, blmblm@myrealbox.com wrote:
Once upon a time you could proofread javadocs with a frames-capable
text-mode browser (such as elinks). Not so much with Java 7,
alas .... Maybe a rant for another thread, but at least a return from
topic drift?
Have you any idea why?
Why what? Why "not so much"? because that may be a bit of an
exaggeration -- but the HTML produced by the Java 7 "javadoc" tool
has a fairly different look from what was produced by previous
versions, and it explicitly complains if you use a browser that
doesn't support Javascript, and .... :
I prefer just tried lynx, which I prefer to elinks, on a Java 6 javadocs
set. It did a reasonable job despite insisting on the non-frames set of
pages. Apart from that, the worst you can say about it is that its
formatting of method parameters with long fully qualified types is
somewhat untidy.
Generally I also prefer lynx, but it doesn't support frames, and
elinks does, and to me that makes a difference for this use case.
Anyway, try either one on on a Java 7 javadocs set -- both still
display the content, but IMO the formatting is noticeably less
satisfactory than for Java 6,