I think that Markdown is bad. I mean, the quote looks like tumblr's quotes. It's from emails not writing out paragraphs from a RP. I hope that BBcode is coming soon so that I can say goodbye to Markdown.

Turns out the BBCode story for server-side Javascript is kinda pitiful. - I evaluated Redactor (<http://imperavi.com/redactor/>), but it's just not going to work since people want more than just formatted text. I can't easily extend raw HTML with things like hider tags without forcing the user to ultimately be able to edit HTML. <div class="hider" name="My Hider">My Secrets</div> Can't quite get behind that. I burned an entire day trying to make it work, but it's just not pretty for the end user. - I tried SCEditor (<http://www.sceditor.com/>) which I really liked. Easy for me to extend. I even extended it with some cool BBCode components to see how easy it was: [hider=My Hider]My Secrets[/hider] [tabs] [tab=Intro] This is the intro [/tab] [tab=Conclusion] This is how it all ends [/tab] [/tabs] ...But there is no straightforward way to use its parser to also do the BBCode->HTML render on the server. So far I'm experimenting with extending an open-source javascript BBCode library. It hasn't been maintained in a long time, but I'm having decent progress with it. I may be able to use SCEditor and then keep SCEditor's BBCode parser in sync with my server-side BBCode parser. I'm sure doing a lot of spelunking down rabbit holes. :)

That's unfortunate... Maybe someone here on the guild has any recommendations for usable systems that can do the right job? Oh, and were there any goblins down those rabbit holes?

Lots of goblins down these rabbit holes. Been feasting on them to stay alive. Also passed by Jon Krakauer's corpse.

Oh. You've been going down those temporal rabbit holes... You see this guy down there? We've been lookin' for him almost everywhere... 

Been making progress extending a parser:  It's actually looking promising.

> Lots of goblins down these rabbit holes. Been feasting on them to stay alive. > > Also passed by Jon Krakauer's corpse. You are assuring that you're taking enough time off, right? The last thing any of us need is for you to burn yourself out.

> Been making progress extending a parser: > > (insert something awesome here) > > It's actually looking promising. Soon™

Ooh... Shiney! That looks very nice.

I greatly appreciate the effort being put into this Mahz.

Got it working with the editor:  Though I'm just going to remove all the buttons except for the "Preview" button at the beginning and add them back later once I write the code to hook them up to BBCode.  I'll push my progress to the dev server when I hit a certain milestone.

Looking good Mahz! I'm excited to the progress you will make on this.

> Got it working with the editor: > > <snip> > > Though I'm just going to remove all the buttons except for the "Preview" button at the beginning and add them back later once I write the code to hook them up to BBCode. > > <snip> > > I'll push my progress to the dev server when I hit a certain milestone. Bye, bye, buttons.

Interesting. So, from the images, you're also working on a system to make custom tabs fit within posts? That could make for some fascinating applications. But yeah, I agree with LegendBegins. Don't burn yourself out.

Uhh... The rest of the formatting can wait, but single line breaks? Please? I have IC posts to write...

> Uhh... The rest of the formatting can wait, but single line breaks? Please? I have IC posts to write... Is it really so bad to just use a double line break while we wait? No offense, but I don't think the world will end if you have to write a post with a few empty lines, which you can remove once it has been fixed.

I tend to be rather particular about this one specific thing, yes. Especially since my posts tend to average several thousand words in length and thusly contain quite a few paragraphs each (worst of all is when people write rapid-pace dialogue with double line breaks after each sentence - I have a rather hard time reading those straight since I keep losing my track and skipping over lines). We don't need a thousand fancy formatting options before the most basic things possible are available.

> I tend to be rather particular about this one specific thing, yes. Especially since my posts tend to average several thousand words in length and thusly contain quite a few paragraphs each (worst of all is when people write rapid-pace dialogue with double line breaks after each sentence - I have a rather hard time reading those straight since I keep losing my track and skipping over lines). We don't need a thousand fancy formatting options before the most basic things possible are available. Trust me, we understand. Getting the formatting done is job #1 right now, and I know it sounds like a terrible cliche at this point, but we're just asking for patience. I apologize for the inconvenience.

> I tend to be rather particular about this one specific thing, yes. Especially since my posts tend to average several thousand words in length and thusly contain quite a few paragraphs each (worst of all is when people write rapid-pace dialogue with double line breaks after each sentence - I have a rather hard time reading those straight since I keep losing my track and skipping over lines). We don't need a thousand fancy formatting options before the most basic things possible are available. The single like break issue is because of Markdown. When he has finished implementing the BBCode parser, Markdown will be removed. Thus, your single line breaks will be restored. So again, perhaps you can survive with double line breaks while he finishes implementing? EDIT: with a bit of googling, it turns out that you can use single line breaks by adding two spaces to the end of the line, then moving to the new line. Example: New line! [Source](http://meta.stackexchange.com/questions/26011/should-the-markdown-renderer-treat-a-single-line-break-as-br)

> The single like break issue is because of Markdown. When he has finished implementing the BBCode parser, Markdown will be removed. Thus, your single line breaks will be restored. > > So again, perhaps you can survive with double line breaks while he finishes implementing? > > EDIT: with a bit of googling, it turns out that you can use single line breaks by adding two spaces to the end of the line, then moving to the new line. > > Example: > New line! > > [Source](http://meta.stackexchange.com/questions/26011/should-the-markdown-renderer-treat-a-single-line-break-as-br) Oh This is a great find! Ty so much --- I think I can fare without buttons for awhile. As long as it's for the editor being fixed! :D