WYMEditor in 3.0

75 views
Skip to first unread message

Daniele Procida

unread,
May 24, 2013, 3:19:22 PM5/24/13
to django-cms...@googlegroups.com
The WYMEditor is absolutely essential to us, so I am considering the best way to provide it for django CMS 3.0.

The earlier cms.plugins.text was fairly editor-agnostic; it seems a shame to have lost this. I would have preferred a single text plugin, which could be configured to use one of multiple text editors.

After all, the main difference between editors is some JS and templates - not Python.

So it seems that to provide a WYMEditor, I will have to create the analogue djangocms_text_wymeditor, based on djangocms_text_ckeditor. I've started to have a look at this.

Since neither of the two built-in editors (WYM and Tiny) of earlier versions are now provided, there needs to be an easy way for users who want to stay with those to roll their own for the CMS, even if the plan is not to provide them.

Daniele

Patrick Lauber

unread,
May 24, 2013, 4:31:10 PM5/24/13
to django-cms...@googlegroups.com
As we don't want to support 3 different text editors or even more in the same package and corresponding JS files… 3 different packages with the djangocms-text-wathever naming is adequate. djangocms-text-ckeditor is a clone of cms.plugins.text… the only additional functionality is that drag and drop of pictures is supported and that those pictures are converted into text plugins automatically. The rest should be the same if i remember correctly…. then there is the question of replacement… djangocms-text-ckeditor uses the cmsplugin_text name in the database as well so it can be an inplace replacement for the other two. I think this is a good idea if you want to switch editors.
> --
> You received this message because you are subscribed to the Google Groups "django-cms-developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to django-cms-devel...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Daniele Procida

unread,
May 25, 2013, 4:37:48 AM5/25/13
to django-cms...@googlegroups.com
On Fri, May 24, 2013, Patrick Lauber <di...@treepy.com> wrote:

>As we don't want to support 3 different text editors or even more in the
>same package and corresponding JS files... 3 different packages with the
>djangocms-text-wathever naming is adequate. djangocms-text-ckeditor is a
>clone of cms.plugins.text... the only additional functionality is that
>drag and drop of pictures is supported and that those pictures are
>converted into text plugins automatically. The rest should be the same
>if i remember correctly.... then there is the question of replacement...
>djangocms-text-ckeditor uses the cmsplugin_text name in the database as
>well so it can be an inplace replacement for the other two. I think this
>is a good idea if you want to switch editors.

There is still quite a lot of WYM stuff hanging around in the CMS, by the way, in docs and in static files.

Anyway I have started work on <https://github.com/evildmp/djangocms-text-wymeditor>.

Daniele

Patrick Lauber

unread,
May 25, 2013, 7:38:07 AM5/25/13
to django-cms...@googlegroups.com
yes we need to do a major cleanup as soon as we removed all plugins from core…
Reply all
Reply to author
Forward
0 new messages