Why Drupal 5.x must have built-in WYSIWYG Editor?
Why Drupal 5.x must have built-in WYSIWYG Editor? General discussion · Drupal 5.x Drupal-id.com - October 6, 2006 - 07:18 I am a web developer with long experience in PHP Nuke, OpenPHP, and Mambo/Joomla. After take a deep look at the Drupal source code and coding that available on TinyMCE and FCKEditor module, I can say that next Drupal version must has a builtin WYSIWYG Editor. Please CMIIW, but read my reasons first before you have different opinion: 1. Both TinyMCE and FCKEditor only find <textarea> then translate to their editor interface. Then how to avoid certain Textarea not converted? The anwer is not possible. What TinyMCE does only disable editor on certain page and FCkEditor will work if the textarea >= n rows. The real case is disknode module. When you set disnode to allow more than 1 file per disknode then the <textarea> of file upload list will converted to Editor. Currently, you can disable the <textarea> on this page but the <textarea> for type description of disknode will be disabled too. You may say, that you can enable the rich-editor-toggle, but you can't set 2 default value: the description using Editor and the file upload list using <textarea>. 2. A best solution, IMHO, is provide a function in Drupal to call the Editor. This Editor() function simply call the ediitor if available, but if no editor installed then Editor() uses <textarea>. What are the advantages if Drupal has Editor() function? 1. Developer like me, will be easier to create module that need both Editor and <textarea> in same page/block 2. We can extend the User Administration: adding capability to select which default editor for each users. We can set that default editor for user is: none (mean using textarea), TinyMCE, HTMLArea, FCKEditor or any editor that installed by third party modules. 3. Easier for community website which contain people that aren't not familiar with HTML tag 4. Easier for blogging site, since blogger usually a person with limited website knowledge, such as journalist, teacher, employee or doctor 5. At the rest, Drupal will no doubt called as the killer CMS. This will add more powerful to Drupal, the best CMS that I love.
I would +1 this personally. But the biggest hurdle might be license. I don't know. I think by default though, it would be great to have the easy editor for things. I have a client that has a bunch of 65+ old ladies using Drupal, and teaching them html gets scary. :) If we are including things like AJAX and such, why not just trick out the text editors, of course, offer the ability to fall back to normal input mode. Personally, I'd love to have a vim module for editing in a form! ;) Trae On 10/6/06, Drupal Indonesia <support@drupal-id.com> wrote:
Why Drupal 5.x must have built-in WYSIWYG Editor? General discussion · Drupal 5.x Drupal-id.com - October 6, 2006 - 07:18
I am a web developer with long experience in PHP Nuke, OpenPHP, and Mambo/Joomla. After take a deep look at the Drupal source code and coding that available on TinyMCE and FCKEditor module, I can say that next Drupal version must has a builtin WYSIWYG Editor. Please CMIIW, but read my reasons first before you have different opinion:
1. Both TinyMCE and FCKEditor only find <textarea> then translate to their editor interface. Then how to avoid certain Textarea not converted? The anwer is not possible. What TinyMCE does only disable editor on certain page and FCkEditor will work if the textarea >= n rows.
The real case is disknode module. When you set disnode to allow more than 1 file per disknode then the <textarea> of file upload list will converted to Editor. Currently, you can disable the <textarea> on this page but the <textarea> for type description of disknode will be disabled too. You may say, that you can enable the rich-editor-toggle, but you can't set 2 default value: the description using Editor and the file upload list using <textarea>.
2. A best solution, IMHO, is provide a function in Drupal to call the Editor. This Editor() function simply call the ediitor if available, but if no editor installed then Editor() uses <textarea>.
What are the advantages if Drupal has Editor() function? 1. Developer like me, will be easier to create module that need both Editor and <textarea> in same page/block 2. We can extend the User Administration: adding capability to select which default editor for each users. We can set that default editor for user is: none (mean using textarea), TinyMCE, HTMLArea, FCKEditor or any editor that installed by third party modules. 3. Easier for community website which contain people that aren't not familiar with HTML tag 4. Easier for blogging site, since blogger usually a person with limited website knowledge, such as journalist, teacher, employee or doctor 5. At the rest, Drupal will no doubt called as the killer CMS. This will add more powerful to Drupal, the best CMS that I love.
-- Trae McCombs || http://occy.net/ Founder - Themes.org // Linux.com
On Friday 06 October 2006 08:11 pm, Trae McCombs wrote:
I have a client that has a bunch of 65+ old ladies using Drupal, and teaching them html gets scary. :)
Personally, I'd love to have a vim module for editing in a form! ;)
Why? Are you planning to teach your 65+ old ladies to use vim? ;] Now THAT is a thought... Augustin. -- http://www.wechange.org/ Because we and the world need to change. http://www.reuniting.info/ Intimate Relationships, peace and harmony in the couple.
On 06 Oct 2006, at 10:44, Drupal Indonesia wrote:
Why Drupal 5.x must have built-in WYSIWYG Editor? General discussion · Drupal 5.x Drupal-id.com - October 6, 2006 - 07:18
No need to fork this discussion. It can be discussed on drupal.org where this thread started. -- Dries Buytaert :: http://www.buytaert.net/
On 10/6/06, Dries Buytaert <dries.buytaert@gmail.com> wrote:
On 06 Oct 2006, at 10:44, Drupal Indonesia wrote:
Why Drupal 5.x must have built-in WYSIWYG Editor? General discussion · Drupal 5.x Drupal-id.com - October 6, 2006 - 07:18
No need to fork this discussion. It can be discussed on drupal.org where this thread started.
Can you point me to the right place (url?) of where to discuss this further? Robrecht
Op vrijdag 6 oktober 2006 10:44, schreef Drupal Indonesia:
2. A best solution, IMHO, is provide a function in Drupal to call the Editor. This Editor() function simply call the ediitor if available, but if no editor installed then Editor() uses <textarea>.
Besides choosing whether or not to render a WYSIWYWFU based on urls, choose any of the following: * CCK-textarea toggle (limited to nodes, but very granular) * textarea ID, possibly advanced settings with regexps. Each TE has an id, it should be easy to capture all these possibly even combined with urls. See HTMLarea drupal mod for this implementation. * users/roles. * user setting, or session variable. * theme. Texareas are themable you can use this. * time of the day. Dont show textareas between midnight and 6 oclock (right makes no sense, but just to make my point clear) * position of the moon in relation to the sun. Again: senseless but hey, who knows? I have played with #2 for quicktags, and have the code for per-area settings done: in admin-textarea mode each textarea comes with some settings: [x] Show quicktags on this textarea [X] show for administrators [X] show for registered users [ ] show for anonymous users [ ] show only if the moon is up, and the sun is down. (no, this one will not go in) Hope to introduce this in the 5.0 version of quicktags, with possible backport to a 4.7.1 version. So: core needs not support anything, you already have full power to make whatever you want. Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
participants (7)
-
Augustin (Beginner) -
Bèr Kessels -
Dries Buytaert -
Drupal Indonesia -
Robrecht Jacques -
Sam Tresler -
Trae McCombs