On 1/17/15 8:32 AM, MattCoder wrote:
> On Saturday, 17 January 2015 at 15:28:57 UTC, Mathias LANG wrote:
>> http://w0rp.com:8010/
>
> I don't know about others but for me the layout above looks more
> attractive than the actual one.

I agree.

> In fact yesterday I was showing the main page for a friend on his
> smartphone (Moto G), and the code example at main page looks awful,
> since it's all wrapped on mobile. Here is an example what I'm talking
> about:
> http://i.imgur.com/9JYNVNk.png

To make a website look good on a mobile device, one needs to do work to make the website look good on a mobile device.


Andrei

On Saturday, 17 January 2015 at 17:59:07 UTC, Andrei Alexandrescu wrote:
>> In fact yesterday I was showing the main page for a friend on his
>> smartphone (Moto G), and the code example at main page looks awful,
>> since it's all wrapped on mobile. Here is an example what I'm talking
>> about:
>> http://i.imgur.com/9JYNVNk.png
>
> To make a website look good on a mobile device, one needs to do work to make the website look good on a mobile device.

Indeed! But, if the "body" had a "width" setted this wouldn't occur.

For example, adding "width: 1024px" on body in style.css it will now be fine to see on mobile.

Matheus.

On 1/17/15 10:39 AM, MattCoder wrote:
> On Saturday, 17 January 2015 at 17:59:07 UTC, Andrei Alexandrescu wrote:
>>> In fact yesterday I was showing the main page for a friend on his
>>> smartphone (Moto G), and the code example at main page looks awful,
>>> since it's all wrapped on mobile. Here is an example what I'm talking
>>> about:
>>> http://i.imgur.com/9JYNVNk.png
>>
>> To make a website look good on a mobile device, one needs to do work
>> to make the website look good on a mobile device.
>
> Indeed! But, if the "body" had a "width" setted this wouldn't occur.
>
> For example, adding "width: 1024px" on body in style.css it will now be
> fine to see on mobile.
>
> Matheus.

A tested PR would be great. Who can take this? -- Andrei

On Saturday, 17 January 2015 at 19:35:01 UTC, Andrei Alexandrescu wrote:
> A tested PR would be great. Who can take this? -- Andrei

A last note about this: using "width:1024px"  will fix the mobile "wrap-text" problem, but the site will look like this on higher resolutions: http://i.imgur.com/MZSmn87.png  (Look the space on the left and right).

So another solution would trying to set "min-width:1024px" on body tag, so the site will continue to be the same as is today even on higher resolutions, and I'm pretty sure this will correct the problem above on mobile devices. If anyone change I'd be glad to test.

PS: I'm assuming 1024 pixels because it's used as minimum standard these days.

Matheus.

On Sat, Jan 17, 2015 at 08:04:56PM +0000, MattCoder via Digitalmars-d wrote:
> On Saturday, 17 January 2015 at 19:35:01 UTC, Andrei Alexandrescu wrote:
> >A tested PR would be great. Who can take this? -- Andrei
> 
> A last note about this: using "width:1024px"  will fix the mobile "wrap-text" problem, but the site will look like this on higher resolutions: http://i.imgur.com/MZSmn87.png  (Look the space on the left and right).
> 
> So another solution would trying to set "min-width:1024px" on body tag, so the site will continue to be the same as is today even on higher resolutions, and I'm pretty sure this will correct the problem above on mobile devices. If anyone change I'd be glad to test.
> 
> PS: I'm assuming 1024 pixels because it's used as minimum standard these days.
[...]

I rather that we use font-based metrics (e.g. 40em) instead of pixel sizes. That way the layout won't break or look horrible if the user changes the default font sizes (e.g. for special needs, etc.) or doesn't maximize his browser window.

But that's just my opinion.

Also, I am skeptical of a single style that will work for both desktop and mobile browsers. Isn't that what mobile stylesheets are for? We can have the same content, but we shouldn't break the desktop layout or make it look laughably spaced out just for the sake of mobile devices. Let the mobile devices have their own stylesheet.


T

-- 
Shin: (n.) A device for finding furniture in the dark.

