On 08/12/2013 05:33 PM, Corey Richardson wrote:
Hello all,
I present to you: rustdoc_ng http://seld.be/rustdoc/master/index.html
It's basically done, only a few minor bugs remain, as well as the
listing of `pub use`'s. I've been using it as my only doc browser the
past day and it's quite
This looks really great. Some random feedback from a skim.
I love that there are cross-references within the code snippets. It's
great to be able to quickly look up what a trait means. I noticed that
prelude in the discussion on
http://seld.be/rustdoc/master/std/index.html isn't
a link, is
On Mon, Aug 12, 2013 at 12:15 PM, Evan Martin mart...@danga.com wrote:
I love that there are cross-references within the code snippets. It's great
to be able to quickly look up what a trait means. I noticed that prelude
in the discussion on http://seld.be/rustdoc/master/std/index.html isn't a
Hello Corey,
Thanks for your work on this. The live search is especially welcome.
The relative weights of fonts on the page don't correspond to their
importance. That is, the TUTORIAL | MANUAL bit is the largest, boldest,
most whitespaced piece of the page but they're only links you're
On 08/12/2013 12:15 PM, Evan Martin wrote:
You could make the links to source more stable by linking to exactly the
version of the source that the docs were built from.
E.g. rather than having
http://seld.be/rustdoc/master/std/either/fn.lefts.html
link to
This is awesome! If you're taking suggestions, it seems like one case
can be improved. If you just heard about this TreeMap thing, you'd go
to the dox, search for treemap (awesome live update btw), hit the
first link, and then get bombarded with a *lot* of type signatures.
If all you wanted to
On Mon, Aug 12, 2013 at 11:33 AM, Corey Richardson co...@octayn.net wrote:
Hello all,
I present to you: rustdoc_ng http://seld.be/rustdoc/master/index.html
It's basically done, only a few minor bugs remain, as well as the
listing of `pub use`'s. I've been using it as my only doc browser the
Hi,
On 12/08/2013 16:33, Corey Richardson wrote:
Super thanks to Jed Estep and Huon Wilson, who helped a lot with the
backend. And, of course, this would have taken 3x longer and the
result would have been half as good if it were not for Jordi Boggiano
and his amazing work with the web
On 8/13/13 4:15 AM, Evan Martin wrote:
This is vague, I feel like there's too many clicks to get into the
details of something. E.g. if I'm trying to see what the std module
offers, the overview page just lists modules without any description.
if I click into ascii, I see a list of functions
On 12.08.2013 20:10, Armin Ronacher wrote:
Hi,
On 12/08/2013 16:33, Corey Richardson wrote:
Super thanks to Jed Estep and Huon Wilson, who helped a lot with the
backend. And, of course, this would have taken 3x longer and the
result would have been half as good if it were not for Jordi
On 12.08.2013 19:39, Daniel Micay wrote:
A nitpick is that the markdown isn't being rendered correctly, at
least not how it would be with an up-to-date pandoc.
Can you give specifics? It's using the npm marked package right now with
GFM (github flavoured markdown) enabled. As far as I could see
On 12.08.2013 19:27, Alex Crichton wrote:
This is awesome! If you're taking suggestions, it seems like one case
can be improved. If you just heard about this TreeMap thing, you'd go
to the dox, search for treemap (awesome live update btw), hit the
first link, and then get bombarded with a
Hi,
On 12/08/2013 20:35, Jordi Boggiano wrote:
Not in full with definitions and docs etc. like the current docs do. I
find this particularly messy when there is more than one liner docs
(which I hope we have one day;). It wouldn't be impossible to add
obviously, but I'd rather focus on one use
On 12.08.2013 20:19, Patrick Walton wrote:
On 8/13/13 4:15 AM, Evan Martin wrote:
This is vague, I feel like there's too many clicks to get into the
details of something. E.g. if I'm trying to see what the std module
offers, the overview page just lists modules without any description.
if
On Mon, Aug 12, 2013 at 3:36 PM, Jordi Boggiano j.boggi...@seld.be wrote:
On 12.08.2013 19:39, Daniel Micay wrote:
A nitpick is that the markdown isn't being rendered correctly, at
least not how it would be with an up-to-date pandoc.
Can you give specifics? It's using the npm marked package
I noticed it because the code samples weren't syntax highlighted but
there are some other quirks with lists/headers. Rust's documentation
doesn't stick to the very small part of the language that's common
across most implementations. It would mean no nested lists, tables,
code snippets,
Searching for std::hashmap::HashMap, I typed Hash. When the ideal
results didn't show up, I added an 'M' to make my query HashM at this
point, I'm told nothing is found and that I should try DDG. However, if
I continue to type 'ap' to make my query HashMap, I get proper
results. This seems
On 12.08.2013 22:47, Jeaye wrote:
Searching for std::hashmap::HashMap, I typed Hash. When the ideal
results didn't show up, I added an 'M' to make my query HashM at this
point, I'm told nothing is found and that I should try DDG. However, if
I continue to type 'ap' to make my query HashMap, I
On Mon, Aug 12, 2013 at 4:41 PM, Jordi Boggiano j.boggi...@seld.be wrote:
I noticed it because the code samples weren't syntax highlighted but
there are some other quirks with lists/headers. Rust's documentation
doesn't stick to the very small part of the language that's common
across most
19 matches
Mail list logo
