> 2) Implement the approach to RichTextField and global editor configuration > from django- > ckeditor, but leave TinyMCE as default. Introducing as little > incompatibilities as possible > would be the hard part.
Sounds like #2 is the approach for improving the core project, though creating a third-party mezzanine-ckeditor project would also be useful. Could you expand (perhaps with a code sample) on how django-ckeditor makes inline RichTextField configuration easier than Mezzanine? -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
