| Summary | Preview existing images when upload new one |
| Queue | Ansel |
| Type | Enhancement |
| State | Assigned |
| Priority | 1. Low |
| Owners | Michael Rubinsky <mrubinsk (at) horde (dot) org> |
| Requester | Duck <duck (at) obala (dot) net> |
| Created | 06/05/2008 (94 days ago) |
| Due | |
| Updated | 06/26/2008 (73 days ago) |
| Assigned | 06/09/2008 (90 days ago) |
| Resolved | |
| Attachments | upload.diff ![]() upload.css ![]() |
| Milestone | |
| Patch | No |
I don't see any reason why we can't use this...
I don't see any reason why we can't use this...
State ⇒ Assigned
I'll try to dig around for another alternative for the carousel and
see what I come up with...otherwise, I'll add this one.
Thanks again!
New Attachment: upload.css
You didn't include the CSS rules you used for the carousel, so I used
the example from the author's web page, changed the class names to
match what you used in the code and took some guesses...so, I'm not
100% sure how you intended this to look on the upload page.
Hopefully, you have a patch for the css you used? I'm not crazy
about the text navigation links, but that's trivial to change.
load, I suppose because it's loading _all_ the gallery's thumbnails,
in the gallery's style, onto the page. This is not good...If we're
going to do this, I would prefer some Ajax magic to load the images
in groups (maybe the same number as defined in the prefs). To
compound the problem, if you have just uploaded large numbers of
images, the thumbnails are not yet generated, so we are not only
loading all the thumbnails, we are possibly generating all of them as
well. At the very least, if we don't do the ajax calls, we should be
forcing the plain thumbnails, or better yet, the mini
thumbs...anything but the 'pretty' thumbnails.
I'm wondering if this would be better as a horizontal scrolling
carousel, with more than one image being visible at a
time...something that the JS code your using doesn't seem capable of?
find a simple prototype script for this. Displaying the last 5 images
by default would be enough.
You didn't include the CSS rules you used for the carousel, so I used
the example from the author's web page, changed the class names to
match what you used in the code and took some guesses...so, I'm not
100% sure how you intended this to look on the upload page. Hopefully,
you have a patch for the css you used? I'm not crazy about the text
navigation links, but that's trivial to change.
My real concern is that it took a _very_ long time for the pager to
load, I suppose because it's loading _all_ the gallery's thumbnails,
in the gallery's style, onto the page. This is not good...If we're
going to do this, I would prefer some Ajax magic to load the images in
groups (maybe the same number as defined in the prefs). To compound
the problem, if you have just uploaded large numbers of images, the
thumbnails are not yet generated, so we are not only loading all the
thumbnails, we are possibly generating all of them as well. At the
very least, if we don't do the ajax calls, we should be forcing the
plain thumbnails, or better yet, the mini thumbs...anything but the
'pretty' thumbnails.
I'm wondering if this would be better as a horizontal scrolling
carousel, with more than one image being visible at a time...something
that the JS code your using doesn't seem capable of?
State ⇒ Accepted
Assigned to Michael Rubinsky
New Attachment: upload.diff
Patch ⇒
Milestone ⇒
Queue ⇒ Ansel
Summary ⇒ Preview existing images when upload new one
Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ New
Very usefull for large galleries when you forgot the last uploaded
image.
The prototype js plug-in can be dound
http://www.victorstanciu.ro/prototype-plugin-carousel/