Wysiwyg for 2.0?

[Silmarillion]

Hello dev-people

As the (de facto, not much by choice) maintainer of most wysiwyg-modules I'm considering the options for choice of wysiwyg in 2.0. I think we should stick with Tiny, as there's a lot of work going on with it (3.0beta1 out now, smaller, faster etc). But I also think that work should go into it. I've got the following wishes:
  * Only one version, I cannot maintain both Tiny and TinyAdv, too much work. Stupid idea in the first place. As upcoming 3.0 version is 25% smaller I think we should include the whole shabang, which leads me to new wish...
  * Customizable feature sets for different admin groups. This could require some kind of API-changes/extensions, but I really think it would be good (for other modules as well) to be able to adjust module preferences according to groups. I will gladly help doing the core/api-part as well.
  * Rewritten file-manager part. Relies on a FCK-project not maintained anymore. Not good... Could perhaps be a joined effort with FileManager-module for the core!?

What do you think? Is there an obvious alternative to Tiny presently? And do you have wishes for the integrations into CMSms. Please let it be wishes for integrations only, not for Tiny behavior as that (probably) is a matter of Tiny-core, not the module. I would rather not hack the Tiny-distribution at all for the module, as it makes it hell to stay updated with newest version.

Regards
Silmarillion/Morten

[Pierre M.]

Hello,

I'm not in the dev team. I'd like to thank you for the good work so far.
All you have written seems good ideas to me. I like simplicity : less bugs, less failures, less need for support
Have fun coding !

Pierre

[kermit]

i don't envy you nor want your job, morten. the editors are the thorn of the rose that is cmsms.

anything you can do to "dumb-down" the editor and its default settings...  restrict the use of inline styles and old-school formatting tags; and better integrate cmsms stylesheet style definitions (tags, classes and IDs specified by the admin as 'editor-accessible'); would be greatly appreciated!  perhaps a 'basic' and 'advanced' mode for the editor, so 'basic' users get the (hopefully) idiot-proof one and 'advanced' users get a different config that does allow some of the things not allowed in 'basic'...

[hexdj]

Hi Silmarillon

I have a couple of requests.  Please consider adding these in a future version of TinyMCE.  We all appreciate your hard work!

* Adding a GreyBox pop-up window (the current pop-ups work great but would be wonderful to see this as an option)

* Maybe make a global option in which when an image is inserted it is inserted with the Absolute Path behind it, this comes in useful for example when using NMS and the final user doesn't know how to insert the full absolute path and NMS doesn't attach images

* Can links to CMSMS be underlined rather than having the {cms_link} tag? its just that it confuses some editing users when working in tinyMCE, they don't understand {cms} tags even after explaining and when cutting text they forget and they leave some {} behind

Just my thoughts

Thanks!

[cyberman]

Hi Sil,

  * Rewritten file-manager part.

Maybe we can use another plugin like this

http://sourceforge.net/tracker/index.ph ... tid=738747

[Silmarillion]

Feature wise WYM is not very developed. And it's not really a WYSIWYG more of a structural/graphical editor.

Sil.

[moonoo]

What do people think of CKEditor then?

The structural setup of descriptive tags as you type into the WYSIWYG is a great feature for editors.. i.e P tags have a dotted box with a small p top left to notify that you have created a Paragraph block of text... Same with UL/Ol's etc..

If this way available in TINYMCE I think it would aide the user in understanding the importance of structure!

WYMEditor is also good for strict markup and would love to see a similar way of thinking.. A visual switcher to show the markup is correct..

An yes I agree ge rid of the ability for inline styles and rely on CSS classes... WYM has a good classes feature but it's hard to implement. But what it does do is allow the setup of H2,H3 tags with classes// wheres TinyMCE classes are not tied to the tags themselves meaning you could have a class called red and you wanted that to be for h2 tags.. you would need to click the H2 drop down in format and then red in the styles drop down.. with WYM it's one click..

Just a few thoughts here and there!

cheers

moonoo

[jpatti]

I like Tiny; it was one of my three primary criteria in choosing a CMS.

[replytomk3]

I have two suggestions.

1) A forum subtopic just for TinyMCE problems, with several stickies. For example, it is possible that several people here ran into the same problem I have and never could help themselves with all suggestions from the forum. Read the problem at http://forum.cmsmadesimple.org/index.php/topic,44280.msg214261.html. Having a list of things to do if Tiny crashes listed in a subforum will make people hate it less.

2) Lets reparse the half a dozen editor modules available in the module manager. If they are even usable, then tell people so. If they are obsolete and unmaintained, then delete them.

Silmarillion, Rolf promised to forward the link above to you. Did you receive it and are familiar with the problem?

[Silmarillion]

I agree to both #1 and #2. And I promise to stay somewhat up to speed with such a forumgroup.

I have some idea on the state of the wysiwyg-modules as I've been involved in most of them.

Sil.

[replytomk3]

I agree to both #1 and #2. And I promise to stay somewhat up to speed with such a forumgroup.

I have some idea on the state of the wysiwyg-modules as I've been involved in most of them.

Sil.

Can you please push this up the chain of command?

[Silmarillion]

Hi garlantinapple

Uhm, nothing depends on FCK anymore (since 1-2 years)... I rewrote the filemanager part from scratch long ago, and btw I also did the FileManager-module, so you are right about that, but everything should be ok on that account.

Sil.