Joys Sorrows of Wysiwyg using Drupal
•Descargar como PPT, PDF•
2 recomendaciones•3,319 vistas
The Joys and Sorrows of implementing WYSIWYG in a Drupal environment, reasons for and against doing and my experience from a recent project.
Recomendados
Más contenido relacionado
Destacado
Similar a Joys Sorrows of Wysiwyg using Drupal
Similar a Joys Sorrows of Wysiwyg using Drupal (20)
Último
Último (20)
Joys Sorrows of Wysiwyg using Drupal
- 1. Leo Robert Klein Chicagoland Library Drupal Group 12/7/2009 Joys & Sorrows of WYSIWYG* *How I Stopped Worrying and Learned to Love the 'Wyg'
- 2. To WYSIWYG or Not To WYSIWYG* *Hamlet Act 3, scene 1, 55
Notas del editor
- Best for those who have little or no experience posting articles or comments on the web - Particularly where the gulf between their experience and the possibility of learning html tagging potentially is insurmountable obstacle Text-based tagging potentially a _big_ problem and can be extremely frustrating (eg trouble-shooting) Content Creators more comfortable with MS Word Makes sense as we move to a more enhanced and interactive online experience
- WYSIWYG EDITORS YUI editor - from Yahoo, also another ('Closure') from Google using basically the api/buttons from GoogleDocs. INTEGRATION MODULES Need some mechanism to connect or integrate these editors-libraries into Drupal. EXTRAS Content management of files making up the page -- anything from images to attachments
- INPUT FILTER Original and most basic formatter
- General Considerations: Speed (loading, working) - Editors consist of countless pages of include pages (javascript, images/buttons, css - big time) Browser compatibility - only works in IE6? Pasted content from MS Word - works or is a complete mess Valid code? OVERALL TREND: trimmer, faster editors, compatible over a wider range of browsers, producing valid code and even may meet accessibility requirements Functionality in keeping with Cloud Computing applications
- WYSIWYG Integration ModulesNeed for 'helper' module to go between the WYSIWYG editor and Drupal Old School: first upload the editor, then upload the editor-specific integration module. Wysiwyg API not only replaces all editor integration modules, but also unifies the integration for all other Drupal modules in contrib by providing a central API to supply plugins/buttons that work in any editor (even if there is none).