You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a reusable application, symposion should be mostly independent against UI part.
It has already archived when dropping all templates from symposion and introduce pinax-project-symposion.
There is another dependency that is MarkItUp widget.
Some user prefer to use TinyMCE (or other widget such as MarkEdit as in PyCon), but it is quite difficult to change without forking and modifying symposion code base itself.
Can we drop MarkItUp dependency from, at least, models?
Changing from MarkupField to TextField, then developer may be able easily to add their preferable widget to their templates.
The text was updated successfully, but these errors were encountered:
As a reusable application, symposion should be mostly independent against UI part.
It has already archived when dropping all templates from symposion and introduce pinax-project-symposion.
There is another dependency that is MarkItUp widget.
Some user prefer to use TinyMCE (or other widget such as MarkEdit as in PyCon), but it is quite difficult to change without forking and modifying symposion code base itself.
Can we drop MarkItUp dependency from, at least, models?
Changing from MarkupField to TextField, then developer may be able easily to add their preferable widget to their templates.
The text was updated successfully, but these errors were encountered: