Why not use composer-redactor as default editor?
-
@agusputra said:
I just hope that do not use plugin-markdown as the default editor.
It's fine as the default editor, just because you don't like it, and it's not popular in your country, doesn't mean everyone else should think the same way. The whole point of the composer being a plugin is you can change it yourself. Redactor was a paid for system donated by another user, which is still in active development.
And I think mostly forum users don't want to learn markdown, they just want to type the text.
Then how is BBCode a better alternative, I'd much rather do
> this is some quoted textthan[quote]this is some quoted text[/quote].The whole point of Markdown is you just type the text. BBCode is clunky and old, WYSIWYG looks good on the surface, but the code that gets spewed out behind it is usually absolutely disgusting to look at.
-
@agusputra said:
@a_5mith but for BBCode the users just need to remember element name
[b], [img] etc. And for markdown they need to remember various marks :*, **, ![](), #, etc
One could argue that BBCode is more obtuse and hard to learn, and that the only reason it is preferred is because it's simply been around longer.
I personally find
*italicised text*easier to understand vs[i]italicised text[/i].Also typing
[and/make my right hand all contorted. I've always hated that. -
Markdown is excellent for bloggers since they type a lot. Redactor is excellent for occasional posting for non-bloggers. I like Markdown but it is not for everyone since there is a learning curve.
I say give the user an option to choose either Markdown or Redactor in the user settings or as a cookie when replying to a post. It will not be for the admin to make the choice. It is for the end user.
-
I've always wondered why BBCode
[b][img][strong]is considered easier to learn than HTML<b><img><string>? -
Just to note here.
2 most reasons why I have migrated to NodeBB:
- Markdown
- NodeJs
-
Wonder why the thread went to markdown vs bbcode...
Redactor is WYSIWYG so better to focus on Markdown vs WYSIWYG
-
@agusputra The whole point of markdown is so you don't have to worry about resizing images. The CSS handles image size via the max-width attribute so it doesn't overspill the container. There's nothing to say you couldn't change that value to make images smaller though.
-
@henrywright It's not really. BBCode came about because forums didn't want people posting plain HTML (risky) so a separate language (Bulletin Board Code) was created to work like HTML but with the ability to sanitise all the input.
Logical at the time to replace <b>Text </b> with [b]Text [/b].
-
It would not be hard to add a plugin that could handle setting the size of an image manually, if it is really needed. I'd think it would be bad to manually size images inside of posts though, as it might break the responsiveness of it. The software should auto resize any images that are too big based on screen size.
-
So, what do you want? Do you want BBcode? Do you want Wysiwyg? Do you want more helper buttons?
-
Uh, so this topic has been beaten to death. @administrators I make a move to close
-
@agusputra I agree with your suggestion about helper buttons. The open source project Rocket Chat has an unobtrusive way of hinting basic Markdown syntax.
Simply a line of greyed text that becomes regular text on mouseover
It might be useful to have something like this at the bottom of the editor input field.
