The web site has changed; it now uses style sheets for layout rather than tables and embedded formatting. I essentially learned how to do this from the many examples posted here of possible new layouts for the documentation pages. Thanks to all!

I don't think the style sheet currently used is as good as the ones you came up with - at this point I was just interested in getting the layout into the style sheet. Now, we can just work on improving the style sheet.

http://www.digitalmars.com/d/changelog.html

Walter Bright wrote:

> The web site has changed; it now uses style sheets for layout rather than tables and embedded formatting. I essentially learned how to do this from the many examples posted here of possible new layouts for the documentation pages. Thanks to all!
> 
> I don't think the style sheet currently used is as good as the ones you came up with - at this point I was just interested in getting the layout into the style sheet. Now, we can just work on improving the style sheet.
> 
> http://www.digitalmars.com/d/changelog.html

First reports say that the left border menu is totally broken in Firefox, Opera and Konqueror.

-- 
Lars Ivar Igesund
blog at http://larsivi.net
DSource & #D: larsivi

Walter Bright wrote:
> The web site has changed; it now uses style sheets for layout rather than tables and embedded formatting. I essentially learned how to do this from the many examples posted here of possible new layouts for the documentation pages. Thanks to all!
> 
> I don't think the style sheet currently used is as good as the ones you came up with - at this point I was just interested in getting the layout into the style sheet. Now, we can just work on improving the style sheet.
> 
> http://www.digitalmars.com/d/changelog.html

It's horrifically broken in at least Firefox, Konqueror (and therefore probably Safari), and Opera.  Basically every browser with any shred of standards compliance.

Don't webdev on IE.  It is not a browser.

 - Gregor Richards

Lars Ivar Igesund wrote:
> Walter Bright wrote:
> 
> 
>>The web site has changed; it now uses style sheets for layout rather
>>than tables and embedded formatting. I essentially learned how to do
>>this from the many examples posted here of possible new layouts for the
>>documentation pages. Thanks to all!
>>
>>I don't think the style sheet currently used is as good as the ones you
>>came up with - at this point I was just interested in getting the layout
>>into the style sheet. Now, we can just work on improving the style sheet.
>>
>>http://www.digitalmars.com/d/changelog.html
> 
> 
> First reports say that the left border menu is totally broken in Firefox,
> Opera and Konqueror.
> 

It is indeed broken in Firefox. Messing with the CSS (with the wonderful Edit CSS plugin for Firefox), dropping "height : 0;" anywhere it appears seems to fix it, at least for Firefox.

-Kirk McDonald

Walter Bright wrote:
> The web site has changed; it now uses style sheets for layout rather than tables and embedded formatting. I essentially learned how to do this from the many examples posted here of possible new layouts for the documentation pages. Thanks to all!
> 
> I don't think the style sheet currently used is as good as the ones you came up with - at this point I was just interested in getting the layout into the style sheet. Now, we can just work on improving the style sheet.
> 
> http://www.digitalmars.com/d/changelog.html

From the changelog:
    Added operator overloading of InExpression.

How does this work? Is it backwards from the other operators? In other words, does

    a in b

get translated to

    b.opIn(a)

? Because that is certainly more useful than the usual behavior, but the documentation doesn't say. (At the least, it should mention this.)

-Kirk McDonald

In article <e5vbqo$284t$1@digitaldaemon.com>, Lars Ivar Igesund says...
>
>First reports say that the left border menu is totally broken in Firefox, Opera and Konqueror.
>

I second this.  The main website is unusable for the moment.

-Mik

Walter Bright wrote:
> The web site has changed; it now uses style sheets for layout rather than tables and embedded formatting. I essentially learned how to do this from the many examples posted here of possible new layouts for the documentation pages. Thanks to all!
> 
> I don't think the style sheet currently used is as good as the ones you came up with - at this point I was just interested in getting the layout into the style sheet. Now, we can just work on improving the style sheet.
> 
> http://www.digitalmars.com/d/changelog.html

Thanks a lot, Walter ! I can finally switch from DMD.157 :)
Yet the site is FUBARed in my firefox...


