|
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)
|
|
|
|
|
Please see this http://www.codeproject.com/script/Articles/ViewDownloads.aspx?aid=605568[^]
In browse code, I find a demo app called "Facebook Login Logout". My tip was about CSS and I clearly remember not to have uploaded any source code. But today when I went there back to add some stuff, I caught sight of this. This is completely unrelated to my article and how did that land up here... I'm out of ideas. And yes, editing set to "Admin Only".
Should I trash it?
Beauty cannot be defined by abscissas and ordinates; neither are circles and ellipses created by their geometrical formulas.
Source
|
|
|
|
|
I want to writing a article named "Mimic-ing drag-drop in MDI Form". But someone has writing about creating MDI Form. Can I continue writing article?
Buiding Picture.
==-------------------------------------- 5%
Estimated tinme 2 days.
|
|
|
|
|
If your article explains some new and useful features that are not in the existing one then I would say, yes give it a go. Once you publish it you will get some feedback on how well people like it.
Use the best guess
|
|
|
|
|
This is something not so strange, there are many articles based on previous ones
My first and only article is an extension of other article. I used the template there but I was missing some options, so I programed them and publish an article.
Important is:
- Give credit to the original author by telling it and posting a Link to the original / base article.
You can check mine if you want, it might give you an idea on what I am saying
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.
|
|
|
|
|
Hi,
I want to update my Source Code version.
Barcode Label Designer C# in Windows Forms[^]
When i click the update button and looking for add Source code and upload button both are missing ,how to update my article source code.
Syed Shanu
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
