[Django] #21611: RichTextField

4 views
Skip to first unread message

Django

unread,
Dec 13, 2013, 12:14:18 PM12/13/13
to django-...@googlegroups.com
#21611: RichTextField
-----------------------------+--------------------
Reporter: revolunet | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: 1.6
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------
hi

Having support for a rich text field in the admin looks like a more and
more common use case to me : editing pages, fragments, model
descriptions...

There are many existing HTMLField implementations but generally painful to
integrate, especially for django newcomers. (and too much choices)

Would be awesome to have a builtin RichTextField with at least a minimal
wysiwyg editor, which could handle HTML, or markdown. We could make the
editor swipable with another implementation (tinymce, redactor.js...) if
needed. (Next to this there is image upload from the editor, but we'll
talk about it a bit later).

Do you think this makes sense to integrate this in Django core ?
I think this would be a really nice addition to the already awesome admin
interface, and makes things easier for beginners.

If so let's discuss about implementation, which editor to use... and i'd
be pleased to help.

Thanks !

--
Ticket URL: <https://code.djangoproject.com/ticket/21611>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Dec 13, 2013, 12:40:30 PM12/13/13
to django-...@googlegroups.com
#21611: RichTextField
-----------------------------+--------------------------------------
Reporter: revolunet | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 1.6
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Changes (by aaugustin):

* status: new => closed
* needs_better_patch: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_docs: => 0


Comment:

Assessing and selecting an external app takes some work, but competition
results in better apps overall that what could be maintained in Django
itself. It's pretty much the same story as urllib2 vs. requests :)

As far as I know, third-party apps such as django-markitup do the job well
with the hooks currently provided by Django. If Django could provide
better hooks to make such integrations smoother, we'd certainly consider
suggestions favorably.

That said, the proper place to discuss a large addition is the django-
developers mailing list, in order to reach a wide audience. You'll have to
present a concrete proposal and compelling arguments, because the current
trend is to trim down Django by deprecating contrib apps that aren't "best
of breed" any more. The team's resources are already spread thin for
maintaining core and contrib. "It would be nice" won't fly!

In terms of process, I'm going to close the ticket as "needsinfo", where
the info needed is a concrete implementation plan and a consensus on the
mailing list that it's a good idea, or at least a few +1 from core devs.
If you reach that point, then you can reopen this ticket and use it to
track the implementation work. Thanks for your understanding!

--
Ticket URL: <https://code.djangoproject.com/ticket/21611#comment:1>

Django

unread,
Dec 14, 2013, 7:47:33 AM12/14/13
to django-...@googlegroups.com
#21611: RichTextField
-----------------------------+--------------------------------------
Reporter: revolunet | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 1.6
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed

Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------

Comment (by revolunet):

thanks for the feedback, i'll send a detailed proposal on the ML

--
Ticket URL: <https://code.djangoproject.com/ticket/21611#comment:2>

Django

unread,
Nov 8, 2018, 7:33:11 AM11/8/18
to django-...@googlegroups.com
#21611: RichTextField
-----------------------------------+--------------------------------------
Reporter: Julien Bouquillon | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 1.6
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed

Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------

Comment (by Jaap Roes):

Just for the people that might stumble across this issue: there's a 3rd
party [https://pypi.org/project/django-richtextfield/ editor agnostic
`RichtTextField` for Django] available that does pretty much what's
described in this ticket. (full disclosure, I'm the author of said
package)

--
Ticket URL: <https://code.djangoproject.com/ticket/21611#comment:3>

Reply all
Reply to author
Forward
0 new messages