July 19, 2016
On Tuesday, 19 July 2016 at 01:38:54 UTC, Andrei Alexandrescu wrote:
>> ...
>>
>> http://i.imgur.com/UTLpK42.png
>>
>> PS: Click to see the full image.
>
> I like the styling on the right - the vertical spacing between paragraph is ridiculous in the left version, and the "Jump to:" box is too tall. -- Andrei

This is why I don't go through this and help on this matter, I mean the layout is too subjective, I think the left version (Which was changed by my friend) is much better to read than the version on the right.

Another thing: using "font-weight" or "bold" sometimes looks weird on high resolutions, which was avoided on the left, maybe is not too visible here but anyway...

And finally: Keep in mind that some folks (like myself) use Tablet to read manuals, and the font size matters a lot on tiny screens.

By the way, this is not a rant, :) I'm just saying that making layout for others is something that I don't like because the different tastes.

Mattcoder.
July 19, 2016
On Tuesday, 19 July 2016 at 01:37:20 UTC, Andrei Alexandrescu wrote:
> On 07/18/2016 06:13 PM, bitwise wrote:
>> Any chance of getting one definition or overload-set per page?
>
> Been like that for a while, my comments refer to the old styling. -- Andrei

Why talk about the old style though? I don't see any of the problems you've mentioned in the new beta docs

http://dlang.org/library/std/algorithm/searching/balanced_parens.html

    Bit

July 19, 2016
On 7/19/16 12:39 PM, bitwise wrote:
> On Tuesday, 19 July 2016 at 01:37:20 UTC, Andrei Alexandrescu wrote:
>> On 07/18/2016 06:13 PM, bitwise wrote:
>>> Any chance of getting one definition or overload-set per page?
>>
>> Been like that for a while, my comments refer to the old styling. --
>> Andrei
>
> Why talk about the old style though? I don't see any of the problems
> you've mentioned in the new beta docs
>
> http://dlang.org/library/std/algorithm/searching/balanced_parens.html
>
>     Bit

The two coexist. -- Andrei

July 19, 2016
On Tuesday, 19 July 2016 at 17:02:34 UTC, Andrei Alexandrescu wrote:
> On 7/19/16 12:39 PM, bitwise wrote:
>> On Tuesday, 19 July 2016 at 01:37:20 UTC, Andrei Alexandrescu wrote:
>>> On 07/18/2016 06:13 PM, bitwise wrote:
>>>> Any chance of getting one definition or overload-set per page?
>>>
>>> Been like that for a while, my comments refer to the old styling. --
>>> Andrei
>>
>> Why talk about the old style though? I don't see any of the problems
>> you've mentioned in the new beta docs
>>
>> http://dlang.org/library/std/algorithm/searching/balanced_parens.html
>>
>>     Bit
>
> The two coexist. -- Andrei

Ok, I was under the impression the old ones would eventually be removed.

Thanks,
    Bit

July 19, 2016
On Monday, 18 July 2016 at 15:56:29 UTC, Andrei Alexandrescu wrote:
>
> * My pet dream was to work on a project with a beautiful justified and hyphenated website. After endless debates, ugliness has won - I'm looking at a eye-scratching ragged right edge.

I just want to point out that Firefox will sporadically justify incredibly poorly, leaving huge spaces between words (In one extreme case, I caught it making something like 3cm gaps).  It looks really bad, and isn't actually easier to read when the line length is long.

-Wyatt
July 21, 2016
I think the Python docs looks better and are more useful...but the older Python docs were even better.  Sometimes fancier HTML just makes things less useful.

That said, I think that when feasible docs should be auto-generated from code included within the code files.  More like ddoc or javadoc then Sphinx or such.  But this shouldn't necessarily apply to the basic frameworks.  The basic D documentation is extremely good, it's when we get to the libraries that things become a bit iffy.  (Then again, I don't like the template syntax.  I thought the D1 docs were better than the D2 docs, but this might be because when they were rewritten they assumed things that give me trouble.  I prefer the way that Python handles ranges to the way the D does. Etc.  These impact the understanding of the documentation of many Phobos files.)


On 07/18/2016 06:41 PM, Andrei Alexandrescu via Digitalmars-d wrote:
> On 07/18/2016 09:28 PM, Carl Vogel wrote:
>> Racket's docs have actually been designed by a professional typographer,
>> so might be a good reference point. Example:
>> https://docs.racket-lang.org/reference/flonums.html
>
> They do look nice! -- Andrei
>

July 21, 2016
I like this kind of discussion. It's good to make the website look as attractive and functional as we can make it. I think we just need to remember to file each issue individually, then group all of the issues to track all of them. Then each individual issue can be tackled, and some work can get done while the rest of the issues are discussed.

Maybe I'm just speaking common sense or something, but I think it's worth mentioning.
July 26, 2016
** RANT ON **

A perfect example for an item for your action list.
And it pretty much looks like the syntax the wiki is using already.

I bet you a drink at next years DConf that it will take you at least 10 minutes to find and reread this thread next time you create a vision document just to rewrite parts of it for you next vision document.

** RANT OFF **

1 2 3
Next ›   Last »