Hi!
I wonder if it is possible to split a long gallery into several pages as it was in X2, i.e. to have a "carousel of grids".
Of course there is an option to physically split a gallery into several sibling folders and let the user navigate between them with navigation buttons, but this will not take the viewport size into account.
I'd prefer to have an option when the grid/columns/justified layout displays only those images that fit on the screen, while the rest of them are placed on other pages of the page carousel, probably with lazy loading of images.
Is it possible to organise a gallery like that in X3?
Thanks!
X3Photo Gallery Forums
X3 Photo Gallery Support Forums
Multi-page gallery3 posts
Re: Multi-page gallery
I hear what you are saying, and I agree that sometimes it's too much to pre-render a layout with hundreds of images. However, I don't think it's a practical solution to build "virtual pages" based on how many images fit on the screen ... Imagine how this would work on mobile devices and other small screens ... Even on my macbook 13", with browser-UI+menu+logo, I can't always fit that many images on the screen at once. It would create a clumsy scenario where the visitor is clicking through "pages" to find images. Besides, it would be a technical nightmare to integrate based on all X3 layout options ... We would have to calculate how many images fit into the current viewport, for the specific device, for the specific layout ... which in some cases could be just one or two images. "Pages" amount would be relative to screen size, and "page4" on a large desktop might be "page22" on a mobile device ... Further issues for deep-linking and SEO.
Personally, I love vertical scroll, and in my opinion it is generally the most effective navigation method for modern websites on modern devices. Touch devices and trackpads (especially Mac), make it fast and easy to navigate between content with vertical scroll.
Infinite Scroll / Load More
Instead, I think it would be more feasible and practical with a "infinite scroll" mechanism or "load more". Once visitor reaches a certain vertical scroll, the visitor will either get presented with a button "load more", or a new segment of gallery items will automatically get appended (and loaded). This is the method that generally all modern services use: Google, Flickr, Instagram, Pinterest, Tumblr etc.
PS! X3 already lazy-loads images as they come into scroll view. By using the method above however, X3 would not need to pre-render a full layout with a long scroll. Segments of items would appear as visitor scrolls to certain a threshold.
Personally, I love vertical scroll, and in my opinion it is generally the most effective navigation method for modern websites on modern devices. Touch devices and trackpads (especially Mac), make it fast and easy to navigate between content with vertical scroll.
Infinite Scroll / Load More
Instead, I think it would be more feasible and practical with a "infinite scroll" mechanism or "load more". Once visitor reaches a certain vertical scroll, the visitor will either get presented with a button "load more", or a new segment of gallery items will automatically get appended (and loaded). This is the method that generally all modern services use: Google, Flickr, Instagram, Pinterest, Tumblr etc.
PS! X3 already lazy-loads images as they come into scroll view. By using the method above however, X3 would not need to pre-render a full layout with a long scroll. Segments of items would appear as visitor scrolls to certain a threshold.
Re: Multi-page gallery
Oh yes, "load more" sounds really cool.
Yeah, the main problem I wanted to solve with this is exactly to avoid the need to pre-render complex layouts for huge galleries (and this is mostly because of the performance issue I have retorted in the other thread). For now I've worked around the issue by changing layout type, so the problem is not thatb important anymore.
Sill the lazy layout rendering looks like a cool feature for future :)
Yeah, the main problem I wanted to solve with this is exactly to avoid the need to pre-render complex layouts for huge galleries (and this is mostly because of the performance issue I have retorted in the other thread). For now I've worked around the issue by changing layout type, so the problem is not thatb important anymore.
Sill the lazy layout rendering looks like a cool feature for future :)