![]() To avoid memory leak in poorly written browsers I tried to find the best match between the two modes, still there are tons of differences. It’s a fundamental change in the structure, every part of the code had to be rewritten to work in both modes. achieving better search results, being able to comment images through Facebook separately, using several hundreds of images in the same folder, to name a few. 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. 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. ![]() Translations for major languages updated.Dealing with digital photo albums on the web you’ll see two basically different models.(Deleted rotate items for sake of space - available in the toolbar) Reverted to again presenting "extensions" directly under jAlbum's context menu.Developers: new JDraggableList component allowing skin user interfaces to allow end user to arrange objects by drag and drop.Developers: New "category" attribute for ja:if element, simplifying testing on categories.Developers: New "include" and "exclude" attribute to ja:fileiterator element allowing a comma separated list of categories to be included or excluded.Just open an existing Turtle project and switch to Tiger, then make the album again. This applies when moving from Turtle to the new Tiger skin for instance. This simplifies moving from one skin to another without having to re-enter the same settings. ![]() "Skin family" mechanism allowing skins belonging to the same family to share the same project settings.Batch rename now supports regular expressions (select several album objects and select rename to launch batch rename tool).New importer to import metadata from various database backed photo management systems (see Add->From database file). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |