While we are more than willing to help those that are stuck, that doesn't mean that we are here to do it all for you! We can't do all the work, you are either getting paid for this, or it's part of your grades and it wouldn't be at all fair for us to do it all for you.
So we need you to do the work, and we will help you when you get stuck. That doesn't mean we will give you a step by step solution you can hand in!
Start by explaining where you are at the moment, and what the next step in the process is. Then tell us what you have tried to get that next step working, and what happened when you did.
Even if we did do your homework for you - which we don't - this would be very much the wrong place to post this!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
I was thinking… once I publish an article on CodeProject, does CodeProject own any copyright rights on that article and code?
Can I publish that article text or code in some other place as well? Use it in my presentation without mentioning CodeProject?
Also, Editor made some changes to the text… spelling, grammar, style changes. That is some work contributed to the article. Who owns copyright now to that version/revision?
If you contribute documents or articles in any form or media ("Documents"), you give us the necessary rights to edit and post and maintain your Document (and the edited version), and to prevent unauthorized uses by end users of Documents that we edit. End users are given rights to read your Document, but no rights to republish or otherwise distribute your Document. CodeProject will retain your copyright notices, and can publish your name and site ID with your posting. If we edit your Document, we will own the edited version, and you will own your original version. We cannot publish our edited version other than on the Site, without your consent.
I see that in article creation form there is a button "paste from Word". I tried it and it preserved/recognized Heading2 as Heading2 html tag and mapped Word paragraphs to <p> html paragraphs.
Is there a rule, which Word style would be mapped into <pre> tag, that is how to present source code in Word text so that it would be mapped into <pre> tag that is used for code in articles html?
I know there are other text editors and I am using Notepad++, but Word has better spell/grammar check....
"Paste from Word" does its best, but unfortunately it is not perfect. If you are having trouble with any article editor issues, please save it in composing status and send it to email@example.com.
I am thinking of writing article that would not be programming topic, but more like a software technology overview of certain domain. With general concepts, definitions, pictures of applications in domain etc. But no code samples or similar. Would this site be a good place for that article, or maybe you can suggest some other place on the net to publish it.
Also, for another article, related to telecommunication wireless IP networking and some technology topics related to it like routing and application experience. Where would be proper place to publish it?
An article that discusses software from a high-level perspective should be OK. But I can only speak as a moderator, so I'll summon @sean-ewington so that you can follow up with him if you're planning an article that doesn't have much of a software angle.
There must be at least 20 of them so far. And given the narrow focus of each one, there could be 100 more on the way. Some have formatting issues (images that are too wide), but I guess the central question is whether the site has a problem with this in general. @sean-ewington
This user's blog feed was broken. Last week I helped them fix it and this was the result. Seems like the posts have stopped now. Less than a quarter of the ones that made it through went live. Save for the blog reference at the bottom of the page, none of them have links back to the blog, and all of the formatting issues have been fixed. If you find any entries leftover that you deem too narrow a focus, please feel free to report the article as unclear or incomplete, or extremely poor quality.