“[Kroc:] ask all the text-editors to provide a browser plugin so I can add twenty buttons to NNF for “edit in x”.”
There are lots of options for this:
• Firefox: It’s All Text! (https://addons.mozilla.org/en-us/firefox/addon/its-all-text/)
• Safari: Saft (http://haoli.dnsalias.com/Saft/index.html)
• Chrome: 1) Edit with Emacs (https://chrome.google.com/webstore/detail/ljobjlafonikaiipfkggjbhkghgicgoh) and 2) TextareaConnect (https://chrome.google.com/webstore/detail/ooddekcmdpjicehjkgobdopbkgepmahj)
“[Wannes:] Post-preview is something that would make the people not read before they post […] I continually reread my post, I mostly don’t even post it, since it's not really contributing to the discussion.”
I’d like to argue previewing can help keep off-topic contributions away in exactly the way you mention. But only when it’s mandatory previewing.
I’ve seen some sites to this. In order to post anything you have to go through a preview first. This makes sure people see what they are posting before they post it and the idea behind it is for people to reread (or proofread) their copy one last time before putting it out there.
However good mandatory previewing might be, I will never want it to be part of forum software. Unless all topics turn into long form game ideas and “meditative topic”s it will only hinder the flow of information, especially for those who just want to leave a comment. People will simply learn not to reread and the effect will be negated.
“[Neolander:] HTML code being generated on the fly as the users clicks the blank post and starts to type?”
While good in theory there is no good way to do this. First there is the problem of not being able to style text and keep it editable in HTML. Many of the known WYSIWYG systems work around this by capturing your cursor position, keeping your actual typed text in a hidden textarea and display an iframe of generated HTML. Even though what this forum would use doesn’t even get close to the functionality they are offering the rendering system is the same crappy work-around.
If you just want to generate a live preview away from the message box (essentially showing everything that is written twice) this would be easier—not easy!—but also quite hindering. The browser will trigger redraws of the page all the time and your scrollbar is going to do little dances. Another problem with this is the parser Kroc wrote. Regular Expressions in Javascript aren’t documented very well. There are limitations, unsupported classes and references and even browser differences. To do the live parsing we would need AJAX that sends raw text to the server and retrieves the HTML output, eating bandwidth for every update.
“[Kroc:] Perhaps we should change the wording? :P I don’t like “submit”, it’s too scary looking.”
Maybe “Put this out there!” will get people thinking? :D