--
Tomasz Stachowiak  /+ a.k.a. h3r3tic +/

"Walter Bright" <newshound@digitalmars.com> wrote in message news:e5vard$26un$1@digitaldaemon.com...
> The web site has changed; it now uses style sheets for layout rather than tables and embedded formatting. I essentially learned how to do this from the many examples posted here of possible new layouts for the documentation pages. Thanks to all!
>
> I don't think the style sheet currently used is as good as the ones you came up with - at this point I was just interested in getting the layout into the style sheet. Now, we can just work on improving the style sheet.
>
> http://www.digitalmars.com/d/changelog.html

Thank you for the [static] assert messages.

o.new Inner?  Very cool.

Operator overloading of "in"?  Cool, but I can't seem to get it to work; I don't know what argument and return types are allowed, as it's listed in the Operator Overloading specs but has no documentation.  I tried:

class A
{
 int* opIn(char[] name)
 {
  return null;
 }
}

void main()
{
 A a = new A();
 int* i = ("hi" in a);
}

And all it said was that the rvalue of an InExpression must be an AA.  I tried a few different return types to no avail; I thought maybe it wanted a pointer type (as that's what in returns for AAs) but it obviously doesn't work.

Oh yeah, I really like the new "all links written in the exact same location" look for the left sidebar in Firefox ;)  Never seen so much text in one spot.

"Jarrett Billingsley" <kb3ctd2@yahoo.com> wrote in message news:e5ved4$2bod$1@digitaldaemon.com...

> Operator overloading of "in"?  Cool, but I can't seem to get it to work; I don't know what argument and return types are allowed, as it's listed in the Operator Overloading specs but has no documentation.  I tried:
>
> class A
> {
> int* opIn(char[] name)
> {
>  return null;
> }
> }
>
> void main()
> {
> A a = new A();
> int* i = ("hi" in a);
> }
>
> And all it said was that the rvalue of an InExpression must be an AA.  I tried a few different return types to no avail; I thought maybe it wanted a pointer type (as that's what in returns for AAs) but it obviously doesn't work.

Oh dear.  I saw Kirk's post, and thought "oh no."  Sure enough, this works:

class A
{
 bool opIn(char[] name)
 {
  if(name == "hi")
   return true;
  else
   return false;
 }
}

void main()
{
 A a = new A();

 writefln(a in "hi");
 writefln(a in "bye");
}

Notice that the expressions for 'in' are reversed.  It looks like I'm checking to see if the object 'a' exists in the strings "hi" and "bye".

Bug #1... ;)

Jarrett Billingsley wrote:
> "Jarrett Billingsley" <kb3ctd2@yahoo.com> wrote in message news:e5ved4$2bod$1@digitaldaemon.com...
> 
> 
>>Operator overloading of "in"?  Cool, but I can't seem to get it to work; I don't know what argument and return types are allowed, as it's listed in the Operator Overloading specs but has no documentation.  I tried:
>>
>>class A
>>{
>>int* opIn(char[] name)
>>{
>> return null;
>>}
>>}
>>
>>void main()
>>{
>>A a = new A();
>>int* i = ("hi" in a);
>>}
>>
>>And all it said was that the rvalue of an InExpression must be an AA.  I tried a few different return types to no avail; I thought maybe it wanted a pointer type (as that's what in returns for AAs) but it obviously doesn't work.
> 
> 
> Oh dear.  I saw Kirk's post, and thought "oh no."  Sure enough, this works:
> 
> class A
> {
>  bool opIn(char[] name)
>  {
>   if(name == "hi")
>    return true;
>   else
>    return false;
>  }
> }
> 
> void main()
> {
>  A a = new A();
> 
>  writefln(a in "hi");
>  writefln(a in "bye");
> }
> 
> Notice that the expressions for 'in' are reversed.  It looks like I'm checking to see if the object 'a' exists in the strings "hi" and "bye".
> 
> Bug #1... ;) 
> 
> 

The fix is simple: opIn is actually an opfunc_r without a corresponding opfunc (or a trailing "_r" in the name).

-Kirk McDonald