The most weakest point of nodebb
-
@julian said in The most weakest point of nodebb:
We have the Redactor editor for those kinds of users
Problem with redactor is you lose all other plugins that interact with the composer
No polls
No canned responses
No spoiler
No calendar
No question and aswer
No color
Etc -
@exodo I think some of those do work with redactor, actually.
-
@PitaJ said in The most weakest point of nodebb:
@exodo I think some of those do work with redactor, actually.
Dont think so. Did a test lat week while addind emoji support back to redactor
-
What do you guys think about having that thing where every joining member has to read and agree to a code of conduct, a "sticky" as it were. And in it would be things like, be nice, don't harass people, don't complain about the editor, etc. etc...
(For context, @nodeber this is the 3rd time it's been brought up)
-
@Bri haha
-
@Bri I think you misunderstand them. They want to be able to have users switch between composers.
-
@Schamper had mentioned it briefly a while ago. An API or abstraction layer, like we have for the databases, might be a nice feature for the composer module. So that plugins that are compatible with one editor would be 99% compatible with the other, without developer intervention.
-
@yariplus said in The most weakest point of nodebb:
@Schamper had mentioned it briefly a while ago. An API or abstraction layer, like we have for the databases, might be a nice feature for the composer module. So that plugins that are compatible with one editor would be 99% compatible with the other, without developer intervention.
Agree. That's best solution
-
Switching editors is not possible, since we save raw data into the database, that is, we save raw markdown in the case of the default composer, and html in the case of redactor.
They are incompatible and do not translate well between each other.
-
@julian also, editing a post submitted with markdown wouldn't work well with redactor and vice versa.
-
@PitaJ said in The most weakest point of nodebb:
@julian also, editing a post submitted with markdown wouldn't work well with redactor and vice versa.
I didnt have problem with editing md post on redactor i think
-
@julian said in The most weakest point of nodebb:
Switching editors is not possible, since we save raw data into the database, that is, we save raw markdown in the case of the default composer, and html in the case of redactor.
They are incompatible and do not translate well between each other.
I dont think the option to user-select is that important
Is more imporant making both composer not plugin dependant like default composer already is
Doubt anyone would choose redactor and lose polls, and all others plugins for his community -
@exodo redactor doesn't have a live preview for markdown. Besides, it's mostly trying to edit redactor output with the markdown editor that's the issue. If redactor could output markdown, that might work, but then other things like bbcode, etc would break.
But yes, I agree that there should be an agnostic composer API.
-
Yes, I second this.
As a developer, I love MD as it is pretty easy to use once you master it. However, the layman out there are not familiar with MD.
As such, I support the notion that the stock editor should be WYSIWYG instead of markdown.
