> On 13 Feb 2015, at 16:09, Andrew Davis <[log in to unmask]> wrote:
>
> Are we missing something obvious? As always, there's budgetary constraints at work, and we need to have something that we can make available in the near future, but we'd need the solution to be scalable and ideally one that will last us for the lifetime of this iteration of our online collection.
>
> Any comments and suggestions gratefully received!
As a user I really don’t like slow loading pages with huge galleries of images and I really, really don’t like page turning presentations.
As a developer I can see why your developers might suggest limiting the number per record, but I’d be suggesting going further and presenting each record with a *single* image initially, but create a series of linked pages for every other image you have for that record (a user will only download them until they get bored - storage space is then your consideration - 450 images sounds like a whole book!
A list of links to images is one way, a link to the first image that links to the next is another. The web is good at hyperlinking and loading images, it breaks when you try and load all the images at once and display them one by one (like most javascript galleries do)
Your developer should be able to prepare html files for each image that links to the next - if you wish to add a page turning paradigm to that, just have the next and previous links at the corners…
If you keep the web simple it will be fast and enjoyable.
Just my Friday 2p worth of opinion.
:o)
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|