 |
|
|
You could do a lot better in this article. Now I haven't downloaded the code so I honestly don't know how good it is or if it will benefit me in any way. But that's what your article was supposed to tell me in the first place. A small section on how to use it and perhaps a sample output would have been more beneficial. Also the fact that the page your article links to has a popup window is does not encourage people to download your code and try it out.
Just my 5 cents.
Wenn ist das Nunstück git und Slotermeyer? Ja! Beierhund das oder die Flipperwaldt gersput!
|
|
|
|
|
|
|
I just wanted to post this.
Try this @ home. (B&B)
|
|
|
|
|
|
|
Hi Dabs,
Thanks for your posting.
I should think of that.
Meanwhile I have added some new links in this article.
Regards,
Alex
|
|
|
|
|
|
|
Meanwhile I have added some new links in this article.
Alex, that's nice but the point here is to write an article that people can read. When I first saw this, I was immediately interested in reading an interesting article, and was disapointed to find little or no content. If I want links I can search on Google.
I do hope you find the time to update this article with more information ! I am waiting anxiously!
¡El diablo está en mis pantalones! ¡Mire, mire!
|
|
|
|
|
|
|
Jim Crafton wrote:
the point here is to write an article that people can read
I meant to post source code.
I didn't know that this is a place for posting arcticles but not (only) code.
It was my mistake.
Is there a place on CodeProject for posting source code ?
Regards,
Alex Vinokur
|
|
|
|
|
|
|
Is there a place on CodeProject for posting source code ?
Well that is what the links are for. Ideally what you want (IMHO) is an article that outlines what the code does and why, and then some explanation of either how the code works, and/or how to use it. If the code is extremely complex, you might consider breaking the whole thing into mutliple articles, perhaps a initial article that goes over the theoretical and/or design issues, and then a follow up article explaining how to actually use it. If the article is about code that makes up a full tool, then the article might focus more on how to use the tool then the actual code implementation.
For example, your Turing article might start by explaining what a Turing machine is, what it is used for, and why is it useful. Explain how you went about implementing your classes. Explain the relationships between your various classes and how they interact together.
Without this all we have are some URL's to your code, that we then have to open up and work this out for ourselves, which, admittedly, is not neccessarily a bad thing, but if this is all I wanted I could just browse around SourceForge or FreshMeat and pull down code. CodeProject is nice because not only can you find code, but you find explanations of the code and that in and of itself is extremely useful (or at least that's my outlook on it).
¡El diablo está en mis pantalones! ¡Mire, mire!
|
|
|
|
|
|
|
Thanks.
Jim Crafton wrote:
CodeProject is nice because not only can you find code, but you find explanations of the code and that in and of itself is extremely useful (or at least that's my outlook on it).
I agree with that.
I am usually posting my code to sites that don't require explanations of the code.
So, I supposed that CodeProject is similar to those sites.
I intend to write explanations.
I think it will take some time.
Regards,
Alex Vinokur
|
|
|
|
|
|
|
Alex,
I checked your user profile, and you have been a member of CodeProject for less than a month. You are to be congratulated for posting articles so quickly! However, I am surprised that you didn't look around the site a bit more before posting them.
Just look at any of the articles that are linked from the front page, and you will notice that they are usually quite lengthy, and have considerable detail.
You should really dig around a site and find its purpose before spamming, regardless of how valuable that spam may be.
--
Paul
"I drank... WHAT?"
|
|
|
|
|
|
|
Paul A. Howes wrote:
I checked your user profile, and you have been a member of CodeProject for less than a month. You are to be congratulated for posting articles so quickly! However, I am surprised that you didn't look around the site a bit more before posting them.
Just look at any of the articles that are linked from the front page, and you will notice that they are usually quite lengthy, and have considerable detail.
You should really dig around a site and find its purpose before spamming, regardless of how valuable that spam may be
Caught.
Thanks.
Alex Vinokur
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Rant 
Admin