|
Code Project recognizes the value of language formatting inside of code blocks within articles. This improves readability, and provides a means for displaying the code as the language would be in its common environments. There are language formats available for common ones such as XML, C#, ASP.Net.
I think Code Project should also be a place to talk about lesser known or new technologies with an equal ability to present. For displaying these (or any) technologies in code blocks, there should be a way to perform custom highlighting if the highlighting rules do not fit a common one. Or is there already a way to do this?
Displaying uncommon highlighting via images is not the preferable approach, and apparently also not an accepted approach.
|
|
|
|
|
|
Hello,
I am currently writing an article, it is still marked as being composed (which is ok). However link to the article from "My Articles" points to older (out of date) revision of it. The page "Revisions" of it seem strange to me:
http://www.codeproject.com/script/Articles/ListVersions.aspx?aid=620045
I do not know who can access it as it is still marked as being composed. In the case you cannot, roughly something similar to this table is there:
Revision Minor Date Status Editor
=============================================================================
4 No 16-Jul-13 19:34 Draft Martin Mitáš
3 No 16-Jul-13 19:34 Composing Martin Mitáš
Updates in content. Changes: 268
current No 14-Jul-13 20:00 Composing Martin Mitáš
Updates in content. Changes: 15776
1 No 12-Jul-13 8:17 Composing Martin Mitáš <Rollback>
I am confused from it for several reasons:
- The newest revision 4 (draft) seems to be missing some content (screenshots) and I consider the revision 3 to be the most actual.
- I do not know how to delete the rev 4 without whole article.
- When I edit rev 3, the rev 4 is still there in the same incomplete state, with an updated timestamp.
- I do not understand why revision 2 keeps to be marked as current and how to change it.
- BTW, what the "Rollback" button does?
Probably I do something in a wrong way when composing a new article but I don't know what it is. Perhaps part of the mess is caused by the fact I do not understand the difference from "Save draft" and "Save this version" (when keeping the check "Work in progress: don't publish"). Is this explained somewhere?
(No the guide Guide really does not cover this sufficiently.)
Also I once accidentally published it (so the state was "pending") but changed it back to composing state fairly quickly. Perhaps it confused the CP.com's content system furthermore?
Any help or pointer to relevant documentation would be appreciated.
modified 19-Jul-13 10:51am.
|
|
|
|
|
Hi Martin,
I am worried that answering your questions in full and in succession might confuse you so I will simply say you cannot delete revisions, and Rollback allows you to rollback your current (possibly published) article to a previous version.
If you'd like, you can email me an HTML version of your final revision and I can apply it to your article so there are no mix-ups. Or deal with the article editor for you entirely. I'm happy to help.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
The source of my confusion, as I can see it now, is probably caused by a bug. The particular article has some mess in its history. I reported it by e-mail and also here: http://www.codeproject.com/Messages/4619265/Re-Table-borders-in-the-on-site-article-editor-bro.aspx[^]
To summarize:
(1) When it was yet in composing state, the page "Revisions" marked as "current" some relatively old version. Links to it (e.g. from "My articles") lead to the old one, being marked "current". Some revisions were not listed in the list.
(2) When it was eventually published, it somehow improved, but still some revisions are not listed, including the current published one. Also, somehow, I have not received 100 rep. points for publishing it. My guess is it is due to the metadata mess.
(3) I would like some admin to take and check and probably repair the metadata of the article to prevent some problems in future, e.g. if some new update to it is made.
(4) The very best thing what would happen is to find the bug which causes such problem and fix it, to avoid similar issues in the future, as I still have some plan to write few more articles.
|
|
|
|
|
Even with 10 million CPians what I write about is too niche to elicit constructive feedback so it's difficult to get better.
CP has a mentor program and what I'm wandering is would that be the way to go?
What are your experiences with mentoring? Is it relevant to my issue or only useful for beginners to get their HTML in order?
"The secret of happiness is freedom, and the secret of freedom, courage."
Thucydides (B.C. 460-400)
|
|
|
|
|
Matthew, I'm one of the mentors. We don't just offer advice about formatting. If you have specific things you'd like us to take a look at, drop Sean a line to ask the mentors to take a look and explain what you want us to concentrate on.
|
|
|
|
|
Thanks Pete, I'll talk to Sean as soon as I have publishable code to go with the next article.
It's a matter of trying to go in two directions at once, trying to make things more comprehensible to non experts and more useful/interesting to experts. One inclines to cover less ground more slowly and the other more ground at greater speed while a compromise pleases no one.
I have expert advice on writing style from my sister who's a freelance script editor but even she struggles to make any comment as she can't read 85% of any given article.
"The secret of happiness is freedom, and the secret of freedom, courage."
Thucydides (B.C. 460-400)
|
|
|
|
|
I just took a look at your first two QOR articles. Part I's introduction I found rather overdone, but the rest was interesting and well explained. Part II looked very well constructed and probably deserves some good votes, but you will probably only get them from anyone who is interested in the subject. To be honest, I found both of them more in the style of blogs than articles, and yes, the distinction is very subtle. If you want some ideas (pre-mentoring) on article structure then take a look at Pete's offerings[^], any of Sacha Barber's[^], and also FMBomb - A Beginner's Approach to Hardware Programming[^], which I think is a really excellent example.
Use the best guess
|
|
|
|
|
Thanks Richard. I'm aware these articles aren't going to garner a lot of interest and that's fine. The trick is to still get better at writing them which initially is easy, spot the mistakes in the first one, compare with a few good articles and do better next time. After that it becomes a lot more difficult to improve. I'll have a read of some of the those you've suggested and see what I can pick up.
I'd certainly be interested to know what distinguishes a blog style from an article style at that length? Perhaps I just read too much Raymond Chen 
"The secret of happiness is freedom, and the secret of freedom, courage."
Thucydides (B.C. 460-400)
|
|
|
|
|
It's really a question of structure and what the article is saying. Your introduction to QOR was a lot of Q&As, and while very useful was not really teaching the reader much. It was more a list of your observations about the overall project. I don't mean to be critical here because it was a well structured and informative piece, but at the end of it I would not be able to do much with QOR. Look at Sacha's Introduction to WPF, at the end of that you could create a simple program. I said it was subtle. 
Bottom line, I do hope you continue as you obviously have some good knowledge and skills. The key is not to be discouraged by a lack of feedback. And if you feel like being a bit cheeky you can always try a flagrant advertisement for your article in the Lounge - once, or as Pete suggests, ask for a mentor to look it over.
Use the best guess
|
|
|
|
|
Richard MacCutchan wrote: I don't mean to be critical here
By all means be critical, that's what I'm looking for. You're right of course, the intro article should have working Strata-1 source code with a working Tea For Two demo at the end. I have been too focused on trying to keep the code size down for each article to speed up the many iterations required to polish it for publication.
I'll have a rethink and work out a way I can make that happen. After 10 years I certainly won't be giving up.
Article-4 is mostly about AOP and is going to need to go through the mentor system I reckon. I at least need to be sure somebody understands what I'm talking about before unleashing it on the masses.
Thanks Richard.
"The secret of happiness is freedom, and the secret of freedom, courage."
Thucydides (B.C. 460-400)
|
|
|
|
|
Hi Guys,
what are the best picture editor , in which we can easily edit images , comment images and make them more attractive and understandable.
what you guys used to edit images ?????
|
|
|
|
|
That really depends on your experience. I use Photoshop and Fireworks, but I've had a lot of exposure to these tools and they may not be to your taste. Simple editing can easily be done in Paint.NET, and this might well be your best bet.
|
|
|
|
|
Simple Win32 Virus[^] seems to be more focussed on writing a virus than defeating it.
Use the best guess
|
|
|
|
|
I have deleted the article and sent a note to the author explaining why it was being deleted. I will be keeping an eye on him, and if he chooses to post material like this again, I will vote to have his account removed.
|
|
|
|
|
|
No problem morzel, I have fixed it.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Thanks 
|
|
|
|
|
A few weeks ago I posted some code to address one of the problems discussed here[^]. Based on the response from the OP, I decided to do a bit of research on the topic and was not able to find any working solution on the internet and I thought it might be worth writing it up a bit as I still have my original hack development files and had keep some notes on its evolution.
With the above stated, my question is: would an article on this code be a valid topic since I had previously posted it in a forum discussion?
I have written a draft, but have not yet posted through any of it through the article submission mechanism because I want to make sure that I don't violate any potential rules here concerning previously posted code.
Also, I am not sure if this would be considered an article or tip. My draft (still a work in progress) is available here.
Thanks for any feed back.
modified 9-Jul-13 23:44pm.
|
|
|
|
|
This isn't tip material. This is full article material (even if it's just short). This is a fascinating topic that really does deserve a good, solid explanation of the requirements being faced and the response to the common responses seen to a problem like this.
Please post it!
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Thanks Chris. I will keep working on it then.
I think I will delete the link to my draft then as I know that my writing deficiencies probably are glaring in that draft and I do not need to embarrass myself. 
Thanks again for the encouragement.
|
|
|
|
|
I'm plotting article 4 in my QOR series and I have a dilemma which amounts to should the article describe the library top down or bottom up.
In other words demos and usage first and then break down the details of how and why or theory and detailed design first building up to usage and demos at the end. Which would you as a developer prefer to read?
To give some context the Microsoft LOC counter calls it at 9833 lines, so a small library but it covers a lot of ground in terms of ideas and techniques. Some of the details are quite hairy but they may also be considered the interesting parts. PHDs have been awarded for less
"The secret of happiness is freedom, and the secret of freedom, courage."
Thucydides (B.C. 460-400)
|
|
|
|
|
My preference is always to be able to get up and running as soon as possible in order to see whather it suits what I need, and then I like to dig deeper. Starting with a broad overview and simple, specific starter cases keeps me engaged. Diving straight into the details means I lose sight of the forest for the trees.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Thanks Chris, your opinion as always outweighs a thousand others, especially when it's the only one.
It's working much better top down anyway so I might have this one done before Christmas.
"The secret of happiness is freedom, and the secret of freedom, courage."
Thucydides (B.C. 460-400)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
