On 09/07/2014 4:43 PM, Chris wrote:
> This sounds just like Imperial education. Very interesting how it
> equates Imperial practices with the "right" thing and the (continental)
> arch enemy with the "wrong" thing. By the way, there was a reason why
> combatant riders would ride on the right side on a tilting yard: they
> were right-handed. Just as it makes more sense to switch gears with the
> right hand and not with the (in most cases) weaker left hand.


Sorry, the correct side/wrong side designations was all me, I have trouble with light and reft, and didn't want to get mixed up with the 2 meanings of right. Perhaps its an artefact of my imperial education ^^

Also some argue that it makes more sense in a modern car to change gear with the left hand and keep the stronger arm on the steering wheel. Early right-hand-drive cars either had all foot operated gears, or they were on the outside (actually outside the cockpit) rather than in the middle because they needed real effort, modern gears especially automatics don't need that effort any more.

A...

On Wednesday, 9 July 2014 at 21:20:28 UTC, Alix Pexton wrote:
> On 09/07/2014 4:43 PM, Chris wrote:
>> This sounds just like Imperial education. Very interesting how it
>> equates Imperial practices with the "right" thing and the (continental)
>> arch enemy with the "wrong" thing. By the way, there was a reason why
>> combatant riders would ride on the right side on a tilting yard: they
>> were right-handed. Just as it makes more sense to switch gears with the
>> right hand and not with the (in most cases) weaker left hand.
>
>
> Sorry, the correct side/wrong side designations was all me, I have trouble with light and reft, and didn't want to get mixed up with the 2 meanings of right. Perhaps its an artefact of my imperial education ^^

I see. Your account of what you learned is interesting nevertheless, because it implies that the Empire kept the ancient system, whereas now a new "corrupt" system is used in the rest of the world, a system that has its roots in the "insidious" tactics of a Frenchman called Napoleon.

> Also some argue that it makes more sense in a modern car to change gear with the left hand and keep the stronger arm on the steering wheel. Early right-hand-drive cars either had all foot operated gears, or they were on the outside (actually outside the cockpit) rather than in the middle because they needed real effort, modern gears especially automatics don't need that effort any more.
>
> A...

I don't agree. A lot of cars still use manual gears, not automatics. I also find that in dangerous situations it is better that the stronger arm has more room for action in the cockpit and is not impeded by the window / door. Also, pressing buttons on the radio / audio player, air conditioning etc. is much easier (=precise) with the stronger arm, especially while driving when these actions cannot get your undivided attention. This is at least my experience, but many people have agreed with me on this.

http://w0rp.com:8010/library/index.html

I just updated the site hosted there with the work I've done on integrating the library documentation to date. I spent a lot of time staring at the pages for a while trying to figure out how to fit everything on a page decent. I admit to hacking the std.algoritm tables into not being tables, etc. I would very much appreciate any pull requests which improve on what I've done so far with it. It's all on GitHub in the usual place.

https://github.com/w0rp/new-dlang.org

Right now I'm using some of the layouts modified from Sönke's ddox templates, some modified from the dlang.org stuff. I'm using Adam D. Ruppe's DOM library, etc. I would like to properly attribute everyone for everything, so I would really appreciate input on where to credit people if I missed anything out. I have a COPYRIGHT file I can add people to if needed for that purpose, and I have retained the copyright comments in the arsd library.

I still haven't included syntax highlighting. This really isn't hard, I just haven't gotten around to doing it yet.

There's still a lot of work to be done, but it's one step closer now.

..and fixed width docs again. Unfortunately I am not competent enough to propose any change so user CSS it stays for me :(

All pages seem to miss all examples - simply not implemented yet or oversight?

On Sunday, 27 July 2014 at 00:38:14 UTC, Dicebot wrote:
> All pages seem to miss all examples - simply not implemented yet or oversight?

ah, nevermind:

> I still haven't included syntax highlighting. This really isn't
> hard, I just haven't gotten around to doing it yet.

On Sat, Jul 26, 2014 at 07:39:50PM -0700, Andrei Alexandrescu via Digitalmars-d wrote:
> On 7/26/14, 6:30 PM, w0rp wrote:
> >The std.algortihm documentation doesn't look good, and I don't have any good ideas for it.
> 
> I find std.algorithm among the best documented libraries out there! I must be in denial... -- Andrei

"No, I'm not in denial! It can't be!!!"


:-P

-- 
Живёшь только однажды.

On 7/26/14, 8:47 PM, H. S. Teoh via Digitalmars-d wrote:
> On Sat, Jul 26, 2014 at 07:39:50PM -0700, Andrei Alexandrescu via Digitalmars-d wrote:
>> On 7/26/14, 6:30 PM, w0rp wrote:
>>> The std.algortihm documentation doesn't look good, and I don't have
>>> any good ideas for it.
>>
>> I find std.algorithm among the best documented libraries out there! I
>> must be in denial... -- Andrei
>
> "No, I'm not in denial! It can't be!!!"

Well correction: I think it's among the better documented modules in std. -- Andrei

On Sunday, 27 July 2014 at 06:10:09 UTC, Andrei Alexandrescu wrote:
> On 7/26/14, 8:47 PM, H. S. Teoh via Digitalmars-d wrote:
>> On Sat, Jul 26, 2014 at 07:39:50PM -0700, Andrei Alexandrescu via Digitalmars-d wrote:
>>> On 7/26/14, 6:30 PM, w0rp wrote:
>>>> The std.algortihm documentation doesn't look good, and I don't have
>>>> any good ideas for it.
>>>
>>> I find std.algorithm among the best documented libraries out there! I
>>> must be in denial... -- Andrei
>>
>> "No, I'm not in denial! It can't be!!!"
>
> Well correction: I think it's among the better documented modules in std. -- Andrei

It's not the text, it's just the current formatting. The cheat sheet can't fit into a smaller column size as a table. So you can break that down into smaller headings and paragraphs instead so it will reflow, but then the length of the page gets bumped up quite a bit and makes it harder to find things at a glance.

Because it's probably the most important library in all of Phobos, it's probably worth excluding the usual output of lists of Functions, Structs, etc. from std.algortihm and letting the cheat sheet itself be the list of symbols, which is organised a lot better than a sort by symbol type then name will ever be. I like the "these are for iteration" kind of categorisation. I'd probably then remove the table right at the top, so you have the module description and example above the fold.

That's what I'm thinking at the moment anyway.

On Sunday, 27 July 2014 at 13:30:18 UTC, w0rp wrote:
> It's not the text, it's just the current formatting. The cheat sheet can't fit into a smaller column size as a table. So you can break that down into smaller headings and paragraphs instead so it will reflow, but then the length of the page gets bumped up quite a bit and makes it harder to find things at a glance.
>
> Because it's probably the most important library in all of Phobos, it's probably worth excluding the usual output of lists of Functions, Structs, etc. from std.algortihm and letting the cheat sheet itself be the list of symbols, which is organised a lot better than a sort by symbol type then name will ever be. I like the "these are for iteration" kind of categorisation. I'd probably then remove the table right at the top, so you have the module description and example above the fold.
>
> That's what I'm thinking at the moment anyway.

This is completely the wrong way to design anything. The design needs rework if it can't handle the content. You don't shorten the content to fit your design!

Also the main content area is far too narrow. The current design look ridiculous on a large monitor.

Desktop: http://imgur.com/Xr25TJ8

and because the design is fixed and not responsive in *any* way it also looks dire on mobile devices.

iPhone: http://imgur.com/fHduaH7

This is a poor amateurish design and i wish you would stop right now. If this ever goes live not only will all developers be extremely frustrated trying to actually read the documentation but we as a community are going to be laughing stock of the programming world!

This needs the attention of a professional designer and web developer.

Am 27.07.2014 00:54, schrieb w0rp:
> http://w0rp.com:8010/library/index.html
>

Since the site is running with vibe.d anyway, I'd think about using registerApiDocs() instead of generating individual HTML files. This gives much nicer URLs and also avoids potential issues with file systems that are case insensitive. See http://vibed.org/api/ for an example.