Hey, sorry if there is a post somewhere that describers this but i couldn't see it (likely should be on project page??).
What is the value that the wysiwyg module provides for us over a solution like the fck module paired with fck?
We have a large publishing system that currently uses the combination of Dr5, TinyMCE module and TinyMCE. We are beginning work to convert this system of around 160 modules over to Dr6 and i have come across the dilemma that the TinyMCE module has been deprecated and we are trying to sort out which way to go as far as a WYSIWYG editor.
My guess would be that it simply allows for better integration of editors into drupal so that we don't require individual modules for each editor (like the fck module project).
Another way to ask this is what is the advantage of one of these over the other:
tinymce module + tinymce = module is deprecated
wysiwyg module + tinymce = should let us use existing tiny apps
fckeditor module + fck = one alternative
wysiwyg module + fck = yet another alternative
And, on a slightly different; but basically the same topic, as part of this system we have a couple d.o projects of custom modules that were designed to work with Tiny:
Autosave: - d.o project that provides background saving of a document in case browser dies
Wordcount - provides a running character and word count window in the tiny menu bar
Should these now be integrated into the wysiwyg module? If they were do we think we'd get global support for the various editors to use the modules? I think there is code in each of these that may be specific to the Tiny editor which means our addon modules still need to be designed for each editor individually - which again raises the question of what is the value of the wysiwyg module.
Peter Lindstrom
LiquidCMS - Content Solution Experts
Comments
Long story short: Wysiwyg
Long story short: Wysiwyg module is the future. It replaces all other editor integration modules.
My viewpoint, as a user, not a developer on this project
The wysiwyg module promise to solve the current administrator dilemma: Which editor to use?
Why is it a dilemma? Well, you point it out yourself, some modules are made for one specific editor, you mention two yourself specifically for tinymce. There are others which works only with a specific editor, one I personally is looking forward to is linodef. It is promised to become a wysiwyg compatible plugin instead of a BUeditor only solution.
The wysiwyg also solves another dilemma for the administrator: What do the user's want?
Some users like a more complex editor, some like it to be a bit like the one in their favorite board or on major websites. Wysiwyg lets you install as many editors as you want, and the user can through the use of better formats decide herself which editor to use.
Another solution that wysiwyg provides is the deprecation of a lot of modules. When each javascript editor has its own project it leads to a lot of work for the first time administrator, installing, testing and deciding. With wysiwyg a lot of clutter disappears, and an administrator can try out a lot of editors with the click of a mouse. In theory all wysiwyg-aware modules will then work with all the editors, which is a good thing :)
In the beginning it felt like wysiwyg was just making things more complex, now I'm of the mind that every module doing something for a specific editor implementation instead of using the wysiwyg api is the problem, not vice versa.
Wysiwyg brings me hope that I don't have to choose an editor because of supporting modules of that editor, but can have all supporting modules inside my editor of choice.
Great write-up and summary! I
Great write-up and summary!
I figure we should put something like that on the project page or in the handbooks, so new users can understand the paradigm more easily?