|
Is it just unrio17.png? I can see it displayed when I look at the article.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Ok, I just looked at it again and you are right.
Hmm....
That is odd. When I checked the article earlier, I noticed the image didn't show.
Oh, well, it's not like these computer things are based upon science of any type. 
Thanks for looking into it. 
|
|
|
|
|
Because of a current occasion I want to repeat my suggestion from several month ago (which didn't get a response from the admins then):
If it's not intentional that the Moderator Forum is kind of hidden like it is I would suggest making it more visible (for the members with sufficient reputation). IMO it's near useless now. If it was more frequented already approved publications with issues could actually be reported by enough members to produce an improved revision.
In case you're concerned that publications could get reported unjustified because in contrast to member-reports in Spam&Abuse there's less of a clear cut measure, the right to post in that forum could require an even higher reputation than to read it.
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
Even if it's multiple hours since the message was first posted. Bug or intended?
Sidenote: Not fixed for me: Firefox does not show format options again[^]
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
modified 3-Feb-16 9:46am.
|
|
|
|
|
It was removed a while ago, you get a note at the bottom of the body.
|
|
|
|
|
Alright.
(I reported this some months ago already and at that time Chris deemed it a bug and changed it back so I thought it might be a bug again.)
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
At the moment there are three categories for articles. Tips/tricks, Articles and Technical blogs.
Considering the way many articles are constructed, there's a category missing: Howtos and Walkthroughs.
Or are they belonging to Tips/tricks? Then it's time for a rename/redefinition, there are lots of Howtos that end up as articles just because of the length.
modified 2-Feb-16 9:36am.
|
|
|
|
|
I see the How-To and Walkthrough as Tip/Tricks and ask the users to consider changing the type.
If I get a "Why" it is long enough I answer...
Quote: A post can contain 2500 words but it still being a tip. I don't think it is a matter of length
The biggest difference for me is the learn effect. Let's suppose the same topic.
Option 1:
You just say click here, choose that, use this code, click there...
This is a tip, no matter how long.
Option 2:
You need to click here to choose the option X1, because that will set the property Y1 that you need to make Z1. If you prefer to do Z2, then you will need to use the property Y2. Once you have done this, you should see that... Once done with this you can use this code to implement the functionality XXX. The code itself will do YYYY (commenting things that are not obvious seeing the code). I made several tests before taking this approach, this was my best option because...
This would be an article.
I hope I could explain the differences in an easy way
.
M.D.V. 
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.
|
|
|
|
|
Have a 5 for that perfect explanation.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
From the Submit a new Article[^] page:
Quote: What is an Article?
An article is typically either a tutorial that allows someone to learn about a technique or technology, or an explanation and documentation for code that you are uploading. Articles outline the problem you're trying to solve, the techniques you're using, and a simple explanation of how to use your code or techniques. Interesting gotcha's or trivia are always welcome.
What is a Tip/Trick?
A tip has the same layout as a regular article but is meant primarily to provide a quick coding solution or tip. Tips and Tricks are not as exhaustive or extensive, nor do they require as much detail as an article to explain a problem and its solution. Articles may be several pages long, but a tip might be only a couple of paragraphs. Tips simply state a problem and a solution.
This probably needs to be boiled down to:
Quote: Articles provide a discussion on a problem or piece of code.
A tip simply state a problem and a solution.
It's not about the length of the article or tip. It's about the intent.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: It's not about the length of the article or tip. It's about the intent.
This is what I want to mean in my text. The most important aspect is how it is explained.
When I ask if they can consider a change I give the links to both definitions (Article/Tip) of the FAQ and additionally the Link to "how to change to a tip" from the FAQ too.
Quote: Have you consider to post this as a tip?
I think it would fit better that category. For more information about the types please read:
Code Project Article FAQ - Article[^]
Code Project Article FAQ - Tip[^]
If you need information about how to change your submission to a tip, please read:
Code Project Article FAQ - change to tip[^]
M.D.V.
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 have always found the name, Tip/Trick, a bit problematic as it's not really very descriptive of the intent.
"A tip simply state a problem and a solution" = Howto
And for the longer ones it becomes a Walkthrough.
So how about "Howtos and Walkthroughs"? Clear enough in itself?
Then make it default choice. So people need to actively choose to make it an article.
|
|
|
|
|
My issue with splitting articles into HowTos and WalkThroughs is that it'll never end. We'll need a category for Interview questions, Backgrounders, Components, Framework Intros etc etc. These are all articles. They all provide (except for interview questions, which personally I dislike) a discussion and education on a topic.
A Tip/Trick is meant to be a super-short "If you need to accomplish X, do Y". Wham, bam, thank you ma'am.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: It's not about the length of the article or tip. It's about the intent.
Chris Maunder wrote: A Tip/Trick is meant to be a super-short "If you need to accomplish X, do Y". Wham, bam, thank you ma'am.
Make up your mind will you. 
Anyway, I prefer your first definition.
I'm not really proposing more categories, I'm proposing a name change.
"If you need to accomplish X, do Y": That's a Howto.
I personally don't find that the plethora of walkthroughs we get as articles today qualify as articles. My 2c.
|
|
|
|
|
If it is we should keep reporting them, if not those with Protector status can just remove them on sight.
|
|
|
|
|
Articles go through moderation by default. So you can remove them if you are 100% sure it is Spam (e.g. Health,Baba etc). I talked to Admins on this. (AFAIK) Spam filter has nothing to do in case of Articles. Let's wait for Admins to respond.
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning
|
|
|
|
|
I delete them manually when I see it is still alive with 10+ reports.
M.D.V.
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.
|
|
|
|
|
The spam filter isn't being used on articles this very second - but that can change. Reporting them is not a bad thing since it means we can always go back and re-train the spam detector when we turn it back on.
cheers
Chris Maunder
|
|
|
|
|
Then I'll keep on reporting and follow Neleks example on removing.
|
|
|
|
|
Thank you, Jörgen. Your help in reporting and stamping out spam makes a difference.
cheers
Chris Maunder
|
|
|
|
|
Is it a problem to delete them when cache problems or so (report counter bigger than 10)?
Or better be patient and leave them alive until system nuke them?
M.D.V.
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.
|
|
|
|
|
At the end of each year I think it would be incredibly valuable to the community on Code Project if Code Project Collated all their Articles and those Articles' Code if {Applicable : Available} into one Downloadable File for a fee if necessary ($64.00 - and this money can be used to assist in funding the site)... Convert the HTML files into either an Open and Free Office Suite, PDF, or Something Else.
Have the Files sorted by their Programming Language.
|
|
|
|
|
Sorry, but it's not going to happen. The costs involved wouldn't be recovered, morally we'd have to talk to all authors of all articles to get their blessing, the demand simply would not be there given that you'd be asking someone to pay for what's already available for free, but the overwhelming issue is that articles live and grow. A snapshot means you don't get the latest updates, the latest comments, suggestions and bug fixes from the community, nor up to date ratings that help sort the wheat from the chaff.
cheers
Chris Maunder
|
|
|
|
|
Thanks for the response and talking about the logistics involved in such an endeavor.
|
|
|
|
|
That would make CodeProject lose their honor of free service because they would be selling their content at the end of the year, which can be read freely. This is one of the reasons I despise one service, SSWUG, they ask for a membership, but they are on the right path because they also pay their authors so asking for payments is not a bad thing.
The way I may have put it, would be to allow the articles of a category to be downloaded (no payments). The way CodeProject already has a "framework"-based learning portal. For example, for Android: Learn Android - CodeProject[^]. CodeProject can generate a link to create the PDF for the available content, like the best articles.
But putting a cost would be a bad UX for CodeProject and I am sure CodeProject won't like that to happen.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
