This means the plugin needs to be re-written to use v5’s API to function – and that will take time.Įven though that’s an issue, there’s also a silver lining.
I do use one third party plugin that provides its core functionality through an iframe. The biggest issue here is the last point – iframes. Iframe content within a Dialog is no longer supported
The API creates breaking changes – v4 to v5 is not a simple upgrade, and will (in most cases) require workĪdding custom icons is dramatically different, now referenced using SVGs rather than font icons However, while playing with v5 and specifically looking at Dialogs and Plugins, I found out a few key points: Its responsiveness and access on touch devices – be that a small screen phone or a larger tablet – is now feeling intuitive and natural on a mobile device. It has been great to see the evolution of mobile browser support and the user experience on these devices. The icons (as coloured images, aka old school Word) are long gone, and now have a very clean and simple interface. TinyMCE now feels modern and integrated in with the rest of the page’s interface. v3 to v4 really improved the user interface. I’ve spent a few days this week playing with the Release Candidate for TinyMCE 5, and specifically looking at how my old v3/v4 plugins can work within the new framework. Update the Dialog and its data dynamically after instantiationĪdding custom SVG icons for your Plugin's Button and Menu Item Make your Plugin have a Dialog using TinyMCE 5's UI components Get started with a basic TinyMCE 5 Plugin In this article, I'll be showing you how to: And it’s such a brilliant WYSIWYG editor. I’ve been using TinyMCE for years – I think if I look back in my code history, v2, maybe even v1. The included code also works with the TinyMCE 5 Stable release.
0 kommentar(er)
