There is another thing I just come across while working on the form implementation. I realised, that there are multiple ways to extend the ClearableFileInput to support multiple files. More specifically the clear checkbox. Should there be only one checkbox to clear all files or individual once to clear each file of the set of files inside contained by the input.
I think there are two think to keep in mind. This case is only for initial values. This case might be rare, since there is no model representation for that case. Hence, once would need to manually build a view and load those images as initial value for once input. This seems an odd UX choice. Secondly there is the question of consistency. If you upload a single of a list of files into a file widget, it would replace the current list of files. So it is all or nothing. I would recommend not to deviate from this approach when it comes to clearing initial values. Have separate checkboxes might also prove to be a UX issue, since users would need to check them all individually. What do you guys think? Am I on the right track regarding this issue? -- Johannes Hoppe Fon: +49 331 2812 9869 1 Fax: +49 331 2812 9869 9 www.johanneshoppe.com Lennéstr. 19 14469 Potsdam USt-IdNr.: DE284754038 On 2. Sep 2017, 11:10 +0200, Melvyn Sopacua <[email protected]>, wrote: > On Sat, Sep 2, 2017 at 10:37 AM, Adam Johnson <[email protected]> wrote: > > > ArchiveField sounds a bit too specific for Django core, the most common case > > for uploading multiple files would probably be to access them individually, > > which it would prevent. > > Yeah, was on the fence on that one myself. The use cases are very domain > specific, the obvious one being a backup application, but also design specs > or legal documents that site staff downloads and never actually views on site > individually. The upside of the field being that you have control of the > archive > format and/or can encrypt the archive with user specific key before sending. > > I researched it for an upcoming project and all the hooks are in place to > create such a model and you're right, it goes beyond "batteries included". > -- > Melvyn Sopacua > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/django-developers/IU8L9Gc6LUI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CA%2Bgw1GWTn%2B8f_bUV7mmJ8gEFodwUrtK_yzF_zEWA%2Bv5ew332gA%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f4db9126-e2c3-4dc9-9e43-c818a077be4d%40Spark. For more options, visit https://groups.google.com/d/optout.