On 1/17/15 2:24 PM, H. S. Teoh via Digitalmars-d wrote:
> On Sat, Jan 17, 2015 at 08:04:56PM +0000, MattCoder via Digitalmars-d wrote:
>> On Saturday, 17 January 2015 at 19:35:01 UTC, Andrei Alexandrescu wrote:
>>> A tested PR would be great. Who can take this? -- Andrei
>>
>> A last note about this: using "width:1024px"  will fix the mobile
>> "wrap-text" problem, but the site will look like this on higher
>> resolutions: http://i.imgur.com/MZSmn87.png  (Look the space on the
>> left and right).
>>
>> So another solution would trying to set "min-width:1024px" on body
>> tag, so the site will continue to be the same as is today even on
>> higher resolutions, and I'm pretty sure this will correct the problem
>> above on mobile devices. If anyone change I'd be glad to test.
>>
>> PS: I'm assuming 1024 pixels because it's used as minimum standard
>> these days.
> [...]
>
> I rather that we use font-based metrics (e.g. 40em) instead of pixel
> sizes. That way the layout won't break or look horrible if the user
> changes the default font sizes (e.g. for special needs, etc.) or doesn't
> maximize his browser window.
>
> But that's just my opinion.
>
> Also, I am skeptical of a single style that will work for both desktop
> and mobile browsers. Isn't that what mobile stylesheets are for? We can
> have the same content, but we shouldn't break the desktop layout or make
> it look laughably spaced out just for the sake of mobile devices. Let
> the mobile devices have their own stylesheet.

Could you please run some experiments and see where they take us? -- Andrei

On Sat, Jan 17, 2015 at 02:24:48PM -0800, H. S. Teoh via Digitalmars-d wrote:
> Also, I am skeptical of a single style that will work for both desktop and mobile browsers. Isn't that what mobile stylesheets are for?

If you do your html and style right in the first place, it will
be mostly the same. At most you might reposition a sidebar or something.

On Sat, Jan 17, 2015 at 02:36:03PM -0800, Andrei Alexandrescu via Digitalmars-d wrote:
> On 1/17/15 2:24 PM, H. S. Teoh via Digitalmars-d wrote:
[...]
> >I rather that we use font-based metrics (e.g. 40em) instead of pixel sizes. That way the layout won't break or look horrible if the user changes the default font sizes (e.g. for special needs, etc.) or doesn't maximize his browser window.
> >
> >But that's just my opinion.
> >
> >Also, I am skeptical of a single style that will work for both desktop and mobile browsers. Isn't that what mobile stylesheets are for? We can have the same content, but we shouldn't break the desktop layout or make it look laughably spaced out just for the sake of mobile devices. Let the mobile devices have their own stylesheet.
> 
> Could you please run some experiments and see where they take us? -- Andrei

I'm busy working on splitting up std.algorithm into more manageable chunks... currently I can't even run the unittests on my machine anymore because it eats up all available RAM.

So far I've managed to successfully extricate the set operations into their own submodule (and pass unittests!).

So yeah... too busy to look into web stuff atm.


T

-- 
PNP = Plug 'N' Pray

On 1/17/15 3:18 PM, H. S. Teoh via Digitalmars-d wrote:
> On Sat, Jan 17, 2015 at 02:36:03PM -0800, Andrei Alexandrescu via Digitalmars-d wrote:
>> On 1/17/15 2:24 PM, H. S. Teoh via Digitalmars-d wrote:
> [...]
>>> I rather that we use font-based metrics (e.g. 40em) instead of pixel
>>> sizes. That way the layout won't break or look horrible if the user
>>> changes the default font sizes (e.g. for special needs, etc.) or
>>> doesn't maximize his browser window.
>>>
>>> But that's just my opinion.
>>>
>>> Also, I am skeptical of a single style that will work for both
>>> desktop and mobile browsers. Isn't that what mobile stylesheets are
>>> for? We can have the same content, but we shouldn't break the desktop
>>> layout or make it look laughably spaced out just for the sake of
>>> mobile devices. Let the mobile devices have their own stylesheet.
>>
>> Could you please run some experiments and see where they take us? --
>> Andrei
>
> I'm busy working on splitting up std.algorithm into more manageable
> chunks... currently I can't even run the unittests on my machine anymore
> because it eats up all available RAM.
>
> So far I've managed to successfully extricate the set operations into
> their own submodule (and pass unittests!).
>
> So yeah... too busy to look into web stuff atm.

Thanks! I filed https://issues.dlang.org/show_bug.cgi?id=13997, who can get into it? -- Andrei

On Saturday, 17 January 2015 at 22:27:08 UTC, H. S. Teoh via Digitalmars-d wrote:
> Also, I am skeptical of a single style that will work for both desktop
> and mobile browsers. Isn't that what mobile stylesheets are for? We can
> have the same content, but we shouldn't break the desktop layout or make
> it look laughably spaced out just for the sake of mobile devices. Let
> the mobile devices have their own stylesheet.

Sure, but for what I see adding: "min-width:1024px;" (or what unit you want) on body will NOT break the site on desktop and will make the site more readable on mobile.

Ideally you would want a stylesheet for mobile, but this would take more time than adding a single line in the current stylesheet.

Matheus.