fine-uploader
fine-uploader copied to clipboard
Feature Request: Re-order images with drag n drop.
Type of issue
- [ ] Bug report
- [x ] Feature request
Uploader type
- [x ] Traditional
- [ ] S3
- [ ] Azure
Note: Support requests cannot be accepted due to lack of time.
Feature Request: Allow to re-order images in the drag n drop area updating an index attribute in them
Feature Request: Allow to re-order images in the drag n drop area updating an index attribute in them
Feature request details
Add the possibility of re-ordering images once uploaded. Assign an index to every image and allow re-ordering them through drag n drop.
We are building this interface where first we are uploading the images to our local server, and then later after posting a form, this images will fly to a remote location. As part of the requirements for the job we have "the chance of ordering the uploaded images before submitting"
Would you be willing to open a PR with changes?
Hi SinghSukhdeep,
Yeah, maybe it'd be an option. Thanks for your comment, I'll consider it.
Although I don't actually see how would this be beneficial. Ordering the images in the UI doesn't really matter as this order wouldn't sustain once images go to your server. I don't quite understand what exactly you are trying to do, can you maybe clarify a bit. Otherwise I don't see this being implemented ever.
Yes, it does matter. We have an web app where we upload images to a remote server. The user will be able to select the images order, these are sent in a specific order to the server, and it's how they are displayed in the remote application. So it does matter.
these are sent in a specific order to the server
Instead, I'd suggest including some metadata/params to send along with each file to indicate the "order". You can build ordering into the UI, but without changes to the uploader code as well, they won't actually upload in the new order. I don't anticipate this being a simple change either, and probably not worthwhile to introduce that sort of additional complexity into the codebase with only one use case.