summaryrefslogtreecommitdiff
path: root/src/generators.c
AgeCommit message (Collapse)AuthorFilesLines
2016-10-18generators: Take the optional shave amount in account for dimension calculationTomas Bzatek1-0/+7
2016-10-04items: Add option to shave image bordersTomas Bzatek1-0/+2
A workaround for badly exported images that contain some garbage at the borders. The amount specifies how many pixels should be shaved from all borders (i.e. amount of 2 results in 4x4 pixels loss). Applicable for particular items or whole album (<general> section) with the following syntax: <shave amount="1" />
2016-10-02Add support for HiDPI imagesTomas Bzatek1-65/+129
This works by creating corresponding hidpi image sizes on startup and letting the machinery generate high resolution images from the source images (no way to use supplied images). However since browsers expect exact image dimension multiples for the particular scale factor, a reference image size (scale factor 1.0x) must be read first, then cropped to match reference aspect ratio and resized to exact dimensions. That way pixel-perfect results can be achieved for the chosen scale factor. TODO: the CSS background-image: image-set() tags are not supported on Firefox. TODO: try the 1.5x scale factor
2016-10-02generators: Don't read EXIF data for all image sizesTomas Bzatek1-1/+1
EXIF data were read in cases where weren't even used.
2016-10-02jpeg-utils: Add support for custom resize optionsTomas Bzatek1-1/+2
This change brings the possibility to tweak resize options using standard ImageMagick `convert` command syntax. Separate options are offered for thumbnails.
2016-09-23generators: Make image quality threshold inclusiveTomas Bzatek1-1/+1
(95% + 5% threshold == 100% source image quality acceptance)
2016-09-23generators: Expose all image sizesTomas Bzatek1-12/+55
A new block LIST_PICTURE_ALL_SIZES has been introduced to expose all available image sizes when iterating through the album items. Image size availability can be tested by the HAVE_IMG_SIZE_xxx define where "xxx" is an upper-case image size name as defined in the theme XML file. Similarly the image standard tags IMG_SIZE_W__xxx, IMG_SIZE_H__xxx and IMG_SRC__xxx have been introduced as well.
2016-09-19block-parser: Clear processed data for further useTomas Bzatek1-3/+11
This change will allow certain blocks to be present multiple times and processed independently within a single page.
2016-09-18Introduce resizing thresholdsTomas Bzatek1-124/+198
This commit brings deeper changes to the image sizes concept. The goal was to allow more flexible input in resizing vs. supplied files mixed mode. Instead of hard <noresize> flags the decision whether to resize or copy an image is now based on threshold. While not 100% universal, it brings more control regarding image size bounds. Also brings a level of tolerance for specific errors (off-by-one exports). Image sizes' rules are a bit simpler, hopefully easier to understand. A lot can be achieved by combination of thresholds.
2016-09-17Drop explicit references to "original" and "preview" image sizesTomas Bzatek1-38/+42
All image sizes are now equal, no special treatment (except of thumbnails).
2016-09-17Drop legacy nofullsize and album width/height/quality tagsTomas Bzatek1-86/+21
This drops the legacy functionality that doesn't really fit into the new flexible design concept and makes code unnecessarily complicated. Most of these overrides affected only the "preview" image size anyway. This also makes the <item src> attribute mandatory as it's being the only source of metadata (unless overriden or supplied externally). This unfortunately breaks the so-far 100% album XML files compatibility.
2016-09-11generators: Optionally warn when an image is being resizedTomas Bzatek1-3/+8
This adds commandline argument --debug-warn-resize that is useful for debugging image resizing, particularly for detecting unintended supplied image resizes.
2016-04-03jpeg-utils: Override artist and owner nameTomas Bzatek1-0/+1
Useful to override previous camera owner name stored in EXIF.
2015-02-01generators: Expose ITEM_INDEX value for non-picture itemsTomas Bzatek1-1/+4
The returned number corresponds with the next picture item ID, for templates to present related information (i.e. section beginning) for the particular picture.
2015-02-01theming: Introduce image size fallback modeTomas Bzatek1-35/+58
This changes image size handling a little bit. An optional <fallback size="xxx" /> tag tells the generator to use different image size when an image for the current image size has not been supplied from the album XML file. This is effectively used for the legacy <nofullsize> tag fallback. More generally this is useful for templates showing additional image sizes. Also saves space as images not having the custom size supplied are not generated from the source image.
2015-01-30theming: Fix the have_image_size() nofullsize testTomas Bzatek1-4/+0
The "original" image size presence should not really be reported when the "preview" image size substitutes it due to its absence (not defined in the album XML file).
2015-01-30theming: Implement have_album_image_size() block functionTomas Bzatek1-0/+37
Similar to the have_image_size() block function this is its variation operating over the album. The block condition is true if there's at least one item in the album of the specified image size. Respects the legacy "nofullsize" tags. Takes one mandatory argument of image size name.
2015-01-25theming: Implement have_image_size() block functionTomas Bzatek1-0/+45
This can be used to query image size availability for the current item. While images are normally generated for theme-defined image sizes and thus guaranteed to be available, this function queries if the image of defined size has really been supplied in album XML files. Takes in account the legacy "nofullsize" tags. Takes one mandatory argument of image size name.
2015-01-25block-parser: Enhance block_parser_register_function() with a destroy notify ↵Tomas Bzatek1-13/+6
callback
2015-01-25generators: Rename HAS_ conditionals to HAVE_Tomas Bzatek1-4/+4
... just a matter of personal taste. Note: this breaks the template API only in current unreleased versions.
2015-01-25theming: Make custom image size handling fully flexibleTomas Bzatek1-53/+44
This commit brings full flexibility of custom image size definition and usage. When a custom image size is defined, it automatically maps to the album <item> tag arguments. Alternatively, this automatic name matching can be overriden by <size tagname="..."> theme setup tags. This allows us to supply image of different sizes that can be also used in templates. Legacy behaviour of "fullsize" and "preview" image size fallback is retained (though not recommended in new theming setups).
2015-01-11generators: Remove unnecessary picture page global blockTomas Bzatek1-25/+14
Turned out there was no need for having most of the picture page closed in a block.
2015-01-11generators: Allow undefined album image and thumbnail sizesTomas Bzatek1-76/+77
There may be certain cases where images or thumbnails on album pages are not needed and textual representation is just fine. Metadata pulled from the source image files are still processed and exposed.
2015-01-04Introduce new "fixed" thumbnail crop modeTomas Bzatek1-4/+15
This mode retains given aspect ratio and crops the area from inside of the source image.
2015-01-04generators: Newline at the end of generated .htaccess fileTomas Bzatek1-1/+2
2015-01-04generators: Use single function for all templatesTomas Bzatek1-526/+537
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-18generators: Separate common code outTomas Bzatek1-142/+136
2014-09-17theming: Make navigation bar strongly themedTomas Bzatek1-81/+169
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.
2014-09-15theming: Allow themes to use different thumbnail image sizesTomas Bzatek1-60/+44
This change makes thumbnail image sizes more flexible by explicitly stating the particular image size is a thumbnail. And each thumbnail image size can have different squared settings. On the theme side it's now mandatory to specify which thumbnail size to use (if applicable). This allows us to have different thumbnail styles for index and album pages. This commit also removes the <squared_thumbnails> tag from setup.xml file but retains fallback for ver. 1 setup.xml files.
2014-09-15theming: Define meaning of the <no_resize> tagTomas Bzatek1-1/+1
Although probably not very common scenario, let's be consistent across all defined image sizes and clearly state that an explicitly supplied image file for an optional image size should carry the tag in order not to get resized.
2014-09-13Introduce properties tableTomas Bzatek1-38/+33
This is a new internal properties storage for attributes that can be defined both in the item and album scope, with the item scope taking priority. The big advantage is a better distinguishment from an undefined, default value. It also makes easier to retrieve attributes with properly defined scope priorities.
2014-03-22Make error reporting nicer when referenced image is not availableTomas Bzatek1-10/+28
There were lots of errors reported for the same issue recently, let's silence some and only report image copy/resize errors.
2014-03-18Use "override" terminology instead of "fake"Tomas Bzatek1-9/+9
This is a file format break within development branch.
2014-03-18Allow absolute pathnames for external EXIF dataTomas Bzatek1-2/+2
2014-03-18Add support for specifying custom focal length and apertureTomas Bzatek1-0/+8
Similar to using supplied timestamps this is useful for fully manual lenses that don't provide any information to the camera.
2013-04-07Add ability to specify thumbnail square crop hintTomas Bzatek1-4/+11
In simple crop square mode it's sometimes viable to specify position of the square. This is vastly useful for portrait pictures so that you don't crop the head off the body.
2013-04-07Use rel="home" for links pointing to gallery rootTomas Bzatek1-2/+2
Hopefully some browsers would understand that. http://microformats.org/wiki/existing-rel-values
2013-04-07Strip unused template tags by defaultTomas Bzatek1-0/+3
If there's a tag defined but not used on replace table processing, this option determines whether it should be written in the generated file or ignored completely. Turned on by default, this will save a few bytes. Use commandline option '--debug-dont-strip-unused-tags' to turn it off, e.g. when debugging template files.
2013-03-16Strip XMP metadata by defaultTomas Bzatek1-1/+1
Some RAW editors like Adobe products like to include XMP data. Let's strip them all off (unless disabled).
2013-03-16Add support for writing external EXIF metadata back to imagesTomas Bzatek1-2/+10
Turned off by default, this will copy all data from supplied external EXIF metadata file back to all generated image files. All user overrides are still applied on top of it. Another reason for turning this off is file size concern, target image files would carry a lot more information that may not be always needed and would increase total amount of data transferred.
2013-03-10Add support for specifying custom dateTomas Bzatek1-0/+3
This essentially means faking the datetime, e.g. when you want to mask original picture date. This commit also changes little bit of datetime conversion, hopefully fixing DST issues. Needs more testing.
2013-03-10Add support for datetime/timezone shiftTomas Bzatek1-2/+24
Simple datetime shift, including EXIF data modification.
2013-02-10Show note for password protected albums on index pagesTomas Bzatek1-0/+1
Also adds IS_PROTECTED define in local item scope.
2013-02-10generators: Process image blocks through local block parsersTomas Bzatek1-21/+31
This change allows using local defines related to each item in the album or index page.
2013-02-10Support theme-defined thumbnail for protected albumsTomas Bzatek1-11/+26
2012-12-31Add support for password protected albumsTomas Bzatek1-0/+76
This adds support for simple password protected areas (albums and all subalbums) through webserver HTTP authentication. CGG simply generates .htaccess and password files and it's up to the user to set up the rest on server side. No UI changes at this point. Limited to one user per album for the moment.
2012-12-27Support external EXIF metadataTomas Bzatek1-2/+10
This brings an ability to specify external file to read EXIF/IPTC data from. The motivation was to work around RAW editors randomly stripping some EXIF blocks.
2012-12-24Add has_exif_key() block functionTomas Bzatek1-0/+13
Simple check whether the EXIF/IPTC key is available for the current image. Precisely one argument is required, similar to the get_exif_value() custom function, an Exiv2 metadata attribute string is expected. This allows templates to change behaviour when certain metadata key is not present (e.g. don't print the particular table line at all).
2012-04-15Add HAS_EXIF defineTomas Bzatek1-0/+5
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-28/+43
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).
generated by cgit v1.2.3 (git 2.46.0) at 2026-01-12 15:29:30 +0000