|
No worries. I've missed some pretty obvious stuff here already myself... 
You must be careful in the forest
Broken glass and rusty nails
If you're to bring back something for us
I have bullets for sale...
|
|
|
|
|
As the codeproject has the feature of submitting any articles ,it would be a nice idea to submit only a small bunchs of code ,like :for example a method that does any update or a class that help not all the article to write and a complete app to submit,
only small pieces of code or tips or helpfull methods like:
Subject : A method to make an encrypted data.
Text : This method will help you encrypt data at your own:
void MyMethod()
{
the tipping code
}
.
|
|
|
|
|
|
of course this bunch will has the description of it ,but not a big article,as it will be releated to a small piece of code and that will help i the tips ,as someone may need to know a method that returns the factorial of any number -for example- ,so i this pieces of code they may contain a method that does this thing ,with it's description ofcourse but not as big as the regular articles in the codeproject .
And ofcourse that will help in searching for ideas or methods only ,not have to read all the article to have the method ,with ofcourse understanding it.
|
|
|
|
|
It comes down to this: either the code itself is so trivial that there's no point to an article, or there's enough information that could be included that it doesn't make sense to post an article without it.
Example #1: A routine for generating an embossed icon
This is fairly simple - the code shouldn't amount to more than 20-40 lines, max. There are a few articles that cover it on CP, but maybe someone noticed that the question arises in the forums from time to time and decided to write an article dedicated to it. Such an article might cover:
- Decomposing icons
- What makes an image look embossed?
- Drawing onto a bitmap
- The DrawState() function, use, pros and cons
- Creating a new icon
Note that any one of those bullets could easily justify an article by itself - but in this example, only those areas relevant to the task at hand would be discussed. Even with that restriction, this would grow to well more than just a code snippet.
Example #2: Creating a bitmap from a block of memory
This is even simpler - fill in a structure and call one method. Yet it still should command more than a few paragraphs if an article is to be made of it. A discussion of bitmap formats, history of bitmaps in the Windows API, the difference between device-dependant bitmaps and DIBs (along with pros/cons of using them in different situations), perhaps even a mention of DirectDraw alternatives could be included.
Sure - many, perhaps even most of those reading such articles would skim through enough to become convinced that they'd found what they needed, then download the code and copy it into their app, never bothering to fully understand how or why it works.
That's not a valid concern for the author, however.
A professional application should not contain code that cannot be tested. Code that is not understood cannot be tested. Therefore, a site such as this, aimed at professional programmers, has no use for code posted without full explanations. This is even more important for small snippets that will be integrated into larger routines than it is for complete components or class libraries, where at least there is an assumption that some unit testing has been done on the whole item.
Finally, consider this: even the code snippets on MSDN occasionally have bugs. When they do, there is nothing to be done but submit a report and wait... maybe it'll be fixed in a reasonable amount of time, maybe it won't. Here, all articles (well, real articles) have forums attached - corrections can be made immediately visible. But what's not there can't be corrected ("was that left out for brevity? is it *supposed* to work that way?!"), so you're left with nothing but a piece of code, stuck in a vacuum, with no past nor future.
The web has plenty of this already...
Let's make the most of the opportunity afforded us here.
Medication for us all
You think you know me, well you're wrong
|
|
|
|
|
|
It comes down to this: either the code itself is so trivial that there's no point to an article, or there's enough information that could be included that it doesn't make sense to post an article without it.
Example #1: A routine for generating an embossed icon
This is fairly simple - the code shouldn't amount to more than 20-40 lines, max. There are a few articles that cover it on CP, but maybe someone noticed that the question arises in the forums from time to time and decided to write an article dedicated to it. Such an article might cover:
Decomposing icons
What makes an image look embossed?
Drawing onto a bitmap
The DrawState() function, use, pros and cons
Creating a new icon
Note that any one of those bullets could easily justify an article by itself - but in this example, only those areas relevant to the task at hand would be discussed. Even with that restriction, this would grow to well more than just a code snippet.
Example #2: Creating a bitmap from a block of memory
This is even simpler - fill in a structure and call one method. Yet it still should command more than a few paragraphs if an article is to be made of it. A discussion of bitmap formats, history of bitmaps in the Windows API, the difference between device-dependant bitmaps and DIBs (along with pros/cons of using them in different situations), perhaps even a mention of DirectDraw alternatives could be included.
Sure - many, perhaps even most of those reading such articles would skim through enough to become convinced that they'd found what they needed, then download the code and copy it into their app, never bothering to fully understand how or why it works.
That's not a valid concern for the author, however.
A professional application should not contain code that cannot be tested. Code that is not understood cannot be tested. Therefore, a site such as this, aimed at professional programmers, has no use for code posted without full explanations. This is even more important for small snippets that will be integrated into larger routines than it is for complete components or class libraries, where at least there is an assumption that some unit testing has been done on the whole item.
Finally, consider this: even the code snippets on MSDN occasionally have bugs. When they do, there is nothing to be done but submit a report and wait... maybe it'll be fixed in a reasonable amount of time, maybe it won't. Here, all articles (well, real articles) have forums attached - corrections can be made immediately visible. But what's not there can't be corrected ("was that left out for brevity? is it *supposed* to work that way?!"), so you're left with nothing but a piece of code, stuck in a vacuum, with no past nor future.
The web has plenty of this already.
Let us take the opportunity afforded us hear, and make the most of it.
Medication for us all
You think you know me, well you're wrong
 ;P;P;P;P;P;P
|
|
|
|
|
|
...I guess i'm being punished. 
You must be careful in the forest
Broken glass and rusty nails
If you're to bring back something for us
I have bullets for sale...
|
|
|
|
|
|
Colin Angus Mackay wrote:
Uh-huh....
Eh, was on a Tom Waits kick again today... happens now and again. 
You must be careful in the forest
Broken glass and rusty nails
If you're to bring back something for us
I have bullets for sale...
|
|
|
|
|
* Forums in bold have new messages since 7:33 Tuesday 5th April, 2005
good idea, but can you improve it?
Here it is 15h56 at this time, so 7:33 doesn't mean a lot to me. I think it changes every hour, but I'm not sure.
Local settings will probably be hard to implement, but something like
* Forums in bold have new messages since 30 minutes would be a bit better.
just a suggestion.
No hurries, no worries.
|
|
|
|
|
Why had no one answered you ?
I also suffer from this .
|
|
|
|
|
Hi Chris
It will be great if the session-timeout for a logged-in user is increased.
I open the code-project site as soon as i come to the office in morning and close it while leaving. So in between if i leave the site idol,my session expires and I have to re-login and locate the article again.
So it will be nice if session-timeout can be increased to atleast 1 hour.
Regards
|
|
|
|
|
With millions of users coming through every month long session times mean lots of stagnant sessions lying around consuming resources. The best thing to do in your situation is click the 'Remember me' box when logging in and at the end of the day click "sign out"
cheers,
Chris Maunder
|
|
|
|
|
Hi Chris,
Thanks for the quick response.
Regards
heeeee
|
|
|
|
|
I would like to be able to go straight to the posts from a particular day. Using the next button takes way too long if it was some days past. If I go to "search comments" and put in the date range I want and leave the keywords blank, then no articles come back.
In one case, even though I knew some words which were in a post and put them in the keywords box, the message I wanted didn't come up in the list.
It is great that the C++ board gets so many submissions, but it makes it very cumbersone and slow trying to move around. Is there already a way to go to a specific date that I've missed?
Thanks.
|
|
|
|
|
Good idea.
cheers,
Chris Maunder
|
|
|
|
|
|
I think there used to be an RSS Feed link for the CodeProject site, but I can't find it anymore? Am I dreaming? Or, has it been discontinued? Or, is it just buried somewhere deep inside the galls?
|
|
|
|
|
|
Hmmm, where can I find info on what the cat numbers are. I've tried cat=1 hoping that it would be C#, but it seems to be C# plus some other stuff. Precisely, do you happen to know the link for C# articles? Thanks.
|
|
|
|
|
On the homepage, select the tab for the types of articles you want to see and then scroll down the page to the "Last 10 updates" list. There is the RSS button/link. That will only include articles for the tab-section you chose.
This is the C# one[^]
Die Freiheit spielt auf allen Geigen
|
|
|
|
|
Thanks. I found it on the "Last 10 updates (category: C#)" heading. It's very well hidden in the entire orange scheme of colors with the button having the same color! Nice!!
|
|
|
|
|
Am I right that I found no forum where to discuss "I want to design an application this and that way, what do you think?" in a rather language-independent way?
--
Affordable Windows-based CMS for only 99 €: try www.zeta-producer.com for free!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
