mccartney wrote:I like it, especially the drag and drop. Have found one problem however - when viewing "gallery details" the description field is blank.
Thanks for the catch, should be fixed now.
arjunrc wrote:b) You have a button called 'load all images'. Consider also adding 'load next set of images' - In my case, I have a pblog with around 900 images. I wanted to edit an image that did not show up in the first set, but I had to wait for around 1 minutes before all my images loaded up.
Approved, I'll get working on that. In the meantime, if you want to be able to edit such a large gallery, consider using the 'original edit page' link at the bottom left of the page. This will let you edit the gallery the old way and will only load the first 20 thumbnails. However, on this page you can actually edit the sequence numbers of the unloaded thumbnails.
arjunrc wrote:c) Looks like you update the DB real-time when I drag and drop. This suggestion may go both ways, but is it better to have an apply button so I can experiment before I apply ? It will be faster, also works as a sort of 'undo any bad things', and you can do a JS popup that says 'you have changes that are not implemented. Apply?' if you detect some threshold of changes, or the user tries to close the window without applying.
Don't really like the idea of the apply button since it is easy enough to undo any changes you made anyway. If you want to really go nuts experimenting with the order or your gallery and then revert it back quickly here is a work around:
• open up a new tab with the edit page loaded
• select all
• shift-click the first thumbnail so that you have everything but the first thumbnail selected
• go to your other tab and go nuts rearranging stuff
• once you want to revert everything back, switch tabs again and drag and drop your selection to the right of the thumbnail that isnt selected
• order restored!
You do bring up a good point about the DB updating every time you move stuff around. I believe I can change it so that your requests are queued up and not reliant on a response. Right now the code locks the page up while it waits for a response back, so this change would let you get stuff done a lot faster. We also plan on making it so that uploads can be done in the background (and will probably add a loading bar to boot).
