#Jalbum version 11.6.14 skin#

It’s because there are several scenarios when the separate slides mode is still beneficial, e.g. You might ask why did then Turtle introduce the traditional mode at all. A dynamic album is capable of making smooth transitions between the images, loading only the necessary components, an rendering a full folder only once.

#Jalbum version 11.6.14 skin#

This is why Turtle skin was originally made dynamic. The downside is inherent in the web technology which doesn’t allow transitions between web pages, nothing can remain from a previous page (like background music), and need to build every page from ground, loading and rendering everything on a page again and again.

Every page has a separate URL address, so you can bookmark or share images separately and can use external widgets which rely on the page address, for example Facebook commenting. In the traditional – separate slide pages – mode, the HTML page loads all the page components and all the widgets (like Facebook, Google +1, etc.) every time an image is loaded. Turn it on for the “Separate slide pages” mode – the default is still the dynamic mode. Here is the magic switch that decides between these modes in jAlbum, called “ Make slide pages“: I’ve seen a lot of confusion regarding these modes, so I decided to put up this blog post. Although this applies to any skin, I will talk specifically about the Turtle skin now, which has been enabled to generate traditional (separate slides) albums since version 4, just a few weeks ago. Sounds like a subtle technical detail but it has far reaching consequences.

The “traditional” – one image per HTML page – and the “dynamic”, which changes the images on the same HTML page upon user interaction, utilizing Javascript. Dealing with digital photo albums on the web you’ll see two basically different models.