|
Which Tip? Sean or I will massage it.
If you hit the "<>" icon on the editor toolbar you switch to HTML mode which allows you to enter the HTML directly. If that doesn't help then an option is I could add a Markdown-style mode that allows you to type the content in as you used to, and have the editor switch to proper HTML on the fly. This, however, is tricky since switching from well-formed HTML to Markdown (or the plain-text-with-HTML isn't reliable.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Thanks for the offer, but now that I know about <> I will have a go myself - that way if I need to help someone, at least I have a better idea what they are going through.
It's more that if I have problems, then a beginner who isn't at all sure what he is doing anyway is likely to get discouraged with the whole idea. What I have at the moment looks fine on screen - until I press the preview or the <> in which case it is pretty obvious there are problems. If you show someone what looks like WYSIWYG then they are going to expect to G what they S! 
Is this a case of "too much pretty, not enough usability"? Was there a real problem with the separate HTML / preview modes we get with messages?
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
Chris, can you move this thread to the Mentoring forum?
I have a feeling that it's going to get a bit long, as either I'm doing things very, very wrong, or there are real problems with the Tip submissions process. I'd like to try explaining what I am doing, and what I get as a result.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
Don't move it - I found a work-around.
Go into HTML mode with <> add the pre tags manually, specifying the language yourself.
Then paste your code inside the block.
The display looks wrong as the syntax colourizer isn't activated, but the preview will include it.
This needs fixing, lots - if looks like the colourizer is kicking in and then the formatter:
Create a tip with the submissions wizard.
Fill in the name, and all the other necessary gubbins - that works fine.
Now, edit the main block of your text so that you have your Tip in English, with no code or supporting stuff.
Use <> and Preview - it's fine.
Go to VS, and highlight your method. Copy it to the clipboard.
Go back to the submissions wizard, and put the cursor where you want your method.
Paste!
Looks good! (It doesn't look like the example in the submissions wizard, but you have deleted that by now so who cares?)
Preview.
O
M
G
You can't see the code for a sea of on-screen HTML.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
Chris, thanks for your earlier explanation of why comments are associated with specific revisions of an article:
http://www.codeproject.com/Messages/4184889/Are-comments-specific-to-an-article-revision.aspx[^]
However, whilst the intention is that comments relating to article quality, whilst it is in the review process, do not make it through to the final - published article. It looks like this doesn't really work in practice!
I spotted a typo on my recently published article, which is now awaiting moderation, and as a result have a number of 'my vote of 5' style comments here:
http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=506455#_comments[^]
and here:
http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=505884#_comments[^]
and of course, here, in the right place:
Plotting Circular Relationship Graphs with Silverlight
I have never spotted this problem before, so I am guessing this is a new feature? Also, I am pretty sure that in the past minor modifications that I made to an article did not require moderation.
Can I suggest that it is made much more obvious that comments on an article which is awaiting moderation are specifically for the purpose of flagging quality issues? This might be quite hard to do with the way that it is currently set up because it is presented in exactly the same way as the regular article commenting mechanism, so I suspect regulars would just go into 'auto-pilot'.
(Any chance the messages on my article revisions could be moved to the main article? - id this is a big deal, don;t worry about it)
Regards, Colin E.
modified 9-Mar-12 9:37am.
|
|
|
|
|
To my mind, this is a fairly major SNAFU. When I review an article, I like to see all the comments - somebody may have posted a particularly useful snippet against an earlier revision which I would miss if I were looking at a later version. This cannot be right.
While it may be useful to indicate that a message applied to an earlier revision of the article, it should not disappear.
|
|
|
|
|
Thanks Pete, I am glad you concur.
Pete O'Hanlon wrote: While it may be useful to indicate that a message applied to an earlier revision of the article, it should not disappear.
It's worse than that! Messages on future revisions (i.e. new revisions awaiting moderation) do not appear either. I do wonder what will happen when the pending future revision is accepted. Where will those comments go?!!
Anyhow, at least it is not just me being over-eager to get a high comment count on my article for the sake of inflating my ego.
of course not.
I'm very modest I am.
|
|
|
|
|
Colin Eberhardt wrote: It's worse than that! Messages on future revisions (i.e. new revisions awaiting moderation) do not appear either. I do wonder what will happen when the pending future revision is accepted. Where will those comments go?!!
I think I just found out, it looks like the comments do not make it into the published version when the new revision is approved. However, you can see them if you access the article by version number - even though this version is the current:
http://www.codeproject.com/script/Articles/ArticleVersion.aspx?aid=342715&av=506455#_comments[^]
Anywho - enough said. I'll leave this to the CodeProject peeps.
|
|
|
|
|
|
Go. Get sleep. Speak after the weekend.
|
|
|
|
|
Thanks Chris - that's an improvement. We'll see whether that fixes it. I have another article I am about to write up, so I'll so if this problem crops up again. Nice work 
Would be good if you could move those comments, but only if it is not too much hassle, I am sure you have a lot of other things to do.
And like Pete says - get some sleep!
|
|
|
|
|
All done.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
|
Hello,
when I open my account at Code Project, and access my home page, I get the opportunity to see all the answers I gave, my sent messages, etc..
Now for example when I select the answer that I gave 15 days ago( or 3 months ), and I update my answer it happens that the answer and whole question appears in the forum as if someone had asked that question again, is there a way to prevent that and only the person who asked the question see my updated answer for outdated questions.
All the best,
Perić Željko
-- modified 9-Mar-12 4:41am.
|
|
|
|
|
If you update an answer then we consider that there has been activity on a question. By default we list questions in descending order of activity. The tabs on the Quick Answers homepage allows you to choose different views.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
|
It really is quite difficult for someone new to find (come across!) the way to navigate message-room entries.
I refer to this:
"Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages."
Yes, it's hidden at the foot of pages like http://www.codeproject.com/Forums/1645/Site-Bugs-Suggestions.aspx[^], but not at all explicitly obvious to one entering the 'forum'.
I managed to forget since my last visit (why should I have to remember? I have enough things to do), and it took me an age to find it again.
At the very least, "navigating entries" could be an item in Help.
You could even put it above the chosen format selector, where it would be obvious.
Then it would save me from rsi & not overload my brain.
|
|
|
|
|
It's just a quick key reminder - you can always do things the old way and click with a mouse...
They only have a certain amount of screen real estate - I for one am happier with the content taking precedence when the page loads and the hints left to the bottom where I can scroll to them if I need them.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
|
Yes, comments are tied to specific versions in order to allow members to post comments while author's fine tune their article during the composition and approval process.
An example is that you post a new article and it's in a Pending state while members approve it. A few members find fault with it, and you make those corrections, and then the article is approved. The comments related to corrections should not be included in the final published version of the article.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
|
This error can be reliably reproduced by trying to preview a message that only has newlines in it.
|
|
|
|
|
This is in the forums, right, with "live preview" disabled in your settings?
I can replicate. I've tried. Lord knows I've tried. Even the error logs aren't showing anything.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
It's in the live preview, sorry..
|
|
|
|
|
Try as I may I can't reproduce this. 
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
