[RFC] WYSIWYG editor

[callumacrae]

I prefer MarkDown to BBCode, and I've used both extensively (I've written documentation in MarkDown and my book in a form of MarkDown). BBCode makes more sense to people who know HTML, but the majority of users have no idea what HTML is.

*italic*, _underline_, **bold**, `inline code` is far more logical to me, especially when I think of it from the viewpoint of a non-developer.

There's an RFC somewhere (possibly made by me) which proposes allowing formatting systems such as BBCode, MarkDown, HTML-subsets to be switched in in something like an extension - obviously, the default install should always use BBCode.

[hanakin]

I would not say BBCODE is because of HTML knowledge as that would make no sense why would we not just use HTML other than security. I personally have switched to a static markdown system for my blog and love it, as it allows me to easily write content on my tablet or iphone and upload it later. Further more the inclusion of markdown would make the mobile version of the app a lot easier to work with as we can opt to not show the buttons for mobile editor thus freeing up room

[Pony99CA]

A configurable system supporting various markup languages would be best (if it can be done with little performance hit). If that can't be done, stick with BBCode as it's what most phpBB users (and, to some extent, vBulletin and other BBS users) know. Until somebody mentioned markdown here a year or two ago, I had never even heard of it. I don't believe that I've ever used a system that supported it.

Steve

[hanakin]

A configurable system supporting various markup languages would be best (if it can be done with little performance hit). If that can't be done, stick with BBCode as it's what most phpBB users (and, to some extent, vBulletin and other BBS users) know. Until somebody mentioned markdown here a year or two ago, I had never even heard of it. I don't believe that I've ever used a system that supported it.

Steve

Its what github uses for readme files/issues/comments!

[Arty]

phpBB is for everyone, not just coders. Users don't want to learn BBCode or markdown, they just want to be able to post. Markdown makes that very hard because it replaces certain sequences, so user might enter markup by mistake and mess up his post.

It is geek friendly, not user friendly and has no place on forum that is meant to be for everyone.

[keith10456]

phpBB is for everyone, not just coders. Users don't want to learn BBCode or markdown, they just want to be able to post...

Agreed

[Avdon]

phpBB is for everyone, not just coders. Users don't want to learn BBCode or markdown, they just want to be able to post...

Agreed

+1

[hanakin]

I see you point with layman use, but you could include an optional checkbox to parse as markdown which would drastically help those on tech related forums which is a probably the majority of the uses out their

[Ger]

phpBB is for everyone, not just coders. Users don't want to learn BBCode or markdown, they just want to be able to post. Markdown makes that very hard because it replaces certain sequences, so user might enter markup by mistake and mess up his post.

+1

[brunoais]

Allowing using Markdown (behind an option) seems fair to me.

As I'll be integrating textFormatter and SCE with phpBB, if someone does a plugin for Markdown on textFormatter and helps getting the markdown plugin ready on SCE, I'll do everything else that is required to create an option for Markdown after I finish the textFormatter and SCE integration which will, hopefully, happen until September. Well... I'll do every single thing I can to get TextFormatter working well on phpBB until mid August.