Opened 12 years ago

Closed 12 years ago

#7406 closed (wontfix)

Json widget for newforms

Reported by: riklaunim@… Owned by: nobody
Component: Forms Version: master
Severity: Keywords:
Cc: Triage Stage: Someday/Maybe
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


I've added a widget for newforms for handling Json data – it uses a text field that has a JSON string like {“a”:”b”, “c”:”d”} it displays it in a series of form inputs for every key-value. When saving data two lists are dumped into a dict and then into a JSON.

Attachments (2)

json_inputs.patch (1.9 KB) - added by riklaunim@… 12 years ago.
The patch
json.png (2.0 KB) - added by riklaunim@… 12 years ago.
widget in action

Download all attachments as: .zip

Change History (6)

Changed 12 years ago by riklaunim@…

Attachment: json_inputs.patch added

The patch

Changed 12 years ago by riklaunim@…

Attachment: json.png added

widget in action

comment:1 Changed 12 years ago by riklaunim@…

And it requires simplejson

comment:2 Changed 12 years ago by George Vilches

I suspect that since this is a new widget, rather specialized (a form widget that creates JSON specially and directly from the form submission, instead of a separate post form data processing activity), and does not require inclusion in Django to work correctly, that it should be hosted externally until such impetus from the community makes it work including internally.

However, I'm not a core dev, so I can't make the final decision, but at best I see this as Someday/Maybe.

comment:3 Changed 12 years ago by mrts

Triage Stage: UnreviewedSomeday/Maybe

gav is right, this widget is too specific do justify inclusion in Django itself. Please post this to djangosnippets.

Marking as Someday/Maybe to ease ticket triaging for core devs.

comment:4 Changed 12 years ago by Russell Keith-Magee

Resolution: wontfix
Status: newclosed

This is a pretty specific widget, for a fairly edge case requirement. It would be hard to argue that there is a widespread need for this capability. As gav and mrts noted, this is much better suited to djangosnippets, or a 3rd party widget library.

Note: See TracTickets for help on using tickets.
Back to Top