| Age | Commit message (Collapse) | Author | Files | Lines |
|
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).
|
|
This adds a support for custom (registered) functions that can be called
from templates with specified arguments.
The syntax is as follows:
<!-- $(function_name(arg1, "arg2", 'arg3')) -->
Arguments are separated by a comma and can be quoted (recommended).
Quoted arguments are allowed to contain a comma as well as another
quote when escaped with a backslash.
To call a function with no arguments just do "function_name()".
Functions are supposed to be registered before actual data are parsed
and are called back from within the parser cycle.
|
|
|
|
|
|
This comes with a cost of decoding full image when only getting image size.
|
|
|
|
|
|
|
|
This change allows greater flexibility for separate themes.
|
|
And also bring back glib/gprintf.h include for g_vasprintf().
|
|
This allows actual defines to be used without explicit update.
Also brings the benefit of placing empty string when define is not defined.
|
|
This is very basic scripting support - simple value retrieval and
block conditionals. Defines could be either static from theme setup
or programatically added during page generation.
|
|
|
|
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)
|
|
Some blocks such as "IMG_LIST" are containers themselves and no data
are retrieved from them. That way they don't ever get marked as used,
resulting in constant hit in the generator loop.
|
|
|
|
And convert it to use global path info.
|
|
No need to store generated data during thread work anymore.
|
|
|
|
This has a nice side effect of not having double slashes in paths anymore.
|
|
This will allow us to pass detailed path info to worker methods.
Each path info instance is bound to a currently processed album
and directory.
Possibly move to struct TItems in the future.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Silly me, this can be easily done at once.
|
|
Disabled by default, only very simple center crop implemented.
The SQUARED_SIMPLE_SHAVE_AMOUNT constant may be slightly adjusted
according to future experience. It's a really dumb algorithm which
may not be suitable for every picture.
Looking for a fast and smart algorithm to determine image weight center
and radius, i.e. focus on object of interest. The OpenCV's face recognition
features are worth to test and consider, though I fear the speed issues.
|
|
|
|
|
|
|
|
|
|
mktime() modifies tm_wday and tm_yday to correct values.
|
|
This option takes the highest priority
|
|
Also print the setup file path in verbose mode.
|
|
|
|
|
|
This will fix all outstanding multithreading issues, coming from
statically allocated memory, common for all threads.
The algorithms have been further extended to allow input of any size.
|
|
|
|
Also fix forgotten two struct members :-o
|
|
Another step to get rid of writes to unlocked objects during threading.
|