Wysiwyg
Just had to reinstall all the modules because of a core update, and so I need to reinstall the wysiwyg editor. I found the new Wysiwyg module, and thought great this should be simpler to install and configure than before. But after reading the install instructions it turns out you must also install a "library". I think what most drupal site admins want most is a simple wysiwyg editor that is built into Drupal or a module that you just install and is ready to go.
Groups:
Login to post comments
I agree that including libraries makes sense
I'm not sure why people so often skip BSD and GPL licensed libraries. I understand skipping libraries that are restricted via licensing, but in a giant GPL community most of these libraries are free. It's one thing to have a php module dependency, but a code dependency that's unincluded doesn't make sense to me. If you're knowledgeable enough to hunt down and install the library, you're knowledgeable enough to upgrade it if you feel the need.
I've seen more than one case where the latest library broke things. We should include a tested codebase with a module to insure it works as advertised.
Reasons
Especially the last point is important. Drupal does not provide proper support for client-side editors (also WYSIWYG), because there have been countless of different editor library integration modules. All of them being duplicated efforts. No other Drupal modules were able to easily integrate with more than one editor.
Wysiwyg module is about to invent a new standard for content-editing in Drupal. It will allow you to do really crazy and insane stuff with your content, using the editor of your choice.
Daniel F. Kudwien
unleashed mind
All good reasons, to allow the end-user to change things
All of these are great reasons for me to change my local configuration. But, it'd be nice if the tool was tested with some library, released with some proven library. These are all good reasons to allow me to do whatever I want, perhaps even to document alternative WYSIWYG tools and libraries. But, I've installed [a] WYSIWYG module more than once where it required me to manually hack the module itself to get the editor working. Some kind of baseline testing or proven library would be a nice proof of concept, and most people would likely just stick with whatever shipped. I love the liberal thinking of "plug in what you want," and development in that direction is great. But, some proven codebase would be nice.
...
What's shipped with Wysiwyg has usually been tested to the usual extent; like any other module. I can only guess that you mean further customizations here, e.g. applying or altering advanced editor settings and similar things. Of course, the module only supports what it supports currently. However, that is not an issue with libraries not being shipped/packaged with the module, but rather caused by the fact that Wysiwyg module is still very young. Wysiwyg 3.x will be entirely rewritten to allow for further customizations and even more and better integration of editors in Drupal.
Daniel F. Kudwien
unleashed mind
I think imjasonn is
I think imjasonn is referring here to other wysiwyg modules like fckeditor - where to get it working you have to also download the fckeditor files from their site, copy things here and there and generally 'set things up' before it will work.
I agree that a simple module that Just Works would be a great thing to have in an initial download, with options to change things if you want to upgrade or change editors etc. However, I also know how frustrating this can be for module maintainers as the libraries included in the download in question get out-of-date.
Forgot to say, though, that
Forgot to say, though, that I'm very excited by the WYSIWYG module that you're working on, Sun, and I think it is a HUGE step forward for Drupal and the thinking around wysiwyg integration. I will definitely be testing this module on my next site.
Not built in
Installing and configuring a wysiwyg editor may be inconvenient to some but the pay off is a light weight, highly configurable content management system for all. There are so many different requirements for filters and editors. Including one would be a bad idea.