Expand Index output to include more than 90 sets

[GoogleCodeExporter]

What is the expected output? What do you see instead?
Models with more than 90 sets are truncated at 90 on the index image. Currently 
only VIP sets are that high, but with the ability to create multiple dynamic 
index sheets, users may be able to set number of thumbnails per page and such.

Original issue reported on code.google.com by mranimos...@gmail.com on 25 Sep 2012 at 6:28

[GoogleCodeExporter]

did some preliminary work last night on it, not much success on how i want it 
to work yet. When I get some better results will post a WIP

Original comment by mranimos...@gmail.com on 5 Oct 2012 at 11:35

[GoogleCodeExporter]

Been thinking about this. My first thought is to extend the CacheImage table 
with two int-columns. For records with an index_id, one contains the 
index-sequence and the other total number of images. Non-index records will 
have NULL in both columns.

For example the records for a cached image of VikaZ with 12 thumbnails per 
image would all have the same UUID, but have different sequence-nunbers (1/4, 
2/4, 3/4 and 4/4). This way we can still fetch the complete Model index from 
the cacheimage table, but have multiple records returned - and put them in a 
slideshow, zipfile, whatever.

For generating the custom-size indexes, I thought the admin_panel would be the 
proper place. Put an extra dropdown control containing 1, 2, 4... and let 
download_index.php handle the multi-imaging. We can put a lot of that dirtywork 
into a separate class - to keep it all readable.

Original comment by fwp...@gmail.com on 26 Oct 2012 at 9:47

[GoogleCodeExporter]

that is a thought that could work, would make referencing the cache index better

Original comment by mranimos...@gmail.com on 27 Oct 2012 at 3:06

[GoogleCodeExporter]

So far looks good

Original comment by mranimos...@gmail.com on 16 Nov 2012 at 1:19