|
An article of mine "Those Magnificent Men, a game for Windows"
[^] has been closed stating "This post is spam, abusive or otherwise inappropriate."
But I don't believe the article is either spam, abusive nor inappropriate. Can someone provide some clarification, or advice about how to improve the article so that it can be re-opened? Does it need some code samples(the original competition stated that we didn't need to provide any code samples)? Does it need more clarification on the choice of language, platform, etc.?
I have put a lot of effort into my project and have been working very hard on it for the past 5 months to move it forward. It is quite hurtful for someone to just close the article without leaving any suggestions on how to rectify the situation.
Thanks,
Ched
|
|
|
|
|
Ched, I am aware that there has been some conversation about this article. While you are correct that you originally submitted this against the AppInnovation contest, the concern that people had raised was that there were updates to this article that happened long after the competition closed, but which didn't show any code - in fact, the only thing other than screenshots, was a link to the indiedb site. It's certainly a bit cheeky of you not to be linking to the AppUp store, after all the competition was for entries in the AppUp store.
|
|
|
|
|
ah .. I had replied to him, not having seen the previous conversation - I did wonder about the 'commercial links'
I've since deleted my reply
|
|
|
|
|
Thanks for replying Pete,
I am aware that the competition is closed, but I would still like to finish my project and keep the code-project article up-to-date. Do you think I should move the article since the competition is over?
As I stated above, there was no specific requirement, originally to show code, although when I return home I will update the article with some example code, if this is what is needed to re-open the article.
The IndieDB link was provided for the Demo/Beta versions for users to access and possibly provide me with comments/suggestions while the project is evolving. I fully intend to submit the final version to the AppUp site. The IndieDB authorisation is quicker (released within 6-12 hrs) while the AppUp authorisation is slow (2 weeks I believe) and so it makes more sense at this stage of the project for the game to be hosted on IndieDB.
Ched
|
|
|
|
|
Ched1980 wrote: there was no specific requirement, originally to show code
That is correct.
Ched1980 wrote: when I return home I will update the article with some example code
Provided you give the article enough context and detail, that should bring it back into the remit of CodeProject.
Ched1980 wrote: the AppUp authorisation is slow (2 weeks I believe)
Sadly, this is true.
Good luck.
|
|
|
|
|
[^]
Is my published article. However there is a video link at the top. It is not embedding the video. Rather, only "Video" is coming. Can somebody please fix that to a video window where user can play the video?
|
|
|
|
|
No problem Grasshopper.iics. I have added the embedded video. Please note, if you need to make updates to this article in the future, I will have to do them so the video remains.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Why dont you show the list of persons who had voted. It will be very helpful for the author. Because sometimes we are getting good comments on the article but the voting shows poor. So we can come to know, whether the people who had really gone through article has done the voting or somebody else had voted.
|
|
|
|
|
Because if I want you to know it was me I'll write a comment. If I don't write a comment I don't want you to know I voted. If voting isn't anonymous I won't vote -- which do you want?
|
|
|
|
|
Do you mean to say the persons who are writing comments are voting? Because if the poor rating is given, I want to know the reason for it.
|
|
|
|
|
syed_babu wrote: I want to know the reason for it
You don't get to know unless people tell you.
Anyone can vote any darn way they like.
|
|
|
|
|
If someone votes 1, 2 or 3, (s)he must post a comment. In that case, you know who voted for your article. If someone votes 4 or 5, (s)he isn't required to post a comment. If he/she don't post a comment, then you don't know who voted. But if he/she post a comment, then you know who voted for your article.
In some cases, my signature will be longer than my message...
<em style="color:red"> <b>ProgramFOX</b></em> ProgramFOX
|
|
|
|
|
Hi,
I'm writing an article about how bitwise operators work. But because bitwise operators are operators that are available in many languages (C#, VB.NET, C, C++ ...), so I don't know which section I should choose for my article.
Any ideas?
In some cases, my signature will be longer than my message...
<em style="color:red"> <b>ProgramFOX</b></em> ProgramFOX
modified 12-Feb-13 13:52pm.
|
|
|
|
|
ProgramFOX wrote: I doubt about the section of my article. I'm not sure what you mean by that, but why not just show examples for each language that you are discussing, and let the reader look up their own reference for any languages you do not support.
|
|
|
|
|
Richard MacCutchan wrote: I'm not sure what you mean by that
I mean that I don't know which section I should choose for my article.
In some cases, my signature will be longer than my message...
<em style="color:red"> <b>ProgramFOX</b></em> ProgramFOX
|
|
|
|
|
Are you presenting some example code? If so, you choose the language in which you are writing your code.
|
|
|
|
|
Yes, but I write code in C# and VB.NET.
In some cases, my signature will be longer than my message...
<em style="color:red"> <b>ProgramFOX</b></em> ProgramFOX
|
|
|
|
|
General Programming -> Programming Tips I suppose.
"Bastards encourage idiots to use Oracle Forms, Web Forms, Access and a number of other dinky web publishing tolls.", Mycroft Holmes[ ^]
|
|
|
|
|
|
Hi syed_babu,
I took a look and everything looks OK now, is that the case on your end as well? Please let me know.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Hi Sean,
Thanks for your response. I'm able to see the contents now but not the download links for my code.
|
|
|
|
|
|
Steve. Have a look at it now (you may need to Ctrl+F5). I've updated the feed and it's been pushed into live now. The HTML should be good to go.
|
|
|
|
|
It looks perfect.
Is there anything I can do to avoid this in the future?
Steve Wellens
|
|
|
|
|
I just fiddled about with the spacing after the pre tags and changed the " to ' for the first JavaScript entry. After that, it seemed to be okay.
|
|
|
|