From: William E. Kempf (williamkempf_at_[hidden])
Date: 2002-09-09 14:33:52
From: "Rozental, Gennadiy" <Gennadiy_at_[hidden]>
> > it can only be
> > viewed with certain web browsers, and those pages cannot be reliably
> > printed.
> I do not believe that is true.
You continue to make this argument, despite users giving you real world
boggles me. I've done quite a bit of HTML development and fully understand
make it work for target browsers. Boost documentation must target ALL
browsers, making this sort of usage extremely difficult, nearly impossible
should be banned. (Well, to be fair, I can envision a few cases where
abused, as I think it is now, then I'll vote for a total ban.)
> (it's better then let say C++ compilers conformance to C++ standart).
Again, real world examples have shown you to be wrong numerous times
already. People do all sorts of things with the HTML, not all of it using a
controlled, can render these uses impossible. I've yet to see a beneficial
so far fall under two categories: "Golly gee whiz bang" features, such as
the rollup menu, which serve no purpose other than to be eye candy, or to
send repetetive HTML to the output stream, which sounds like a legitimate
use, but there are ways to remove the repetitive nature here with out
Sorry, but this stuff isn't really portable, and "portable" usage means
detecting the browser, which in and of itself is often done in a manner
that's not 100% fool proof, is likely to break with the next version of the
browsers, and won't cover all target browsers in any event (since Boost is
totally open on this).
> is as important as usage of external style sheets.
Style sheets can't be compared to JS. Style sheets are 100% compatible for
all browsers/tools, since they can simply be ignored with no ill effect.
And as I've pointed out, there are better, more portable means of dealing
with repetitive tasks then using JS.
> Preprocessor docs hides bulky example to prevent obscuring reference page
> content. Note that MSDN site doing the same.
"Hiding" documentation may make the online docs easier to read (I should
have emphasised *may*, as that's debatable), but it interferes with printing
and other tasks. On the other hand, documentation that never attempts these
"whiz bang display" enhancements are generally easier to deal with for all
other tasks, and is debatably easier to use even for online documentation
> to the styling.
especially when the printing is done with out a browser with tools like an
HTML to Postscript utility.
> 6. According to recent info in net ~95-97 present of browsers domain is
> covered by ie and clones. Among the developers numbers are different of
> course but ie still prevail I think. All others browsers try to keep up
> de facto standard ie. Though I would not want to discuss this point too
I'm glad you said that, because usage patterns like this mean NOTHING to
this context. If I were designing an online website for banking, for
instance, I might be swayed by such data, but if there's a single Boost user
that's one user too many.
> could consider giving it at least some chances to be usable?
actual release. I can just imagine the trouble we'll see if it goes out in
a release. I'm not at all interested in wading through the complaints we're
likely to see on the mailing lists at that point.
becomes a much bigger issue.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk