|
We've had several C questions in the C# forum today. Could you please add a simple sentence to the C# forum header, something like:
C# is not C, it is a C descendant (as are C++ and Java); C# is one of the managed programming languages that fit the .NET FrameWork. Please use the appropriate forum.
TIA
|
|
|
|
|
Come on Luc, it's only the regulars who will read it, and they don't need telling!
|
|
|
|
|
with that excuse most texts would be useless.
|
|
|
|
|
I'm not making excuses I'm making observations.
|
|
|
|
|
A thought-terminating cliche, to be precise. You could just as well say that it takes "all kinds of people" to "make CodeProject go round". When a group is to play nicely together, then they need to agree on some basic terms on which they play together.
Those terms or rules are there to protect the group as a whole and the individuals, and they need to be public. Without a common ruleset, you'd have anarchy. Or, at the very least, a different interpretation of the HTML4-specification for every existing browser 
I are Troll 
|
|
|
|
|
Eddy Vluggen wrote: Without a common ruleset, you'd have anarchy.
Well we have a common ruleset as published in the guidelines for posting questions, and still people ignore them, and we do have (some) anarchy. My observation is that adding more text at the top of the page is not likely to have a significant effect on this. Call it excuses or cycnicism or whatever, I am making an observation based on years of dealing with users from the sharper ends of customer service, and these forums.
|
|
|
|
|
If it's any consolation, we get a load of *your* questions in *our* nice C++ forum too!
(OK, more CLI than C~, but still!)
"Oh, it begins with the same letter, that'll do!" works both ways.
And if you think those posters read the stickies, I have a bridge to sell you...
Iain.
I have now moved to Sweden for love (awwww).
|
|
|
|
|
Thanks for the bridge offer, but no thanks.
I suggest every forum gets a simple sentence explaining what it is for, and also naming (and prociding links to other forums) the one or two most popular subjects it is not for.
Putting up some signs can't be wrong; not everyone going to read them is no reason not to do it.
|
|
|
|
|
Luc Pattyn wrote: Putting up some signs can't be wrong; not everyone going to read them is no reason not to do it.
Thinking logically you are absolutely right.
It's a bit like those signs outside country towns in the UK that say "Please drive carefully through our town". Ask any resident how many people drive too fast ...
|
|
|
|
|
My favourite sign was by a school near where I used to live:
"Slow
Children Crossing".
Oh, the power of a missing comma...
Iain.
I have now moved to Sweden for love (awwww).
|
|
|
|
|
I've also seen "Slow Police Checkpoint" and "Warning Stationery Vehicle".
|
|
|
|
|
Luc Pattyn wrote: I suggest every forum gets a simple sentence explaining what it is for
That information is already shown in the title. Do you think that repeating it on the same page will make any difference?
Sorry, I'll side with Richard on this one.
|
|
|
|
|
that was half my sentence, I suggest also to name at least one thing it is not for, if experience has told us people seem to get confused.
|
|
|
|
|
Well, come on; where do you draw the line with that? Does every forum then get a statement of what it's for, followed by an ever-growing list, stating everything it isn't for? I think you're just going to have to deal with the occasional idiot that posts in the wrong forum; you could add notices telling them not to till the page was nothing BUT notices, and some would still post there anyway. I think you're deceiving yourself if you think another notice will make a difference.
|
|
|
|
|
Iain Clarke, Warrior Programmer wrote: And if you think those posters read the stickies, I have a bridge to sell you...
Brilliant. 
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
Here[^] is another abuser of your site I'm afraid.
|
|
|
|
|
Looks like he cleaned up his own act
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
It's still there as far as I can see.
|
|
|
|
|
Is there a problem with the pre tags? Have a look here[^]. It did some wierd stuff with some hyperlinks, italic and code tags so I took them out, but removing the pre tags would incur the wrath of Luc which I don't want this early in the morning!
(Only one is showing incorrectly by the way)
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Why are you using VB6? Do you hate yourself? (Christian Graus)
|
|
|
|
|
Hi Davey,
I waited for the afternoon before replying to you message. 
Yes, there (still) are weird things going on with PRE tags.
Yesterday (working on this[^]) I tried to get the first and last line marked special, either colored red by adding a <span style='emphasis'>, or bolded with <b>, and that worked well for the first line and failed for the last one.
I once read a message claiming only every second TAG pair works inside PRE; not sure about that though.
Also the linecount trick does not always work. And then there is the default language issue.
|
|
|
|
|
I hadn't noticed it before, but then I haven't been as active as normal here for the last few weeks - been overloaded at work
I wonder how they've managed to introduce a bug into something that's worked perfectly for eons?... probably something to do with tweaks for Q&A.
I'm sure Chris and the boys/girls will sort it 
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Why are you using VB6? Do you hate yourself? (Christian Graus)
|
|
|
|
|
I'm not sure it ever worked correctly. For a long time I was assuming tags were not allowed inside PRE/CODE blocks. I do remember the following changes in the last couple of years:
- handle empty lines
- syntax coloring added
- process smileys (almost) correctly
- added linecount='on' (on my suggestion)
So if some bug got introduced, I guess it was while implementing one of the above.
BTW: there also is a "comments and string literals coloring" anomaly.
I tested more thoroughly when I recently decided to put more and more info in my "use PRE tags" T&T
|
|
|
|
|
This is actually an old bug. If you don't put quotes around the "text" in
<pre lang="text" it can fail.
It's on the list.
cheers,
Chris Maunder
The Code Project Co-founder
Microsoft C++ MVP
|
|
|
|
|
Ah... cool. I never have put quotes around them, I'm not sure why! It makes sense to create valid html when using characters instead of/as well as numeric values.
Is there a list of allowed attributes we can add in to the various supported tags anywhere?
(Thanks for fixing the post!)
Dave
BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)
Why are you using VB6? Do you hate yourself? (Christian Graus)
|
|
|
|
|
To test what was going on with the digital-clipart.de site, I created a new user via the site, and posted a message - all worked ok, which is a bit odd. Please delete the new account "JustATest, really", if you would be so kind!
All those who believe in psycho kinesis, raise my hand.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
