|
... but the navigation links at the top of the lounge have a space missing. FirstPrev Next.
They still work fine, but next time someone is ferreting about in there?
FF4.0 - XP SP3
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
I wouldn't let CG touch my Abacus!
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
|
|
|
|
|
Yeah, but that's only true on the first page. (And, in fact, the same for this forum). So it's sort of like a double indicator that First==Prev.
|
|
|
|
|
Never considered that.
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
I wouldn't let CG touch my Abacus!
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
|
|
|
|
|
Henry Minute wrote: They still work fine
Not so, the FirstPrev Siamese twins aren't functional at all. All kinds of browsers.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
I wouldn't let CG touch my Abacus!
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
|
|
|
|
|
Fixed - thanks
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I know this is the third thread about it, but they really do need to be put back into their own tabs again. I was perusing the latest "Articles" and went on a 1-voting spree because all of the "articles" were too short and had no source download. By the time I reached thabout the 20th "article by the same author, I realized they were *BLOG ENTRIES*! I had to go back and unvote on all of his stuff.
This really is a change for the worse, guys.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
You found a way to unvote? I'd like to know how that goes... (in fact I would like to have a way to undo every voting, bookmarking, moderating, and maybe even reporting action).
PS: I agree.
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
Deleting your "Reason for my Vote of 1" message also deletes the vote itself (at least I think it does).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Yes, that should work as your vote pertains to some article/tip/blog but is associated with your message, which you can delete as long as it is a leaf message. Under most circumstances the vote/bookmark/moderation is associated with something you can't delete...
Luc Pattyn [Forum Guidelines] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at the code.
|
|
|
|
|
I don't think it does that. If you don't want to vote a 5, vote a 3. That will at least remove the down vote.
|
|
|
|
|
For me, the bigger problem (that I've already communicated) is the fact that proper articles will now suffer from a visibility perspective. I mean, it sucks that I can spend 2 weeks on an article only for it to be blown off the front page by someone blogging about the release of a new service pack for visual studio (which probably took him 10 minutes). Not trying to say all blogs suck, but the nature of blogs is different from that of articles.
[made a typo fix]
|
|
|
|
|
You have absolutely right.
I'm thinking about my next article, but now I have some doubts:
- How may time should I spend for it?
- Which is the best place to address my readers?
I don't spend days (or even weeks) in an article, for such a small presentation time slot.
In my opinion changes like this increase the content quantity, but decrease the overall quality. That's a pity.
That's maybe also a problem of a big community like Code Project. It's a challenge to provide such different information, from a Tip to an in-depth article, and satisfying all stakeholders.
|
|
|
|
|
I don't see how the duration of or manner in which an article is displayed on the front page would have any relationship to the amount of time you spend writing an article, or how much effort you put into it in terms of quality.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
I write articles to support so much people as possible. And Code Project is the optimal platform to do it.
The front page it's the best place to announce an article, which can be measured by the view counter.
This applies to the 'Articles' section and during the first two weeks, also for the 'Latest Best Picks' section.
So, for me it's a question of relationship between 'how much to investigate' vs. 'how much is the benefit for the community'.
|
|
|
|
|
It *should* be about writing the best article you can, regardless of how visible it is on the front page. That was my point.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
John Simmons / outlaw programmer wrote: I don't see how the duration of or manner in which an article is displayed on
the front page would have any relationship to the amount of time you spend
writing an article, or how much effort you put into it in terms of quality.
Peer feedback and visibility. You can't get those if your article goes off the front page in less than an hour. So there's not much incentive anymore to posting a high effort article here.
The workarounds I see are to blog about the article on your personal blog and to get friends to pass along links to other folks. That seems to be the only way these days to get some page hits and feedback.
|
|
|
|
|
Nishant Sivakumar wrote: You can't get those if your article goes off the front page in less than an hour
I apologise but I'm going to have to bring in some facts that may, unfortunately, ruin a good argument 
Over the last 7 days, 61 standard articles and 31 technical blog articles have been published. With a tab just for articles this means an article stays on the homepage a little over a day.
If we combine articles and blogs we have one item per 1.8hrs being posted, so after 18 hrs an item will fall off the front page, given 10 items and a combined tab. That's a little more than "less than an hour".
I've increased the front page count to 15, an increase of 50%, which balances out nicely the addition of 50% more items with the inclusion of technical blogs into the tab.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Jani Giannoudis wrote: In my opinion changes like this increase the content quantity, but decrease the
overall quality.
Yeah, that's what I see happening too.
Jani Giannoudis wrote: I don't spend days (or even weeks) in an article, for such a small presentation
time slot.
I hear you.
|
|
|
|
|
Nishant Sivakumar wrote: someone blogging about the release of a new service pack for visual studio
Apart from volume of new entries issue that has been raised, an important point is that a Technical blog is meant to be an article that provides the same level of value as an article. A "did you know..." type entry simply isn't to the level that should be accepted.
The issue in this very specific case isn't that an article gets blown off, but that blogs are being inappropriately approved.
So: two problems, not just one
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
So do the rep points reflect that "equal value"? I don't think they are of equal value because a blog isn't written specifically *for* CodeProject (unlike articles that are posted here). I spend days and sometimes WEEKS on an article, and it kinda twists me up to know that mere blog entries are considered to be "equal" in any way to an article.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
modified on Sunday, May 1, 2011 9:34 AM
|
|
|
|
|
Chris Maunder wrote: So: two problems, not just one
Great!
|
|
|
|
|
In my opinion several layout enhancement would eliminate this problem:
1) Move the 'Featured Article' box to the right pane
2) Compact the item entry
- Icon for new/updated
- Icon for the topics type: MFC/C++/C#/VB.NET/Mobile/ASP.NET/SQL/Architect/Java/LAMP/Tech Lead
- Compact the update time
- Move the additional item tags into the article tool-tip
3) New box below the articles with two columns: Technical Blog and Tip/Trick
|
|
|
|
|
This has been done.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
