"Alix Pexton" <Alix@seven-point-star.co.uk> escribió en el mensaje news:01c210a9$d79b6cc0$e1257ad5@jpswm...
> > I like it. IMHO, I would prefer the Code section not to be inside a box.
>
> It doesn't have to be in a box, it's just one line of css, but I think
that
> something should be done to make it absolutely clear what is code and what isn't. Most magazines do something to highlight segments of code, no
matter
> how short, ant it does help readability, but then so does the syntax highlighting...
I understand that. It was just an opinion.

>
> I foresee that the journal will definitely be designed by committee...
>
> Alix Pexton...
I think that's a must.

Alix

This looks really good. It looks like we may be up and running sooner than I first thought. I'll have to start organising the contributors soon.

Are we to take it that you've kind of volunteered yourself as the layout/presentation guy?

Matthew

"Alix Pexton" <Alix@seven-point-star.co.uk> wrote in message news:01c210a2$3ac60ec0$e1257ad5@jpswm...
> > Don't kill yourself to get something immediate, as we're still in the process of garnering enough support to get this baby off the ground.
> Early
> > signs are encouraging though.
>
> I'm still alive, so I attached a very simple mockup of what the journal might look like...
>
> Alix Pexton...
>

I like the box

Style will have to evolve over the next couple of months, but I think we have a good base to build on here.

I'm going to knock up a fictional first magazine content list, and then if you could lay that out we could see how a full magazine would look in HTML pages, in order to get a more informed opinion from everyone.

Matthew

"Alix Pexton" <Alix@seven-point-star.co.uk> wrote in message news:01c210a9$d79b6cc0$e1257ad5@jpswm...
> > I like it. IMHO, I would prefer the Code section not to be inside a box.
>
> It doesn't have to be in a box, it's just one line of css, but I think
that
> something should be done to make it absolutely clear what is code and what isn't. Most magazines do something to highlight segments of code, no
matter
> how short, ant it does help readability, but then so does the syntax highlighting...
>
> I foresee that the journal will definitely be designed by committee...
>
> Alix Pexton...

What about a D tip of the week/day in the right hand bottom corner. I could even just be a random one from some database.

"Alix Pexton" <Alix@seven-point-star.co.uk> wrote in message news:01c210a2$3ac60ec0$e1257ad5@jpswm...
> > Don't kill yourself to get something immediate, as we're still in the process of garnering enough support to get this baby off the ground.
> Early
> > signs are encouraging though.
>
> I'm still alive, so I attached a very simple mockup of what the journal might look like...
>
> Alix Pexton...
>

"Alix Pexton" <Alix@seven-point-star.co.uk> wrote in message news:01c210a2$3ac60ec0$e1257ad5@jpswm...

> I'm still alive, so I attached a very simple mockup of what the journal might look like...

Looks great!

I wonder how was this piece of code made? The colors look very familiar
(in fact, those are my preferences in Visual C++ editor)... =)

By the way, I guess we'll need some kind of coding standarts for the site, like where to put braces etc... =)

Ouch!

That's going to start a war

I am not convinced we need a coding standard for the site, though. Personally I go for the Allman style

    if(x)
    {
        y;
    }

mainly because it lends clarity when the conditional expression is complex. However, I have learnt over the years - even in situtations where I've written the coding standards! - that people will not be forced away from their own style.

I would much prefer that we encourage contributions as much as possible, and let the style evolve collaboratively. Also, it can be good mental exercise to read in another style every now and then.

 ... "Yeah, and it came to pass that the wisdom of "my" style fell upon
thee!"

Matthew

"Pavel Minayev" <evilone@omen.ru> wrote in message news:ae3u73$1ell$1@digitaldaemon.com...
> "Alix Pexton" <Alix@seven-point-star.co.uk> wrote in message news:01c210a2$3ac60ec0$e1257ad5@jpswm...
>
> > I'm still alive, so I attached a very simple mockup of what the journal might look like...
>
> Looks great!
>
> I wonder how was this piece of code made? The colors look very familiar
> (in fact, those are my preferences in Visual C++ editor)... =)
>
> By the way, I guess we'll need some kind of coding standarts for the site, like where to put braces etc... =)
>
>

We are getting lots of interest in this. Thanks for that all you guys

I'll let it run until the weekend, and then count up the volunteers and suggestions, and post a tentative plan for the first issue.

Thanks again. I think this is going to be fun and educational for all of us

Matthew

Pavel Minayev wrote:
> "Alix Pexton" <Alix@seven-point-star.co.uk> wrote in message
> news:01c210a2$3ac60ec0$e1257ad5@jpswm...
> 
> 
>>I'm still alive, so I attached a very simple mockup of what the journal
>>might look like...
> 
> 
> Looks great!
> 
> I wonder how was this piece of code made? The colors look very familiar
> (in fact, those are my preferences in Visual C++ editor)... =)
> 
> By the way, I guess we'll need some kind of coding standarts for the
> site, like where to put braces etc... =)
> 
> 

-1 - The standard should be that the code is readable.  If that is the case, who cares where the braces are.  This is the stuff of pedantic flamewars that have no logical conclusion.

-Andy

> I'm going to knock up a fictional first magazine content list, and then
if
> you could lay that out we could see how a full magazine would look in
HTML
> pages, in order to get a more informed opinion from everyone.

OK...

Alix Pexton...

> I wonder how was this piece of code made? The colors look very familiar
> (in fact, those are my preferences in Visual C++ editor)... =)

I wrote in all the highlighting by hand on this occasion, but I have also rewritten a certain D sample program so that it emits code that is css-able (uses spans instead of font tags). The colo(u)r values came from the aforementioned sample program...

> By the way, I guess we'll need some kind of coding standards for the site, like where to put braces etc... =)

As far as code style goes, along as it compiles (if included as a part of a full program) then that's OK, we could always have a section in the journal dedicated to discussing (read "arguing" if you like) the merits of different styles.

IMO, discussions about coding style amongst seasoned programmers are
pointless, as we'll never change now that when we press enter is a reflex
not a
conscious decision. But on the other hand, a good debate is always good for

the newcomers.

Alix Pexton...