Jen Lampton's talk; thoughts on editor-related features

I haven't completely avoided being recorded, they got me at DrupalCamp Austin, and I've posted the video on my site incase anyone else is looking for a video also. (They also got the first few minutes of my presentation in Paris too, but this information is very out of date!)

To answer your questions:

1) Autosave isn't so much a WYSIWYG problem as a Drupal problem, and there's a module for that I haven't used it yet myself, but I'd start here.

2) My preference for TinyMCE is personal. I like it for several reasons: First, TinyMCE has a mature, thriving Open Source community of its own. Every time I've needed a plugin for something that wasn't already included (for example: a youtube button, spellchecking, or HTML templates) it's always already existed for the TinyMCE editor. TinyMCE also has really great documentation, something our community might learn something from :) WordPress also uses the TinyMCE Editor, and we can't ignore the amount of work that community is putting into the development and improvement of TinyMCE as well. I expect faster progress of TinyMCE because lots of people are using it, and lots of developers are working on it. There also seem to be a lot more plugins that are already included for TinyMCE. (You have access to these via the list on the WYSIWYG profile configuration screen.) The TinyMCE editor also integrates really well with the WYSIWYG module, I've run into problems using CKEditor when I needed to do things like allow HTML comments, but for TinyMCE that's as easy as checking a checkbox. My clients also prefer using the TinyMCE editor. No WYSIWYG editor is going to make creating tables in your content easy, but I find it less painful with TinyMCE than with others. One of my favorite modules for use with WYSIWYG is the caption_filter module, and what that module does (allow you to float the caption right or left along with the image) is technically impossible using the CKEditor. Because of this last limitation, I suspect TinyMCE will be the editor that gets into Drupal 8 core.

At the end of the day, everyone should choose the editor that's best for them, their clients, and their needs. If you prefer the CKEditor, or another, then by all means, do what makes you happiest :)

3) There are a lot of modules that can allow smaller images to enlarge, either on mouse-over or on click. My personal favorite is the colorbox module but there is a great comparison of all these modules if you'd like to find your own favorite. Most of these modules work nicely with WYSIWYG already, but some of them will require custom code (HTML, CSS, and sometimes jQuery) to work exactly how you want them to (for example, to get them to play nicely with insert module you often need to override the inserted image template file). Another note: If you configure the insert module to allow the original, or large-sized images to be inserted into the post and don't enable the image resize filter module, then you'll have very large images available in your HTML to manipulate in whatever other ways you see fit.

I'd love to hear what other people's favorites are, so if anyone else has an opinion, please post below!

http://wysiwyg.jenlampton.com will be back, as soon as I get some time. So, not this week ;)

I've just gone back to it and it's working.

I think the problem was that I hadn't put the path to the wysiwyg.css style sheet in correctly was trying to use %t. In stead I changed that to the full path from the drupal root: /sites/all/themes/mytheme/wysiwyg.css, but then forgot to clear all the caches.

--Chris