The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Only generally in "boring" text boxes: as soon as you start formatting stuff spell check goes out the window.
In fact, even in multiline textboxes, Chrome loses spell check half the time when I paste HTML into a CP box (like this one)
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Start with everything you want to talk about, put it into an outline of topics/sub-topics.
Start writing either linearly or the parts that you're drawn to first.
As you're writing, update the outline and see how things begin to evolve -- is it getting too long, is there a natural break for a couple articles evolving? Prune stuff that becomes irrelevant or you don't want to deal with.
Should I use the online editor
No - although it's evolved a lot, like being able to save drafts, I find online editing of anything to be a PITA, with the exception of lounge posts, haha. I'm an old fart, so believe it or not, I'm still using FrontPage 2003 for editing. Find a decent HTML editor (harder than it looks, maybe someone can make some recommendations here) that can let you do a split screen of the markup and the WYSIWYG. Write it all offline.
Hint to save you pain: images go in the same folder as wherever your "article.html" is, as image references in CP are now (and have been for quite a while, but it was not always so) "local".
Main topic headers are H2
Use bold and italic sparingly
variable names, methods, etc., in the text should be wrapped with code tags
code blocks are wrapped in pre tags
watch your image size, CP likes images no bigger than, um, 600 width (I think) which I violate constantly. One cool technique for really big images is to put upload both a small and a 100% image, and add a link to the 100% image, like "click here for full size image."
Personally, I like small code blocks. Don't throw a 500 line class at me, break it into individual method code blocks, in between explain what each method does and why (why is sooo important), etc.
Something I've seen people start doing which I really like is a section at the top of the article on "what you will learn", which is cool, because even if I have no interest in a C-like <1% parser, I might be really interested in how EBNF works and other cool geeky things you are covering.
Something I've seen people start doing which I really like is a section at the top of the article on "what you will learn",
A very good tip. The main Thing should be to Point out the way from EBNF to Wizard and how "intermediate" results of this are connected to the Parser stuff. While writing just the sentence before, I have a Feeling that one of the bigger problems will be my english.
What do you think about this Basic layout for the article:
^What you will learn
^What is a Parser
^What is EBNF (Extended Backus–Naur form)
^EBNF to data structure
^From EBNF to wizard
^Using the code
This article tries to point out how a simple programming language can be defined by a meta language like EBNF (Extended Backus–Naur form) and how a parser and - the main aspect here- a wizard can be build based on such a meta definition.
No problem. The outline is great. Something my readers have commented that they liked, which you elude to with the section on "some notes about the code" is some light (and lighthearted) discussion of the compromises, rabbit holes, and other things I did (including the wrong ones) that I discovered along the way.
BTW, if you'd like me to proofread anything (regarding your concern about English) I'd be happy to offer my editing services.
Also, there's this Table of Contents generator that I use for large articles. It has a couple bugs (no symbols in the headers, and popping two levels breaks further link generation) but otherwise it's a solid tool and there's some comments about how to fix those bugs in the article itself.
I really appreciate to accept your offer, I allready ask @OriginalGriff to help me on this. Maybe another expirience for me to see the differences between britan and us english... I assume I will see similar (but hopefully easier differences) things compared to when I have to translate EU-Spanish to Argentina/Colombia/Equador/Salvador/Equador/Honduras
You might want to try CodeProject.Show, an offline article writer for CodeProject developed by Anele Mbanga. The link is to the CodeProject article which includes source code and installer for the Show app.
In Anele's words,
The purpose of this article is to introduce CodeProject.Show, an offline CodeProject article writer. CodeProject.Show has been developed using WinForms, ICSharp.TextEditor and the Webbrowser control using VB.Net. I started developing this five days ago to enable me to write my CodeProject articles offline. This was due to internet connectivity issues at times being erratic and also me loosing an article due to these internet challenges. I also wanted to ensure that I kept track of my articles and are able to update them in one place.
Strange. It says "professional", but it really doesn't sound like that...
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - I'd just like a chance to prove that money can't make me happy. Me, all the time
Initially I was dismayed to discover that some members here knew that Maunder had inflicted us with My Little Ponies avatars. But now I understand some of these members know the names of said Ponies.
I thought Maunder had just ran some of his selfies through a Meme generator.
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004