Re: [boost] javascript in docs

From: Robert Ramey (ramey_at_[hidden])
Date: 2007-05-30 22:48:24

David Abrahams wrote:
> on Mon May 28 2007, Rene Rivera <grafikrobot-AT-gmail.com> wrote:
>
>> David Abrahams wrote:
>>> I would also like library authors to be mindful of the fact that
>>> we're trying to move to a (more) consistent look & feel for Boost
>>> documentation, so I would prefer if we only used JS that is
>>> generally accepted for future adoption (e.g. Jonathan Turkanis'
>>> menu control).
>>
>> There's also the consideration of adopting, as in allow use of and
>> include someplace common, an external JS library. There are numerous
>> JS libraries out there that smooth out most of the cross-browser
>> incompatibilities. And that way we would leave the testing and
>> maintenance to JS experts.
>
> Yes, hooray for libraries!

As I recall, the whole question was launched by the inclusion of
a JS index in the serialization library documentation.  This violated
boost guidlines but I believe that this objection was overridden
by the manifest utility of such a "documentation navigator".  This
sparked Jonathan's effort to make a better more definitive
implementation which I believe was tested on all browsers
that we use.

Note that if this tree "navigator" were automatically generated
and inserted as part of the documentation build, it could be
replaced by some other implemenation just by changing
the build script.  So I don't see this fact that we may find
an implementation which is somewhat better as any reason
for making an improvement using what we currently have
available.

Robert Ramey