Rich Text Editor #29
Comments
I'd be happy to start working on this component if it's still open? I was thinking TinyMCE might be the best option to wrap - it's the lightest in terms of bundle size of the options above, and has a fairly extensive API to get what we need from it :) |
@danielbollom the issues is all yours! I've assigned the issue to you. I look forward to reviewing the pull request! |
I agree that TinyMCE is the best choice for us. In its last version, it is easy to use and powerful enough to handle all of the our use cases. |
Hey guys! I was working on this one earlier and I was wondering which functionality/plugins would be required for the editor? I was thinking:
Is there anything else that would be useful to include? The list of TinyMCE plugins is here: https://www.tiny.cloud/docs-3x/reference/TinyMCE3x@Plugins/ And the list of buttons/controls is here: https://www.tiny.cloud/docs-3x/reference/buttons/ |
@danielbollom I think this is a sufficient list of features for now! |
I want to point out that we need an extra care on image embed feature. We don't really want to allow our users to embed patient images, MRIs and so on. The software will have already a place to store patient images. I think it would be nice to let them "include" an image in text: however also this could be problematic, since the images will be stored encrypted using pub/priv keys. |
@fox1t the default behaviour for tinyMCE gives the user an option to include a link to an image which is sets as the source for an image tag in the output. Would this be okay, or will it be easier to remove the image functionality for the moment? It's very straightforward to include/exclude at a later point if required. |
I think we can remove the image functionality for the moment. We will surely return to it in the near future. :) |
Sounds great! :) I should time to get a pull request ready for this one in a day or two 馃憤 |
# [0.18.0](v0.17.1...v0.18.0) (2019-11-21) ### Features * **richtext:** adds RichText component ([d541c93](d541c93)), closes [#29](#29) * **richtext:** fixes comments in Props to display in storybook ([fa1e526](fa1e526)), closes [#93](#93) * **richtext:** fixes default value for disabled prop ([587a493](587a493)), closes [#93](#93)
馃帀 This issue has been resolved in version 0.18.0 馃帀 The release is available on: Your semantic-release bot 馃摝馃殌 |
馃殌 Feature Proposal
Add a rich text editor as a component.
Motivation
Rich text editors are used when there is a need for formatted text content.
Example
Patient Notes
Relevant Links
The text was updated successfully, but these errors were encountered: