On 1/18/15 6:46 PM, Mike wrote:
> On Monday, 19 January 2015 at 02:36:35 UTC, Andrei Alexandrescu wrote:
>
>>>> My only real complaint about the ddoc site is that the build process
>>>> is pure evil.
>>>
>>> I can second that. I haven't tried in the past week, but I've been
>>> unable to build the site, stopping the doc pulls I wanted to make in
>>> their tracks.
>>
>> Destroy!!! What's not working? -- Andrei
>
> For starters, simple, accurate instructions in dlang.org's Readme.md file.
>
> Mike

"There's a bug report for that." https://issues.dlang.org/show_bug.cgi?id=14006

Andrei

On 1/18/15 11:18 PM, Andrei Alexandrescu wrote:
> TL;DR: I've uploaded new menu colors at http://erdani.com/d/, this time
> aiming for a more martian red ethos. Please let me know.
>
> ==================
>
> So I was looking at the css today (original at
> http://paste.ofcode.org/fHGT24YASrWu3rnMYLdm4C taken from the zip at
> http://cssmenumaker.com/menu/modern-jquery-accordion-menu) and it was
> quite unwieldy to experiment with. For example, the same color appears
> hardcoded in a number of places; whenever changing one I'd need to
> change all, or miss some important instances (as it happened with my
> first experiment).
>
> I'm sure experts must have tools for allowing things like variables and
> macros for css creation.

Sass (http://sass-lang.com/) and Less (http://lesscss.org/) comes to my mind. Any decent web framework comes with support for them.

I think you will eventually find that ddoc is turing-complete and will implement one of the above transpilers in it.

And css minification isn't just about gzip. It's also about removing whitespace and compacting stuff. Can you code a ddoc macro for that?

On 1/18/15 7:12 PM, Ary Borenszweig wrote:
> On 1/18/15 11:18 PM, Andrei Alexandrescu wrote:
>> TL;DR: I've uploaded new menu colors at http://erdani.com/d/, this time
>> aiming for a more martian red ethos. Please let me know.
>>
>> ==================
>>
>> So I was looking at the css today (original at
>> http://paste.ofcode.org/fHGT24YASrWu3rnMYLdm4C taken from the zip at
>> http://cssmenumaker.com/menu/modern-jquery-accordion-menu) and it was
>> quite unwieldy to experiment with. For example, the same color appears
>> hardcoded in a number of places; whenever changing one I'd need to
>> change all, or miss some important instances (as it happened with my
>> first experiment).
>>
>> I'm sure experts must have tools for allowing things like variables and
>> macros for css creation.
>
> Sass (http://sass-lang.com/) and Less (http://lesscss.org/) comes to my
> mind. Any decent web framework comes with support for them.

Yah. The ones I found were paid. My point is ddoc was there and fit the job perfectly well.

> I think you will eventually find that ddoc is turing-complete and will
> implement one of the above transpilers in it.

It's not, but irony gotten :o).

> And css minification isn't just about gzip. It's also about removing
> whitespace and compacting stuff. Can you code a ddoc macro for that?

This is a confusion - css minification is a separate topic altogether; I got to it as a drive-by optimization and many people here thought I need to spend the next quarter on traffic improvements.

To answer: it is not possible to do that with ddoc macros.


Andrei

On Monday, 19 January 2015 at 03:01:44 UTC, Andrei Alexandrescu wrote:
> No personal aspect to this. What hex colors did you use? --

background-color: #6E6E6E;

And I cleaned:

#cssmenu > ul > li > a {
    font-size: 14px;
    display: block;
    background: url("http://erdani.com/d/images/xpattern.png.pagespeed.ic.QEXJsY5pYW.png") repeat scroll left top transparent;
    border-right: 1px solid #893A28;
    border-width: medium 1px 1px;
    border-style: none solid solid;
    border-color: -moz-use-text-color #893A28 #893A28;
    -moz-border-top-colors: none;
    -moz-border-right-colors: none;
    -moz-border-bottom-colors: none;
    -moz-border-left-colors: none;
    border-image: none;
    color: #FFF;
    text-shadow: 0px -1px 1px #751D0C;
}

to

#cssmenu > ul > li > a {
    font-size: 14px;
    display: block;
    color: #FFF;
    text-shadow: 0px -1px 1px #751D0C;
}

Matheus.

On Monday, 19 January 2015 at 02:18:32 UTC, Andrei Alexandrescu wrote:
> TL;DR: I've uploaded new menu colors at http://erdani.com/d/, this time aiming for a more martian red ethos. Please let me know.
>
> ==================
>
> So I was looking at the css today (original at http://paste.ofcode.org/fHGT24YASrWu3rnMYLdm4C taken from the zip at http://cssmenumaker.com/menu/modern-jquery-accordion-menu) and it was quite unwieldy to experiment with. For example, the same color appears hardcoded in a number of places; whenever changing one I'd need to change all, or miss some important instances (as it happened with my first experiment).
>
> I'm sure experts must have tools for allowing things like variables and macros for css creation. Indeed there are a number of CSS editors that features things like variables, substitutions, and code generations, but most come at a cost and require quite some involvement.
>
> So I slapped something much simpler together using... ddoc.
>
> 1. I aded this at the top of the original file:
>
> Ddoc
>
> and then this at the bottom:
>
> Macros:
>
> DDOC=$(BODY)
> DDOC_COMMENT=/*$0*/
> ESCAPES=/</</ />/>/ /&/&/
>
> then saved the file as cssmenu.css.dd. Now I suddenly had a file compilable with ddoc, which produced itself (sans the heading and the macros). Here's the cmdline:
>
> dmd -c -o- -Dfweb/css/cssmenu.css css/cssmenu.css.dd
>
> It's a bit of a bummer that I need to define three unintuitive macros to get idempotent generation, but I guess that's that. We should document that somewhere.
>
> 2. Now the fun begins. Now with macros I could define things like variables and even functions, and change all by changing one. Cool! So I started looking for all colors in the document and converted them to macros.
>
> After a short time I had http://paste.ofcode.org/3agBQ3t6C3UJsqMfRe4GeQL working. With that in hand, it was trivially easy to test different colors and see how they impact the look.
>
> The result is as I mentioned at http://erdani.com/d. I trust you'll hate the colors but maybe not the hack.
>
> So, may I add a pull request of this without anyone having an apoplexy attack? When we pass the site for styling we can pass the generated css.
>
>
> Andrei


Red colour is hard to work with generally. It takes too much attention. It goes well with white and grey colours. Though, here is some colours for you to try:

https://color.adobe.com/create/color-wheel/?base=2&rule=Custom&selected=4&name=My%20Color%20Theme&mode=rgb&rgbvalues=0.7,0.22200669464295397,0.1097099201844362,0.6268360119554587,1,0.5314703422197685,0.125290070947203,1,0.4581047763190884,0.13626074345941347,0.4015373174033305,0.8,0.3049403467128378,0.4400712229615978,0.7&swatchOrder=0,1,2,3,4


I know it is hard to accept change though, for more professional look, many changes would require on the site.

This is an example for Phobos documentation:
http://php.net/manual/en/function.shm-attach.php


We could use Open Sans font as well maybe from Google Fonts.


I mostly write CSS, JS, HTML by hand instead of using frameworks. So, I am sorry if the tools in the hand are not giving enough flexibility.

On Monday, 19 January 2015 at 03:02:37 UTC, Andrei Alexandrescu wrote:

>>> Destroy!!! What's not working? -- Andrei
>>
>> For starters, simple, accurate instructions in dlang.org's Readme.md file.
>>
>> Mike
>
> "There's a bug report for that." https://issues.dlang.org/show_bug.cgi?id=14006

That's a separate issue.  I'm referring to problems like this:
https://issues.dlang.org/show_bug.cgi?id=13436

The instructions are absent in readme.md and wrong or broken in contributing.md.

So, you might be wondering, why don't I fix it.  Answer, because I don't know what it should be.  This should be fixed by someone who already knows the build process, so others who don't know have a something working to start with, and can eventually inherit the maintenance and knowledge so they, themselves, can pass it on to others.

Mike

On 1/18/15 7:28 PM, Mike wrote:
> On Monday, 19 January 2015 at 03:02:37 UTC, Andrei Alexandrescu wrote:
>
>>>> Destroy!!! What's not working? -- Andrei
>>>
>>> For starters, simple, accurate instructions in dlang.org's Readme.md
>>> file.
>>>
>>> Mike
>>
>> "There's a bug report for that."
>> https://issues.dlang.org/show_bug.cgi?id=14006
>
> That's a separate issue.  I'm referring to problems like this:
> https://issues.dlang.org/show_bug.cgi?id=13436
>
> The instructions are absent in readme.md and wrong or broken in
> contributing.md.
>
> So, you might be wondering, why don't I fix it.  Answer, because I don't
> know what it should be.  This should be fixed by someone who already
> knows the build process, so others who don't know have a something
> working to start with, and can eventually inherit the maintenance and
> knowledge so they, themselves, can pass it on to others.

Agreed. If there's anything to add, add to 13436. -- Andrei

On 01/18/2015 06:18 PM, Andrei Alexandrescu wrote:

A general plea about ddoc: Please don't change its behavior; a whole book depends on how it behaves. :)

There were silent changes in the past, which made me find workarounds and change the way I use ddoc.

Ali

On 2015-01-19 04:17, Andrei Alexandrescu wrote:

> Yah. The ones I found were paid. My point is ddoc was there and fit the
> job perfectly well.

libsass [1] is a C implementation of Sass. Original implementation of Sass is in Ruby.

> This is a confusion - css minification is a separate topic altogether; I
> got to it as a drive-by optimization and many people here thought I need
> to spend the next quarter on traffic improvements.
>
> To answer: it is not possible to do that with ddoc macros.

Sass already does that.

[1] http://libsass.org

-- 
/Jacob Carlborg

On 2015-01-19 03:18, Andrei Alexandrescu wrote:
> TL;DR: I've uploaded new menu colors at http://erdani.com/d/, this time
> aiming for a more martian red ethos. Please let me know.

I still like the original menu better.

-- 
/Jacob Carlborg