Oh, you're right, I forget that because I don't have Visual Studio on my primary web development machine.

I guess that's unfair if the express web edition does have it, but the price of Visual Studio (and relative low usage among web developers of its other features) makes it impractical otherwise imho.

Thanks for reminding me, though.  I should probably go install Visual Studio there... sorry for the mistake.

-[Unknown]


Julio César Carrascal Urquijo wrote:
> Unknown W. Brackets wrote:
>> Using JavaScript debuggers such as WebKit's and Firebug (IE has none afaik.)
> 
> You can debug JavaScript with Visual Studio ("Disable script debuging" in the Advanced tab of Internet Options).
> 
> Nothing compared with Firebug though.
> 
> 

janderson Wrote:

> Walter Bright wrote:
>  > Unknown W. Brackets wrote:
>  >> IMHO, the font size wasn't bad before.  Nice to have a larger one
> with lots to read.  Just my opinion.
>  >>
>  >> Also I suggest a line-height of 1.4em for the content.  This
> generally makes large blocks of text (e.g. documentation, articles, blog
> posts) easier to read.
>  >>
>  >> Walter: if you're reading this, what are things you'd like to see
> the website do?  Aside from possible comments, it's better to get a full
> plan together (usually called the "discovery" phase) before jumping in
> and making a mess.
>  >
>  > I don't know, except that I don't want it to be an ongoing time sink.
> 
> Exactly why this should be handed off to the community.  No offense, but some of the communities web pages look a lot better then D's.
> 
> -Joel
> 
> PS - I apologize for sending this to your personal email, I hit the wrong button.
> 

I have no problem with the idea of an open web design strategy, except someone needs to be in charge of making sure it conforms to what Walter wants it to look like; and make sure nothing bad goes on his site. The "community" is a rather diverse and flexible bunch and it is his site after all.

I'm in the process of making the site look just a little better stylistically.  Walter is a very good devil's advocate, so making changes is quite a bit harder than just changing them and him going "yeah, if you say so".

Now, I'm in the process of committing a bunch of changes to the stylesheet.  If someone has anything else to add to the site, please let myself and/or Walter know.

If you go through me, I'll mediate with Walter's expectations.  : )

Regards,
Dan

Don Clugston wrote:
> What do you think of the Tango site?
> (I'm sure there's some synergy to be found around here).

It looks nice, but some nits (you asked!):

- the text won't flow on resizing the window
- the 3 column theme on the front page doesn't continue to the sub-pages
- I liked the original Tango logo better (the one with the two dancers), I know, you can't please everyone :-)
- the left two characters of the [News] items are cut off after clicking on [Dynamic]

I like the header and footer.

Dan wrote:
> janderson Wrote:
> 
>> Walter Bright wrote:
>>  > Unknown W. Brackets wrote:
>>  >> IMHO, the font size wasn't bad before.  Nice to have a larger one with lots to read.  Just my opinion.
>>  >>
>>  >> Also I suggest a line-height of 1.4em for the content.  This generally makes large blocks of text (e.g. documentation, articles, blog posts) easier to read.
>>  >>
>>  >> Walter: if you're reading this, what are things you'd like to see the website do?  Aside from possible comments, it's better to get a full plan together (usually called the "discovery" phase) before jumping in and making a mess.
>>  >
>>  > I don't know, except that I don't want it to be an ongoing time sink.
>>
>> Exactly why this should be handed off to the community.  No offense, but some of the communities web pages look a lot better then D's.
>>
>> -Joel
>>
>> PS - I apologize for sending this to your personal email, I hit the wrong button.
>>
> 
> I have no problem with the idea of an open web design strategy, except someone needs to be in charge of making sure it conforms to what Walter wants it to look like; and make sure nothing bad goes on his site. The "community" is a rather diverse and flexible bunch and it is his site after all.
> 
> I'm in the process of making the site look just a little better stylistically.  Walter is a very good devil's advocate, so making changes is quite a bit harder than just changing them and him going "yeah, if you say so".
> 
> Now, I'm in the process of committing a bunch of changes to the stylesheet.  If someone has anything else to add to the site, please let myself and/or Walter know.
> 
> If you go through me, I'll mediate with Walter's expectations.  : )
> 
> Regards,
> Dan

In that case, could you do something about the nav bar in every single Phobos documentation page? It's doing strange things: http://ic.sunysb.edu/stu/cbwright/digitalmars_oddity.png

Not to mention the small font.

Christopher Wright wrote:
> In that case, could you do something about the nav bar in every single Phobos documentation page? It's doing strange things: http://ic.sunysb.edu/stu/cbwright/digitalmars_oddity.png

I can't make that happen with Explorer or firefox.

> Not to mention the small font.

Walter Bright wrote:
> Christopher Wright wrote:
>> In that case, could you do something about the nav bar in every single Phobos documentation page? It's doing strange things: http://ic.sunysb.edu/stu/cbwright/digitalmars_oddity.png
> 
> I can't make that happen with Explorer or firefox.

Argh. Damn Debian for forking Firefox. I'll rip it out and use Firefox instead.

What does Help -> About show?  As long as you can give the build number I'd guess it can't be that different from Gecko's regular rendering engine (forked or not.)

-[Unknown]


Christopher Wright wrote:
> Walter Bright wrote:
>> Christopher Wright wrote:
>>> In that case, could you do something about the nav bar in every single Phobos documentation page? It's doing strange things: http://ic.sunysb.edu/stu/cbwright/digitalmars_oddity.png
>>
>> I can't make that happen with Explorer or firefox.
> 
> Argh. Damn Debian for forking Firefox. I'll rip it out and use Firefox instead.

Unknown W. Brackets wrote:
> What does Help -> About show?  As long as you can give the build number I'd guess it can't be that different from Gecko's regular rendering engine (forked or not.)
> 
> -[Unknown]
> 

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20071128 Iceweasel/2.0.0.11 (Debian-2.0.0.11-1)

Yes, that really should be in sync with Firefox 2.0.0.11.  It's using Gecko 1.8.1.11, which is the right tree and version.

Does anything happen if you change your theme (I have no idea if Debian ships winstripe but any other theme just to test is fine.)  Also, I assume you've made no changes to userContent.css or userChrome.css? Does it help to start Firefox in safe mode?

http://www.mozilla.com/en-US/firefox/2.0/releasenotes/#troubleshooting

-[Unknown]


Christopher Wright wrote:
> Unknown W. Brackets wrote:
>> What does Help -> About show?  As long as you can give the build number I'd guess it can't be that different from Gecko's regular rendering engine (forked or not.)
>>
>> -[Unknown]
>>
> 
> Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.11) Gecko/20071128 Iceweasel/2.0.0.11 (Debian-2.0.0.11-1)

Unknown W. Brackets wrote:
> Yes, that really should be in sync with Firefox 2.0.0.11.  It's using Gecko 1.8.1.11, which is the right tree and version.
> 
> Does anything happen if you change your theme (I have no idea if Debian ships winstripe but any other theme just to test is fine.)  Also, I assume you've made no changes to userContent.css or userChrome.css? Does it help to start Firefox in safe mode?
> 
> http://www.mozilla.com/en-US/firefox/2.0/releasenotes/#troubleshooting
> 
> -[Unknown]

Using Firefox 2.0.0.11 gets rid of the problem, using what's supposedly the same build of Gecko. It's an Iceweasel-specific problem; the Debian people fscked it up.

A pity; the Iceweasel icon's cuter. I shall survive.