Minimal toolbar for TinyMCE 4
Cam Findlay
Public
Seen by 45
It looks like there's been some substantial progress on the effort to get TinyMCE 4 integrated into SS3, which is fantastic news. I'm wondering if we might also use this opportunity to reduce, drastically, the inventory of buttons in the toolbar that the default instance of HTMLEditorField gives you. For as long as I can remember, SilverStripe has thrown you the kitchen sink TinyMCE installation, sending users on a time warp to MS Word 2000 and overwhelming them with way too many options, more opportunities to break stuff, and a slower editor to boot.
Yes, there's an API for it, and I always make a point to create my own settings, but it seems like unnecessary boilerplate to me. The default case should not be the edge case. Tables, horizontal rules, and the seemingly redundant "cut and paste" options are decidedly an edge case IMO.
My ideal default TinyMCE would look a lot like the editor I'm typing into right now on Google.:
Paragraph/Heading, Bold, Italic, Link, Image, Media, lists, block quote, alignment.
What does everyone else think?
Poll Created Mon 14 Jul 2014 1:15AM
The default TinyMCE toolbar should only include a minimal set of features out of the box. Closed Tue 15 Jul 2014 5:09PM
TinyMCE should only include Paragraph/Heading, Bold, Italic, Link, Image, Media, lists, block quote, alignment. to begin with.
Results
| Results | Option | % of points | Voters | |
|---|---|---|---|---|
|
|
Agree | 100.0% | 2 |
|
| Abstain | 0.0% | 0 | ||
| Disagree | 0.0% | 0 | ||
| Block | 0.0% | 0 | ||
| Undecided | 0% | 36 |
|
2 of 38 people have participated (5%)
Cam Findlay
Mon 14 Jul 2014 4:28AM
I would say having a minimal set out of the box and then being able to add complexity as use case requires is a better approach. It is a bit like SilverStripe itself, less out of the box so you can build up what your client needs not tear down things
Poll Created Fri 18 Jul 2014 3:18AM
We should continue to use the custom SilverStripe media plugin for inserting media into TinyMCE Closed Fri 25 Jul 2014 5:10AM
Seems we agree and this makes sense given the decision over in https://www.loomio.org/d/f0TlKEBy/upgrade-tinymce-to-4-0 that we implement 4.x and continue to use our media insertion methods.
Rather than the built in TinyMCE one, or any of the plugin available with TinyMCE 4.x.
Results
| Results | Option | % of points | Voters | |
|---|---|---|---|---|
|
|
Agree | 84.6% | 11 |
|
| Abstain | 15.4% | 2 |
|
|
| Disagree | 0.0% | 0 | ||
| Block | 0.0% | 0 | ||
| Undecided | 0% | 25 |
|
13 of 38 people have participated (34%)
Sam Minnée
Fri 18 Jul 2014 3:32AM
The SilverStripe plugin is functionally rich and heavily integrated with our asset system. It would be nice to ensure that our pop-up was easily deployed to other WYSIWYG editors.
Gábor Novoszádi
Fri 18 Jul 2014 6:01AM
Integration with our asset system is very important.
Cam Findlay
Sat 19 Jul 2014 6:21AM
yip TinyMCE 4 seems to keep the UI out of the way until you need it via dropdowns. I also know I have had lots of requests from the community about "when are you going to add 4.x" so it's a yep from me.
James Cocker
Sat 19 Jul 2014 9:46AM
Definitely, the TinyMCE one requires several more steps when inserting a new image. I think the current SilverStripe one works very well (apart from editing captions, and changing image alignment for images with captions)
Nathan J. Brauer
Tue 22 Jul 2014 3:56AM
This is sort of a no-brainer. But it should have a UX overhaul.
Shaun De Greeff
Wed 23 Jul 2014 7:18AM
Would be good if we can add a field that allows you to add css directly to object before inserted. Example, i insert image and want to use .img-responsive css class....i cant currently add the class while inserting the media object
Cam Findlay · Mon 14 Jul 2014 4:26AM
@unclecheese I borrowed this as a test discussion from the dev list. What is your position on this?