Thread: Proposal: Code colouring

95% of the noobs only post in code tags because we have a script which won't let them post code without them. Even then, there are a few creative idiots who still manage to screw that up.

On other boards, untagged code is routine, and so is the nagging to get the noobs into line.

Even when it's tagged, they've obviously either never used indentation, or used some horrid mix of spaces and tabs (see past GD topics) and the code still looks like a mess. "HELLO PEOPLE" the preview button is there for a reason.

> when you upload a page it will load your defaults so you see it as you wish.
Excellent - I'll turn it all off thanks.
At least it won't be me coding that system, and ensuring that through the myriad of choices that everyone sees exactly the same code.

>> Even when it's tagged, they've obviously either never used indentation, or used some horrid mix of spaces and tabs (see past GD topics) and the code still looks like a mess.

Well, that's not a problem with the colouring at all, it could be blamed on the tags but mainly the newbs themselves. You can't change how they are going to post their code. They just want answers, nothing more. So perhaps an indentation-beautification treatment with the code tags might be worth implementing, if not the colouring. But then it'll be absolutely necessary to make sure that they don't "do a fine job of actually corrupting the code".

>> Excellent - I'll turn it all off thanks.
That's your choice. But I find it easier to 'see' errors in code when the code itself is in colour. I mean the obvious ones, such as people messing up "'s and such. The same goes for the indenting which is one of the reasons why we get so upset with people don't use them. I find it somewhat ironic that you petitioned so hard for code tags, granted it wasn't only for the reasons I've given, but do not wish for code colouring. Only somewhat. I understand they are not the same, don't worry.

edit:
>> Great idea, but I'll take 95%, thanks.
I reported some bugs to you, so with inflation, exchange rates, political tensions ... mumbles ... I'll have 23%

Code coloring and some sort of auto-indention would be great. I don't want to get picky about the proper way to beautify code, but at least if some standard was used here, it would be easier to see what the clueless people are doing or not doing.

Given the format of other tags, like [quote], I think if this feature was enabled it might have this syntax:

Code:

[code]
or
[code=language]
or
[code=language;style] (maybe)

I agree that if this were enabled there would probably be arguments about which style was better. Perhaps it could be colour coded and the viewer could choose the style, in their User Profile or something?

Another blow for PHP code tags: In IE 6, when you have a PHP code block selected (i.e., you click on it) you can't scroll with the keyboard: up, down, page up, page down, nothing works. You can of course just click off to the side. But it annoys me at least . . .

(Yes I know that IE 6 is not the best browser in the world . . . this is not my computer.)

One thing I was wondering was how come the php script-colour-er is enabled. Not so much 'why is it enabled', I know it's in a good few programming forums, but why is it so common around the place? Is it just ... there or something?

A vBulletin (and other forum software) default?

One thing I was wondering was how come the php script-colour-er is enabled. Not so much 'why is it enabled', I know it's in a good few programming forums, but why is it so common around the place? Is it just ... there or something?

PHP can highlight itself. It's built in to the language. So any board written in PHP usually supports highlighting PHP.

>> Perhaps it could be colour coded and the viewer could choose the style, in their User Profile or something?
Yeah, that's what I suggested. Could be defaulted to nothing and you change it, or something.

Now that's an idea!

But I think that you should still need to mark code that is to be coloured, because having all code coloured would be annoying (see my first post).

Elseweb, on sites that have introduced it, at first it seemed nice to me. But it's always someone else's scheme, so as the novelty wears off it ends up looking to me as unappealing as the PHP code coloring.

I think it would be interesting to be able to post with some magic tags that present code in the same manner as my editor. But then again, as Salem mentioned, plain Jane code tags display the bad formatting that is the issue often in newb-presented code. And as has also been mentioned, I am also one who likes to take "plain" code tags and use my own coloring to highlight certain parts of the code.

So by default, the enforced code tag script is best for newbs and passersby. If a special colorizer were available, I would be unlikely to use it. I've even stopped using the minimal one I started to write long ago. (Once in a while, however.)

I understand the sentiment, but I think you may also arrive at the "keep the status quo" point of view after you've come full circle.

I think my/twomers' idea is a good one: you put

Code:

[code=c++][/code]

and each member gets to choose how coloured C++ code is displayed. Perhaps they could choose Dev-C++ style, or Kate style, or no style (disabled altogether).

But then if they had Kate colouring for example, and the author had highlighted a few specific lines... oh noes

I voted yes, as highlighting code, especially if more than 20 or so lines, can make things easier to pick out. Fundamental C syntax things like "if", "while", "sizeof", "long", or "unsigned" would be one color. Common C functions like "printf", "scanf", "malloc", "fopen", etc. would be another, strings as another, and everything else as fourth.

This image gives a decent overview of some of it - blue is for C's fundamental key words, white for basic syntax, teal for user functions, red for variables, yellow for structs, magenta for numbers, and green for comments.

Originally Posted by zacs7

But then if they had Kate colouring for example, and the author had highlighted a few specific lines... oh noes

Why do you keep bumping old threads?

Wow! I didn't notice that this thread was a month old! I still support the idea though.