|
I third it and our UML designer fourths it.
I support two teams: the Canucks and whoever is playing the Leafs!
|
|
|
|
|
A significant percentage of newbie posters systematically forget to check this option on, so that their snippets of code are unreadable. My proposal tries to remedy this while having the least impact on more seasoned users:
- This option is a user profile dependent config option.
- Existing users keep their status quo (i.e. the option is initially set off
for them.) - Starting from the date the patch is applied, new users will have the option set on by default.
- Every time an user posts a message, the option used (set on/set off) gets saved to her profile as the default for subsequent posts.
What do you think of this? Regards
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
good idea
for me the best solution would be that the parser will not handle html tags inside the <pre> and <code> sections
|
|
|
|
|
I wouldn't like to be deprived of the possibility of embedding tags inside <pre> sections. It allows me to write things like:
Change the function declaration to
extern object clone(<font color=ff0000>const</font> object& x);
Furthermore, newbies usually paste the code without any <pre> (they probably don't know this can be used.)
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo
|
|
|
|
|
|
|
...a Bob bobble head doll!
WHAT a treasure! (And highly collectable, as well.)
Ya gotta do it - ya just gotta! Dave, Chris, trust me on this one! It`s gonna be GrrrrrrrrrrrrreeeeaaaTTTT!
|
|
|
|
|
Already checked into pricing.
All I can say is:
cheers,
Chris Maunder
|
|
|
|
|
Maybe if you order 500,000 of them, the price per unit should definitely come down
Sonork 100.11743 Chicken Little
"You're obviously a superstar." - Christian Graus about me - 12 Feb '03
Within you lies the power for good - Use it!
|
|
|
|
|
Maybe I've already overlooked them in my haste, but I haven't seen any forums devoted to DirectX, OpenGL, or other API's of the like. What happens when someone has a question about a DirectX project they're working on but they're doing it in VB. Yes they can take it to the VB forum, but there's also a lot of people who know DirectX in the C++ part as well. The opposite would be true as well. A few ideas on how to work this:
-One forum devoted to API's as a whole
-Separate forums for the most popular API's
-Subforums for the API's under the respective languages ( C#->API )
-Subforums for the different API's under the language forums ( VB->DirectX, C++->OpenGL, etc )
Any thoughts?
Always Fear the Man with Nothing to Lose
Jeryth
|
|
|
|
|
IMHO, the current approach - focusing more on the task than on a potential tool - is better in most cases. However, it would be nice in certain situations to have a very granular API forum - being able to group questions & answers by a specific API (all random data for SetWindowPos() ) could come in handy were it used correctly.
Still, the CP search function does quite well for this last use, and given the potential for abuse (users cross-posting when they can't decide on a correct forum) seems like it may be an acceptable compromize for the time being.
Shog9 -- Exchanging a walk-on part in the War for the lead role in a Cage
|
|
|
|
|
Maybe I understood your post a little differently than you intended, but this might serve to clarify it for others. I didn't mean to employ all four ways I listed, but to select one that might work and use that and forget the others.
Always Fear the Man with Nothing to Lose
Jeryth
|
|
|
|
|
Currently, there is one "Result" bar that displays readers' feedback about an article with regards to how they rate it.
A good idea would be to add a second "Result" bar to reflect readers' evaluation of the same article (and it's sample code) if the author should update the work. The general idea is that after an article has been posted, many times the author will respond by improving his/her work due to the feedback received. It would be good for the general readership, when they see two "Result" bars, to know that the work has been updated, and can judge whether it was done for the better or the worst (because of the new evaluation responses the community would be giving).
Looking at the situation the way it is now, if an article (and its accompanying code) started out poorly and duly received poor rating, but due to the feedback the original article received, the author may have tremendously improved its quality and contents, hardly anyone would know if it was improved for the better or the worst. One "Result" bar does not accurately reflect the new reception the upgraded and improved work would be (deserving of) getting. A second "Result" bar would.
If the thought is that a single "Result" bar adequately does the job (and would continue doing it) if the work is improved (because readership would then start giving it improved rating), is exactly the point, but it would be mixed in with the old rating that reflected the poor quality it was before. That poor rating (the original "Result" bar would show), may just discourage a new reader from reading what has been markedly improved. A second "Result" bar would leave no doubt to those who see a second bar, that it may just worth their while to review the improved version of the article (which may just turn out to be to the reader's benefit but which ONLY would have happened because he/she saw a second "Result" bar).
If after a while, the second bar start showing the same level of rating as the original one, the other members would know it's not even worth their time to give the article a second glance. (The appearance of a second bar came through beneficially again.)
William
Fortes in fide et opere!
|
|
|
|
|
A second bar doesn't seem to scale well, do you add a third bar if the article is revised a second time?
A different way to address the same problem might be to just let people change their vote. That was my instinctive desire when faced with an article that had been improved with a revision or two.
--
-Blake (com/bcdev/blake)
|
|
|
|
|
No, you don't add a third bar, nor a fourth, nor a fifth (etc.) every time the article is revised. There will ALWAYS be just two bars; one representing the current rating, and the other representing the previous rating, with the readership getting to vote anew every time the article gets updated. That ability to vote anew only becomes doable when the article is revised.
The idea of being able to vote anew with only one "Result" bar present, is that it would invalidate (or corrupt) the previous rating for the work (as it existed) prior to it being updated, leaving the general readership without a means of knowing whether the updated work was better, worst, or of the same quality (whatever that might be) prior to it being updated.
The second bar simply adds a comparative means to the prospective reader in deciding whether to do a second reading of the work or simply pass it over.
William
Fortes in fide et opere!
|
|
|
|
|
The problem with having a fixed two bars tied to the current edit and the last one is that a simple typo correction would roll things over. Hmm, perhaps in conjunction with some sort of 'Is this a minor or major edit?' prompt when saving changes.
--
-Blake (com/bcdev/blake)
|
|
|
|
|
Your point of having a prompt asking if the update is a minor or major one, is well taken in that a "minor" reply would not cause a rollover. A "major" reply would cause a rollover, but would necessitate the sanction of an editor at CP to make that determination.
William
Fortes in fide et opere!
|
|
|
|
|
this CP forum is without a doubt the most code bloated forum I visit
I don't think it's strictly a server load issue because I watch the task-mgr-networking, and clicking buttons on the CP forum causes my 56K network connection jump to 90% until the thing finishes loading....
Is that "cool" tree control with indents for thread posts really worth it ? Or whatever is causing that network congestion
I saw some earlier posts about work schedules for next year, here's a thought...
Why not optimize the forum section ? There are many snappy no-bloat forums out there for examples (see www.freerepublic.com for USA right wing example)
The articles are useful too, but I reallllllllly like the forums here because the poster's mostly seem to be computer geeks & wether we like it or not, we really are a bit different than other people !!! ie, the writing style is much more concise
Other forums seem to be completely infested with the same type opinion posters, but here at CP the common thing is computers and the opinions are everywhere !!!!!!!!!
|
|
|
|
|
You might want to check out the options you have set (the bar, right above the forum). Yes, the amount of data dumped on your poor browser at 50msgs/dynamic view is huge - but you get 50 messages to read without a reload too. If you're just browsing, then threaded view may be more your thing. Or, if you tend to read just the latest few messages, maybe reduce the # per page to 25 or 10.
Shog9 -- Exchanging a walk-on part in the War for the lead role in a Cage
|
|
|
|
|
Yes I set the "view" listbox to "threads" for 56K modem and this works much better !!!
|
|
|
|
|
greghop wrote:
Is that "cool" tree control with indents for thread posts really worth it ?
You bet it is. I'm on a modem at home and I love the fact that I can get a whole page of messages and read several, all with only one page load. I remember the time before that feature was implemented, and having one page load for every... single... post... I... wanted... to read... was unbearable. Switch your viewing mode to "Normal" and see for yourself.
--Mike--
Ericahist | CP SearchBar v2.0.2 | Homepage | RightClick-Encrypt | 1ClickPicGrabber
|
|
|
|
|
Why not give articles that have won a competition a special Bi-Line as to what is so good about them, so some of us aspiring authors have something to strive for.
Regardz
Colin J Davies
* WARNING * This could be addictive The minion's version of "Catch "
It's a real shame that people as stupid as you can work out how to use a computer. said by Christian Graus in the Soapbox
|
|
|
|
|
Almost had this done, then travel got in the way. It's gonna happen.
cheers,
Chris Maunder
|
|
|
|
|
Why don't we have a topic of the day ?
Regardz
Colin J Davies
* WARNING * This could be addictive The minion's version of "Catch "
It's a real shame that people as stupid as you can work out how to use a computer. said by Christian Graus in the Soapbox
|
|
|
|
|
I'm not quite sure how the article process here works (having not written one myself), but I think it would be in the interests of sanity and the quality of the site to prevent articles this poor from getting onto the main sections of the site and into the RSS feed (where upon, I get annoyed and end up writing suggestions like this one):
http://www.codeproject.com/aspnet/AspNetEXButton.asp[^]
Therefore I suggest some sort of queue - which is still visible to all users of the site (this is important), but articles are not sectioned or placed on the main page until either an editor has taken a shufty at it (not necessarily edited it), or the article has been voted to some suitable score, say 2.5 (as an article might have good content or ideas, but be poorly written or explained). Articles would not count towards a users article count until they were out of the queue. Anything that consistently got voted poorly could be booted automatically after a period of time. articles that consistently got voted averagely or well could be automatically added to the main site.
The link to the queue could either be a separate tab on the main page, or a link in the sidebar.
At any rate, what I'm interested in is improving the S/N ratio or articles on the site (which is already good, but things this poor shouldn't even see light of day)
--
Ian Darling
"The moral of the story is that with a contrived example, you can prove anything." - Joel Spolsky
|
|
|
|