Yes, you are absolutely right. Parallel downloads / order and other issues need to be taken care of. Also, I noticed that if image is being downloaded in background then Flick animation gets slower.
Thanks, Maulik. On Sat, May 8, 2010 at 5:07 AM, faustino forcen <[email protected]>wrote: > I completely agree with Remi. It's not only a network speed issue, but > also the problem with the ordering of the loads. I mean: how many > parallel downloads will make Safari? In which order? If you asign > several images as a background to a div will it load them in order? If > you asign an image and then another, how do you control that the first > has been loaded before downloading the next one? > > Getting back to the first reply of Remi, maybe programming the > download of next/prev images after each image is loaded. I'm working > on other project these days, but I'll try this approach as soon as I > can. > > > > On May 8, 1:01 am, Remi Grumeau <[email protected]> wrote: > > Whatever number you want folks, but keep in mind that mobile signal is > not ADSL or cable network, and i think (but that's my personal opinion, > which means that i can easily be wrong :) ) that the less http request you > load at the same time, the best performance you should get. > > > > My advice would be just one image each side of the primary one, and then > once at a time when sliding. > > Again, this is my 0,02$ and a few tests would prove me right, or wrong... > > > > Remi > > > > Le 7 mai 2010 à 19:41, Victor Hudson a écrit : > > > > > > > > > What about preloading 3-5 images each way and then getting the next > one 4-6th image each time user swipes to next image? > > > > > Vic Hudson > > > > > On Fri, May 7, 2010 at 12:53 PM, Maulik Modi <[email protected]> > wrote: > > > I guess, better solution would be to load 5 images in the previous > direction and 5 images in the next direction. After user navigates all 5 > images, you might want to show progress bar and load images in the > background. > > > > > Thanks, > > > Maulik. > > > > > On Wed, May 5, 2010 at 4:07 PM, Remi Grumeau <[email protected]> > wrote: > > > The loading time of each image is a real problem, but you will > definitely not solve it by surcharging the http requests number at the same > time with this background trick. > > > Haven't think about that much, but if you load the next image when the > previous one is loaded, you may have a nice cascading image loader tha add > the image to the div using DOM. That would be my first thought / try > > > > -- > You received this message because you are subscribed to the Google Groups > "iPhoneWebDev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<iphonewebdev%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/iphonewebdev?hl=en. > > -- Good judgement comes from experience, and experience comes from bad judgement. Simple things should be simple, complex things should be possible. -- You received this message because you are subscribed to the Google Groups "iPhoneWebDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/iphonewebdev?hl=en.
