You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to see a new feature added which I cannot find in the provided documentation. This feature would be an export of the entire document in markdown format. This allows documents to be stored on SQL-type databases where special characters (like "'" and "{" or "}")are not allowed. Markdown text is usually plaintext in the CommonMark format.
While there is some implementation of markdown syntax it does not completely follow the CommonMark specifications. That should be a good design rule since other products have adopted it and are commonly used (e.g. Jopin, and This HTML issue editor).
It would also gender the question of whether or not there should be two modes: raw and display (or something similar) to allow viewing of the raw markdown text and the rendered RichText. One suggestion might be a radio button or a new tab widget with tabs for raw and rendered RichText. It could even be a splitter object with one side raw markdown text and the other the rendered RichText.
I recognize this adds some complexity to the code. But, the feature would be worth it in the end.
BTW, maybe not on this subject but, the examples do not use the Gluon JavaFX FXML structure. It would simplify the example code if the examples used FXML forms made with SceneBuilder. This would be the normal usage of JavaFX for a custom RichText editor like the Full Feature Example, rather than making everything from code...if I may make a strong suggestion.
The text was updated successfully, but these errors were encountered:
I would like to see a new feature added which I cannot find in the provided documentation. This feature would be an export of the entire document in markdown format. This allows documents to be stored on SQL-type databases where special characters (like "'" and "{" or "}")are not allowed. Markdown text is usually plaintext in the CommonMark format.
While there is some implementation of markdown syntax it does not completely follow the CommonMark specifications. That should be a good design rule since other products have adopted it and are commonly used (e.g. Jopin, and This HTML issue editor).
It would also gender the question of whether or not there should be two modes: raw and display (or something similar) to allow viewing of the raw markdown text and the rendered RichText. One suggestion might be a radio button or a new tab widget with tabs for raw and rendered RichText. It could even be a splitter object with one side raw markdown text and the other the rendered RichText.
I recognize this adds some complexity to the code. But, the feature would be worth it in the end.
BTW, maybe not on this subject but, the examples do not use the Gluon JavaFX FXML structure. It would simplify the example code if the examples used FXML forms made with SceneBuilder. This would be the normal usage of JavaFX for a custom RichText editor like the Full Feature Example, rather than making everything from code...if I may make a strong suggestion.
The text was updated successfully, but these errors were encountered: