On Sun, 09 Mar 2014 23:44:43 -0400, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:

> Consider it alpha quality. Please don't announce yet before we put it in good shape.
>

I LOVE this. Been waiting for it for a long time. The cross-links themselves are worth the wait.

Just look at how organized std.datetime has become!

Now, one nitpick -- I would like to see leaf links expand locally instead of opening a new page. Perhaps you can click on the link, and it opens a new page, but have a + button to expand in-line if desired. Essentially, the disruption of going to a new page when looking at the details of a function, I feel is too much.

And look at that, disqus comments!

-Steve

On Monday, 10 March 2014 at 03:44:54 UTC, Andrei Alexandrescu wrote:
> Consider it alpha quality. Please don't announce yet before we put it in good shape.
>
> https://github.com/D-Programming-Language/dlang.org/pull/516
>
> http://dlang.org/library
>
> http://dlang.org/library-prerelease
>
> I needed to change quite a bit about the makefile. It was building everything over and over again, and it's _slow_.
>
> Some functions are not ready, compare e.g.
>
> http://dlang.org/library/std/algorithm/balancedParens.html
>
> with
>
> http://dlang.org/library/std/algorithm/any.html
>
>
> Andrei

I still don't like disqus :)

Documentation in general may probably benefit from some styling tweaks - for example, std.alogrithm looks funny when manually crafted tables turn into usual generated function list. But overall look solid.

Thank you, to everone who worked on this.  It's quite an improvement.

Problem:
http://dlang.org/library/std/compiler/vendor.html is a 404

Recommendation:
I really liked the immediate link to the source file on github in the old layout.  If possible please add it to the new layout.

Mike

On Monday, 10 March 2014 at 14:08:07 UTC, Mike wrote:
> Thank you, to everone who worked on this.  It's quite an improvement.
>
> Problem:
> http://dlang.org/library/std/compiler/vendor.html is a 404
>
> Recommendation:
> I really liked the immediate link to the source file on github in the old layout.  If possible please add it to the new layout.

Since (IIRC) DDox parses JSON layout, I think it is capable of generating exact links to the file:line of each symbol. That would be neat, as it allows quickly seeing the implementation if the documentation is not sufficient.

On 3/10/14, 1:35 AM, Nicolas Sicard wrote:
> For me it's a real improvement! One thing: symbol names (modules,
> functions, etc.) shouldn't be hyphenated, specially in tables.

All: how does one turn off css hyphenation?

Andrei

On 3/10/14, 7:00 AM, Dicebot wrote:
> I still don't like disqus :)

Are there better such systems available?

> Documentation in general may probably benefit from some styling tweaks -
> for example, std.alogrithm looks funny when manually crafted tables turn
> into usual generated function list. But overall look solid.

Yah, we need a solid community effort on this all. Please file issues appropriately, and hopefully fix others directly.

Folks, this is the long tail. Please help us improve our documentation.


Andrei

On Monday, 10 March 2014 at 14:56:13 UTC, Andrei Alexandrescu wrote:
> On 3/10/14, 1:35 AM, Nicolas Sicard wrote:
>> For me it's a real improvement! One thing: symbol names (modules,
>> functions, etc.) shouldn't be hyphenated, specially in tables.
>
> All: how does one turn off css hyphenation?
>
> Andrei

word-wrap: break-word;
-webkit-hypens: none;
-moz-hypens: none;
-ms-hypens: none;
hypens: none;


should do the trick..

On Monday, 10 March 2014 at 14:56:13 UTC, Andrei Alexandrescu wrote:
> On 3/10/14, 1:35 AM, Nicolas Sicard wrote:
>> For me it's a real improvement! One thing: symbol names (modules,
>> functions, etc.) shouldn't be hyphenated, specially in tables.
>
> All: how does one turn off css hyphenation?
>
> Andrei

class="donthyphenate"

On Monday, 10 March 2014 at 14:11:06 UTC, Vladimir Panteleev wrote:
> On Monday, 10 March 2014 at 14:08:07 UTC, Mike wrote:
>> Thank you, to everone who worked on this.  It's quite an improvement.
>>
>> Problem:
>> http://dlang.org/library/std/compiler/vendor.html is a 404
>>
>> Recommendation:
>> I really liked the immediate link to the source file on github in the old layout.  If possible please add it to the new layout.
>
> Since (IIRC) DDox parses JSON layout, I think it is capable of generating exact links to the file:line of each symbol. That would be neat, as it allows quickly seeing the implementation if the documentation is not sufficient.

I wanted to do just this so I considered adding a predefined macro to ddoc to get line numbers like I did to get filenames (I needed SRCFILENAME to add the Improve This Page button) but the line numbers would pretty quickly lose sync between master and the documentation so that would also require integrating the release tag into the documentation somehow so I gave up on that idea.

On Monday, 10 March 2014 at 16:54:37 UTC, Brad Anderson wrote:
> On Monday, 10 March 2014 at 14:11:06 UTC, Vladimir Panteleev wrote:
>> On Monday, 10 March 2014 at 14:08:07 UTC, Mike wrote:
>>> Thank you, to everone who worked on this.  It's quite an improvement.
>>>
>>> Problem:
>>> http://dlang.org/library/std/compiler/vendor.html is a 404
>>>
>>> Recommendation:
>>> I really liked the immediate link to the source file on github in the old layout.  If possible please add it to the new layout.
>>
>> Since (IIRC) DDox parses JSON layout, I think it is capable of generating exact links to the file:line of each symbol. That would be neat, as it allows quickly seeing the implementation if the documentation is not sufficient.
>
> I wanted to do just this so I considered adding a predefined macro to ddoc to get line numbers like I did to get filenames (I needed SRCFILENAME to add the Improve This Page button) but the line numbers would pretty quickly lose sync between master and the documentation so that would also require integrating the release tag into the documentation somehow so I gave up on that idea.

So... don't link to master?

The dmd repo has a VERSION file. Can that be used to link to the respective tag instead?