[racket] Using new packages, step-by-step

On Mon, Mar 10, 2014 at 7:34 PM, Matt Jadud <matt at jadud.com> wrote:
> Hi Matthew,
>
> (Or, anyone else who chimes in...)
>
> I have not noticed whether there are rendered versions of 3rd-party library
> documentation anywhere.

Currently, there's no centralized place where you can read
documentation for libraries you haven't installed.  Lots of people
have put documentation up for their packages, though; here are two
examples:

http://soegaard.github.io/docs/metapict/metapict.html
http://takikawa.github.io/racket-quickcheck/

As you can see, GitHub pages is a good place for this.

However, we do recognize the benefit of central documentation, and
that's something we plan to address in the (reasonably near) future --
it's probably the biggest thing missing from the package system at
this point.

Sam


> Is the idea that I would:
>
> 1. git clone [lib]
> 2. open docs/...
>
> on my local machine if I'm curious about the library? (Or, install via IDE.)
> One of the features of the original repository that I really liked was the
> ability to browse documentation without having to pull down the library to
> my local machine.
>
>
> I thought I'd ask, in case the ability to read docs for libraries in the new
> package manager is already baked in, and I've somehow managed to fail to
> find it.
>
> Many thanks,
> Matt
>
>
>
> On Sun, Mar 9, 2014 at 10:23 PM, Matthew Flatt <mflatt at cs.utah.edu> wrote:
>>
>>
>> After either of those, searching documentation "memoize" should work,
>> and the docs say to use
>>>
>>>
>>  (require memoize)
>
>
> ____________________
>   Racket Users list:
>   http://lists.racket-lang.org/users
>