With the introduction of image support in Design Mode (#100) it makes sense to add features to easily extract images and/or upload them, automatically dispose of images in memory when no longer needed, and to allow for more customizations to the editor (e.g. enable/disable individual plugins and buttons). We therefore need to move "Design Mode" into a separate control to avoid polluting the Input control with HTML editor specific features.
Suggestions for control names:
RichInput or RichEditor
HtmlInput or HtmlEditor
Ideas for additional new features:
HTML Table support
Inline editor / floating toolbar
TBD: Preserve support for Input.DesignMode(..) for backward compatibility ?
It would probably need to create an instance of the new HTML editor control and mount it within Input's DOM container, and then map relevant functions such as Input.Value(..) and Input.OnChange(..) etc. to HtmlEditor.Value(..) and HtmlEditor.OnChange(..). It seems like a lot of work, rather than merely having to create an instance of a new control. But it would be a breaking change.
With the introduction of image support in Design Mode (#100) it makes sense to add features to easily extract images and/or upload them, automatically dispose of images in memory when no longer needed, and to allow for more customizations to the editor (e.g. enable/disable individual plugins and buttons). We therefore need to move "Design Mode" into a separate control to avoid polluting the Input control with HTML editor specific features.
Suggestions for control names:
Ideas for additional new features:
TBD: Preserve support for Input.DesignMode(..) for backward compatibility ? It would probably need to create an instance of the new HTML editor control and mount it within Input's DOM container, and then map relevant functions such as Input.Value(..) and Input.OnChange(..) etc. to HtmlEditor.Value(..) and HtmlEditor.OnChange(..). It seems like a lot of work, rather than merely having to create an instance of a new control. But it would be a breaking change.