<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Upload UI</title> 
  <pubDate>Fri, 10 Apr 2026 02:21:32 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7967</link> 
  <atom:link rel="self" type="application/rss+xml" title="Upload UI" href="https://bugs.horde.org/ticket/7967/rss" /> 
  <description>Upload UI</description> 
 
   
   
  <item> 
   <title>1.redirect again to image upload screen after image upload. </title> 
   <description>1.redirect again to image upload screen after image upload. Is a natural begaviour as you are filling the gallery. Otherwise you must always go back to the upload screen.

2.Load image_ids for lightbox only if gallery is  not empty

3.Show images in recursive order. Is more natural to see by default the last uploaded images not to always slide to see what you uploaded the last time.</description> 
   <pubDate>Mon, 09 Feb 2009 10:33:36 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7967#t52396</link> 
  </item> 
   
  <item> 
   <title>&gt; 1.redirect again to image upload screen after image upload</title> 
   <description>&gt; 1.redirect again to image upload screen after image upload. Is a 

&gt; natural begaviour as you are filling the gallery.



I&#039;m not sure I agree with this.  If we are going to change this behavior, I&#039;d much rather see something like a &quot;What do you want to do now?&quot; message. You could redirect back to the upload screen, and display this message with choices like view gallery, add captions, etc...

This is how Flickr works, IIRC.



Of course, even better would be an Ajax image uploader :)



&gt; 2.Load image_ids for lightbox only if gallery is  not empty



Looks good, thanks.



&gt; 3.Show images in recursive order. Is more natural to see by default 

&gt; the last uploaded images not to always slide to see what you uploaded 

&gt; the last time.



The only issue I have with this is that the images are not necessarily listed in chronological order, they are listed according to the image_sort field.  Listing them in reverse order may or may not provide the last uploaded image first - and it might lead to confusion with the user as to why there images are not in the order they have selected.</description> 
   <pubDate>Mon, 09 Feb 2009 17:16:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7967#t52407</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

http://cvs.h</title> 
   <description>Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/ansel/img/upload.php?rt=horde&amp;r1=1.38&amp;r2=1.39&amp;ty=u
http://cvs.horde.org/diff.php/ansel/templates/image/upload.inc?rt=horde&amp;r1=1.12&amp;r2=1.13&amp;ty=u</description> 
   <pubDate>Tue, 10 Feb 2009 01:37:54 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7967#t52437</link> 
  </item> 
   
  <item> 
   <title>Committed item #2 from above, and tweaked it a bit to remove</title> 
   <description>Committed item #2 from above, and tweaked it a bit to remove some (now) redundant checks in the upload template file and to avoid loading any of the js if we aren&#039;t showing the carousel.



Anyone else want to weigh in on points #1 and #3 before I close?</description> 
   <pubDate>Tue, 10 Feb 2009 01:39:35 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7967#t52438</link> 
  </item> 
   
  <item> 
   <title>&gt; The only issue I have with this is that the images are not</title> 
   <description>&gt; The only issue I have with this is that the images are not 

&gt; necessarily listed in chronological order, they are listed according 

&gt; to the image_sort field.  Listing them in reverse order may or may 

&gt; not provide the last uploaded image first - and it might lead to 

&gt; confusion with the user as to why there images are not in the order 

&gt; they have selected.



Then we can just resort the array of images_ids. As ids are incremental, we get the correct upload order by using rsort($image_ids, SORT_NUMERIC).

</description> 
   <pubDate>Tue, 10 Feb 2009 10:34:25 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7967#t52442</link> 
  </item> 
   
  <item> 
   <title>I guess I don&#039;t know if I&#039;m comfortable with changing the us</title> 
   <description>I guess I don&#039;t know if I&#039;m comfortable with changing the user-defined sort order...plus the image_id will only follow the larger the numer == more recent upload if there were no images moved into the gallery from another gallery - probably a somewhat fringe case, I know, but I don&#039;t think we should be relying on a backend specific numbering scheme for presentation logic.



</description> 
   <pubDate>Tue, 10 Feb 2009 14:56:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7967#t52443</link> 
  </item> 
   
  <item> 
   <title>If ease of navigation here is the goal - then we should prob</title> 
   <description>If ease of navigation here is the goal - then we should probably add a first and last image link to the carousel...</description> 
   <pubDate>Tue, 10 Feb 2009 14:58:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7967#t52444</link> 
  </item> 
   
  <item> 
   <title>What&#039;s left here?</title> 
   <description>What&#039;s left here?</description> 
   <pubDate>Mon, 09 Mar 2009 00:45:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7967#t52952</link> 
  </item> 
   
  <item> 
   <title>I&#039;m inclined to say this ticket can be closed.  Having a lig</title> 
   <description>I&#039;m inclined to say this ticket can be closed.  Having a lightbox on the page would be nice, but would pretty much require a total rewrite of the ajax carousel, not something I&#039;m personally up for in the near future.



First/Last links would also be nice, but again, would require some changes to the carousel code that I&#039;m not inclined to spend time on in the near future.



So, unless anyone else is going to do this, I&#039;d say this can be closed, or maybe given a 2.0 milestone...</description> 
   <pubDate>Mon, 09 Mar 2009 14:28:41 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7967#t52970</link> 
  </item> 
   
  <item> 
   <title>Closing for now.</title> 
   <description>Closing for now.</description> 
   <pubDate>Mon, 09 Mar 2009 14:29:47 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7967#t52971</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
