[racket-dev] A grab-bag of issues

A few minutes ago, Matthew Flatt wrote:
> At Fri, 5 Jul 2013 18:55:32 -0400, Eli Barzilay wrote:
> > Yesterday, Matthew Flatt wrote:
> > > At Thu, 4 Jul 2013 12:52:10 -0400, Sam Tobin-Hochstadt wrote:
> > > 
> > > > 2. It's possible to get lots of undefined tags in the documentation
> > > > builds.  Should this be remedied with more build dependencies, or
> > > > will it be fixed with the online documentation server, or
> > > > something else?
> > > 
> > > Mostly through an online documentation server and declaring certain
> > > documentation links to be "indirect" (which may sometimes involve
> > > adjusting the documentation content).
> > 
> > If the documentation requires consulting a server, then why distribute
> > them in the first place?
> 
> Reading documentation does require a server. Following a link from
> installed documentation to uninstalled documentation requires a server.

OK (assuming a "does not" in the first sentence...).


> > There were a whole bunch of issues (most notably a lack of a full
> > text search) that are much easier to deal with if the
> > documentations are all on-line.
> 
> While I am interested in exploring installations where all
> documentation is online, there are also issues that seem harder to
> handle with exclusively online documentation (most notably, aspects
> of DrRacket's support for connecting code to documentation).

(I think that these should be easy with just having the same files on
the server, where drr can grab them and use them.  That's except for
jumping straight to some specific documentation, which would be done
by the server, probably via a url that is formatted according to the
source module etc.)

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!