summaryrefslogtreecommitdiff
path: root/templates/template_picture.html
AgeCommit message (Collapse)AuthorFilesLines
2015-01-11generators: Remove unnecessary picture page global blockTomas Bzatek1-3/+0
Turned out there was no need for having most of the picture page closed in a block.
2015-01-04generators: Use single function for all templatesTomas Bzatek1-7/+8
This commit makes use of a common function for all template parsing and page writing. The behaviour is controlled by the "item" argument passed in. This allows us to have a single code that generates code for list of items as well as for a single item. In the future, this can be used for e.g. combining thumbnails and large images on the same page. Other than that this commit also brings several other changes: - further clarification of theming setup XML file - <protected_thumbnail> tag has been moved out of the <album> structure into the <index> structure where it functionally belongs. Only whole albums can be protected and the substitute thumbnail is displayed on index pages. - position marker format has been broken out to a constant - added few more FIXMEs to mark places that will change soon - some template variables have been renamed
2014-09-17theming: Make navigation bar strongly themedTomas Bzatek1-1/+19
Navigation bar can be complex and comprises of several different elements. Until now the navigation bar was almost hardcoded. We needed to separate different types of navigation bar elements: * NAV_BAR_FIRST - the first element, usually denoting gallery root. This element takes priority and is used when there are no other elements in the path. * NAV_BAR_ELEM - normal element used in the path between first and last elements. * NAV_BAR_LAST - ending element, guaranteed there's at least the NAV_BAR_FIRST element before. * NAV_BAR_CURRENT - non-clickable informational element displaying the current page title. Optional, in contrast to the former three defines. * NAV_BAR_CURRENT_ROOT - a special case of the latter one, displayed at the very root page. Also optional, in that case the navigation bar would become empty.
2013-04-07Add rel="prev"/"next" attributes to navigation linksTomas Bzatek1-2/+2
Some browsers may understand this tag and use the associated link for easy transition to the next item. While in case the link points to the index page the rel="index" value should be used, we would lose browser capability to determine previous/next page for transitioning, thus hardcoding for our case. http://mail.xfce.org/pipermail/xfce/2011-August/028993.html http://mail.xfce.org/pipermail/xfce4-commits/2011-March/017929.html http://microformats.org/wiki/existing-rel-values
2012-12-27Add support for EXIF Canon Camera temperatureTomas Bzatek1-0/+3
For the moment we're using Exif.CanonSi.0x000c key from Exiv2 namespace since it's an unknown tag to it. This may need little tweaking in the future when proper naming becomes upstream.
2012-04-15Add HAS_EXIF defineTomas Bzatek1-2/+10
This brings a new HAS_EXIF define which is present when EXIF information are available. Templates have been modified to inform user when not available. The test for EXIF metadata presence is fairly basic, we only look for aperture, focal length and exposure time attributes. This might be a subject to change in the future.
2012-04-15Change EXIF metadata handling into a registered functionTomas Bzatek1-8/+8
This allows much greater flexibility from templates regarding EXIF metadata handling, no more hardcoded symbols. It's possible to display essentially any attribute known to Exiv2. Please see http://exiv2.org/metadata.html This brings two new functions that can be called from templates: * get_exif_value (exiv2_attribute) * get_exif_value_fixed (exiv2_attribute) Both functions take a string argument of metadata attribute name from Exiv2 namespace. The difference is that get_exif_value_fixed() does some extra formatting for several basic attributes (e.g. datetime format).
2011-06-04Port fullsize image link to the new defines systemTomas Bzatek1-2/+2
2011-06-04Port EXIF table visibility switch to the new defines systemTomas Bzatek1-2/+2
2011-06-04Port border style to the new defines systemTomas Bzatek1-1/+1
This change allows greater flexibility for separate themes.
2011-05-29Introduce new theming systemTomas Bzatek1-0/+76
This extends current templating system to another dimension, bringing the possibility to have multiple themes generated at once. The purpose is to be able to switch between multiple designs, from PC to mobile, classic vs. flat view, slideshow, etc. For the moment, only the classic theme is available. Rules: * for switching between themes, place a link inside your template manually - it's not a cgg concern, only your theming infrastructure * don't forget to define different file names for index and album pages across different themes * it's recommended to keep default theme named as "index.*" to avoid showing directory listing on webserver Notes: * some TODOs will be fixed when we have new theme using these advanced features (e.g. pictures in album pages) * TODO: introduce tag/block conditional system, allow custom user defines for each theme/page * TODO: deprecate <show_go_up>, <show_exif_table> and <border style> in favor of conditionals (these tags belong to theming)