| Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
This change will allow certain blocks to be present multiple times
and processed independently within a single page.
|
|
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.
|
|
All image sizes are now equal, no special treatment (except of
thumbnails).
|
|
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.
|
|
This adds commandline argument --debug-warn-resize that is useful
for debugging image resizing, particularly for detecting unintended
supplied image resizes.
|
|
Needed for struct tm.tm_gmtoff
|
|
Used by the new fluid theme.
|
|
Useful to override previous camera owner name stored in EXIF.
|
|
This brings support for copying whole directories when specified in
album extra files or template supplemental files.
|
|
Both MagickWand and exiv2 needs some initialization and cleanup, move
it to jpeg-utils for clean includes in cgg.c.
Also add explicit exiv2 XMP initialization as stated on
http://dev.exiv2.org/projects/exiv2/wiki/Thread_safety:
"The XMP SDK initialization function is not mutex protected, thus
Exiv2::XmpParser::initialize is not thread-safe. Therefore, multi-threaded
applications need to ensure that this XMP function is serialized, e.g.,
by calling them from an initialization section which is run before any
threads are started."
See also https://bugs.kde.org/show_bug.cgi?id=166424
|
|
Logical issue, found by a gcc-5.2.0 warning.
|
|
Turned out that we shouldn't blindly copy all metadata from the supplied
external EXIF file since they belong to a different image. This includes
image size, JPEG compression parameters, rotation etc.
This commit adds tag filtering so that not all tags are copied, retaining
the important ones from the gallery image.
The list of retained tags is by no means complete and is subject to future
tweaks. For the moment this feature is recommended to be turned off (and
is by default).
|
|
|
|
The returned number corresponds with the next picture item ID, for templates
to present related information (i.e. section beginning) for the particular
picture.
|
|
|
|
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.
|
|
Users are not really supposed to hit any of them, it would indicate
a programmer mistake otherwise.
|
|
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).
|
|
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.
|
|
|
|
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.
|
|
callback
|
|
... just a matter of personal taste.
Note: this breaks the template API only in current unreleased versions.
|
|
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).
|
|
Turned out there was no need for having most of the picture page
closed in a block.
|
|
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.
|
|
|
|
As per rules defined in the sample default.xml setup file the whole
<picture> theme definiton block is not mandatory anymore. The rest
of the code plays nicely already.
|
|
This mode retains given aspect ratio and crops the area from inside of the
source image.
|
|
|
|
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
|
|
|
|
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.
|
|
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.
|
|
Let's make it mandatory for now.
|
|
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.
|
|
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.
|
|
There were lots of errors reported for the same issue recently, let's
silence some and only report image copy/resize errors.
|
|
To allow combined use of different cgg versions, user may provide
ver. 2 setup.xml file that takes priority over standard setup.xml
file.
This applies only to current working directory, not the files
placed in ~/.cgg or distributed as $PREFIX/share/cgg.
|
|
This commit makes setup files (setup.xml and referenced design
setup xml file) versioned and adds checks for correct versions.
If a newer versioned file is detected, warning is printed out
in assumption that a stray cgg version is used.
If the version information is missing or is lower than expected
version, files are read in legacy mode. Some values are left
on defaults and missing mandatory values are either read from
renamed keys or made up to suit current requirements.
This essentially brings back compatibility with old setup.xml
files that are usually part of galleries.
However, some values are hardcoded and should be kept in mind
to update and test the legacy mode along with future enhancements.
|
|
This is a file format break within development branch.
|
|
Some cameras have the Exif.CanonSi.0x000c tag present but set to zero
(raw value). Since this would result in some -128 deg. C, ignore such
values.
|
|
|
|
Similar to using supplied timestamps this is useful for fully manual
lenses that don't provide any information to the camera.
|
|
This removes associated ICC profiles and such, though we should
perform proper colorspace conversion to plain (s)RGB first.
|
|
Turned out the Exif.Image.DateTime key may contain original timestamp
in some cases, e.g. when using extracted EXIF data from original image.
Since we can't trust this key has ever been modified by a photo software,
let's modify it together with other keys. It comes with a cost of changing
correct timestamp but we can't really distinguish that.
|
|
The gthread library has been merged in glib and the threading API has changed
a little. Since changes are negligible, there's no point of losing support
of older glib releases, thus make it conditional.
|
|
https://live.gnome.org/GnomeGoals/ModernAutotools
Big thanks to Pavel Raiskup for autoconf hints
|
|
|