-copyright: "Except where otherwise noted, content on this site is licensed under a [Creative Commons Attribution 4.0 International license](https://creativecommons.org/licenses/by-sa/4.0/)."
+digiKam is an advanced open-source digital photo management application that runs on Linux, Windows, and macOS X. The application provides a comprehensive set of tools for importing, managing, editing, and sharing photos and raw files.
+
+### Highlights
+
+You can use digiKam's import capabilities to easily transfer photos, raw files, and videos directly from your camera and external storage devices (SD cards, USB disks, etc.). The application allows you to configure import settings and rules that process and organize imported items on-the-fly.
+
+digiKam organizes photos, raw files, and videos into albums. But the application also features powerful tagging tools that allow you to assign tags, ratings, and labels to photos and raw files. You can then use filtering functionality to quickly find items that match specific criteria.
+
+In addition to filtering functionality, digiKam features powerful searching capabilities that let you search the photo library by a wide range of criteria. You can search photos by tags, labels, rating, data, location, and even specific EXIF metadata. You can also combine several criteria for more advanced searches.
+
+digiKam can handle raw files, and the application uses the excellent [LibRaw](https://www.libraw.org/) library for decoding raw files. The library is actively maintained and regularly updated to include support for the latest camera models.
+
+The application provides a comprehensive set of editing tools. This includes basic tools for adjusting colors, cropping, and sharpening as well as advanced tools for lens correction, curves adjustment, panorama stitching, and much more.
+
+Extended functionality in digiKam is implemented via [Kipi plugins](https://projects.kde.org/projects/extragear/graphics/kipi-plugins). These plugins are shared by other KDE applications, including [Gwenview](https://userbase.kde.org/Gwenview) and [KPhotoAlbum](https://www.kphotoalbum.org/). You can easily customize digiKam by enable and disable individual plugins.
-digiKam is an advanced digital photo management application for Linux, Windows, and Mac-OSX.
-
-The people who inspired digiKam's design are the photographers like you who want to view, manage, edit, enhance, organize, tag, and share photographs under Linux systems.
-
-You can take a look into the digiKam <a href="?q=about/overview">Overview</a> page to take a tour or the <a href="?q=about/features">Features</a> page to see more advanced information about.
- <li><a href="http://digikam3rdparty.free.fr/Documents/TuxMagazineArticle-digiKam.pdf">Article from Tux Magazine</a></li>
-
- <li><a href="http://digikam3rdparty.free.fr/Documents/LPMagazineArticle-digiKam.pdf">Article from Linux Pratique (French)</a></li>
-
- <li><a href="http://digikam3rdparty.free.fr/Documents/LXFMagazineArticle-digiKam.pdf">Article from Linux Format Magazine</a></li>
-
-</ul><p></p>
-<br><b>2006</b><br>
-<p></p><ul>
-
- <li><a href="http://cyberborean.wordpress.com/2006/04/27/tools-digikam-manage-your-photos">Article from Cyberborean Chronicles : Manage your photos</a></li>
-
- <li><a href="http://www.gienux.org/site/index.php?itemid=77">Article from gienux.org : gérer vos photos et images numériques (French)</a></li>
-
- <li><a href="http://canllaith.org/?page_id=16">Blog from Canllaith.org : Photography management using digiKam 0.8.2</a></li>
-
-</ul><p></p>
-<br><b>2007</b><br>
-<p></p><ul>
-
- <li><a href="http://linux.vilars.com/dotclear/index.php?2007/01/03/6-color-management-workflow-using-digikam"> Blog from Nicolas Vilars : Color Management Workflow using digiKam 0.9.0</a></li>
-
- <li><a href="http://linux.vilars.com/dotclear/index.php?2007/01/08/8-io-files-settings-advanced-options-how-to-get-the-most-out-of-your-pictures"> Blog from Nicolas Vilars : RAW files decoding settings using digiKam 0.9.0</a></li>
-
- <li><a href="http://www.szdavid.com/wordpress/2007/01/05/digikam-09-la-classe/">Blog from Szdavid: digiKam 0.9 la classe (French), report from a gnome user</a></li>
-
- <li><a href="http://www.declencheur.com/clic/archives/2007/03/digikam-le-catalogueur-libre">Gilles Caulier interview in French about digiKam 0.9.x (podcast from declencheur.com)</a></li>
-
- <li><a href="http://www.linuxgraphics.ru/news.php?readmore=407">digiKam 0.9.2 review by Alexandre Prokoudine (Russian)</a></li>
-
- <li><a href="http://www.mscgizcast.com/2007/06/msc-giz-cast-episode-15-digikam.html">Podcast about an Ubuntu user which use digiKam</a></li>
-
- <li><a href="http://www.nautile.org/Utilisation-basique-de-Digikam.html">Notice for beginners about to use digiKam (French)</a></li>
-
- <li><a href="/?q=node/239">digiKam 0.9.2 favorably compared by c't magazine #14 to Kphotoalbum, Gthumb, F-Spot, Picasa (German)</a></li>
-
-<li><a href="http://www.freesoftwaremagazine.com/articles/manage_your_photos_with_digikam">Article from freesoftwaremagazine.com about how to manage your photos with digiKam 0.9.2</a></li>
-
-<li><a href="http://www.linuxplanet.com/linuxplanet/tutorials/6424/1">Article from linuxplanet.com about digital photo-management using digiKam</a></li>
-
-<li><a href="http://www.xwing.info/index.php?p=digikam">Tutorials from xwing.info about Raw Workflow and Color Management under digiKam (French)</a></li>
-
-<li><a href="http://www.associatedcontent.com/article/223272/digikam_an_iphoto_replacement_for_linux.html">digiKam: an iphoto replacement for Linux</a></li>
-
-</ul><p></p>
-<br><b>2008</b><br>
-<p></p><ul>
-
-<li><a href="http://polishlinux.org/kde/kde-4-tour-digikam-010">digiKam 0.10: port to KDE4 review</a></li>
-<li><a href="http://blog.roozeec.fr/2008/07/02/album-photo-picassaweb-et-digikam">digiKam and PicasaWeb export plugin (French)</a></li>
-
-<li><a href="http://www.ubuntuproductivity.com/journal/ubuntu/07/2008/ubuntu-photo-manager-experiment/">digiKam is not even considered in this FOSS for photos review, but read the reader comments!</a></li>
-
-<li><a href="http://www.kdedevelopers.org/node/3612">digiKam Levels adjust tutorial by Unai Garro</a></li>
-
-<li><a href="http://www.kdedevelopers.org/node/3618">digiKam Curves adjust tutorial by Unai Garro</a></li>
-
-<li><a href="http://www.kdedevelopers.org/node/3655">digiKam White Balance tutorial by Unai Garro</a></li>
-
-<li><a href="http://www.ugarro.com/blog/blog4.php/2008/09/06/photo-kde-tutorial-1-4-brightness-contra">digiKam Brightness/Contrast/Gamma and Hue/Saturation/Lightness tutorial by Unai Garro</a></li>
-
-<li><a href="http://njanes.free.fr/wordpress2/?p=33">How to install pre-compiled digiKam under Microsoft Windows (French)</a></li>
-<li><a href="http://www.jesusda.com/blog/index.php?id=284">How to create a Calendar with digiKam (Spanish)</a></li>
-<li><a href="http://colegota.fotolibre.net/como/como-georreferenciar-vuestas-fotos-con-rutas-gps-y-digikam/">How to geolocalize images with digiKam (Spanish)</a></li>
-<li><a href="http://larrazun.blogspot.com/2009/01/ordenando-nuestras-fotografias.html">Introduction to digiKam for KDE4 (Spanish)</a></li>
-<li><a href="http://ningning.org/blog2/2009/02/09/software-review-digikam-linux-users-lightroom">digiKam: Linux User’s Lightroom ++</a></li>
-<li><a href="http://maketecheasier.com/use-digikam-export-photos-flickr-picasaweb-and-facebook/2009/09/14">How to Use digiKam 1.0.0 to Export Photos to Flickr, PicasaWeb, and Facebook</a></li>
-<li><a href="http://www.shutter-speed.ch/wordpress/?p=887">digiKam review in German</a></li>
-How to make Pseudo HDR image with digiKam</a></li>
-<li><a href="http://www.linux-magazine.com/Online/Blogs/Productivity-Sauce-Dmitri-s-open-source-blend-of-productive-computing/Perfect-Cloud-based-Photo-Setup-with-digiKam-and-Piwigo">digiKam and Piwigo export</a></li>
-<li><a href="http://scribblesandsnaps.wordpress.com/2010/06/03/renaming-photos-with-digikam">Mass files renaming in digiKam</a></li>
-<li><a href="http://scribblesandsnaps.wordpress.com/2010/08/30/correct-lens-distortion-with-digikam">Lens auto correction with digiKam</a></li>
-<li><a href="http://www.sanderdekievit.nl/blog/?cat=10">digiKam versus Aperture</a></li>
-<li><a href="http://www.ghacks.net/2010/09/11/manage-your-digital-camera-in-linux-with-digikam" "="">Manage your digital camera with digiKam</a></li>
-<li><a href="http://scribblesandsnaps.wordpress.com/2010/06/18/improve-photos-with-digikams-local-contrast-tool">Improve image with Local Contrast tool from digiKam image editor</a></li>
-<li><a href="http://www.grainworks.eu/wp/180/photography/photo-workflow-in-linux-with-digikam">Photo work-flow with digiKam</a></li>
-<li><a href="http://scribblesandsnaps.wordpress.com/2010/10/15/using-digikam-with-mysql">Using Mysql with digiKam</a></li>
-<li><a href="http://www.thephotoargus.com/freelance/introduction-to-digikam">Introduction to digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=587">Wavelets Noise Reduction with digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=587">Reducing Noise Using digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=616">Geotag Photos With digiKam</a></li>
-<li><a href="http://scribblesandsnaps.wordpress.com/2011/02/16/geotag-photos-with-open-gps-tracker-and-digikam">How to use Android Open-GPS-Tracker with digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=688">How to geo-localize your photo with GoogleMaps under digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=711">Straighten Your Pictures Using digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=639">How to find duplicate images on digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=595">Face Detection In digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=735">Creating Calendars Using digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=723">Remove Red Eyes From Your Pictures Using digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=750">Applying Image Effects Using digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=761">Batch Rename Photos In digiKam</a></li>
-<li><a href="http://www.mohamedmalik.com/?p=755">Re-compress Images Using digiKam</a></li>
-<li><a href="http://chrisharvey.id.au/geotagging-ubuntu-and-nikon-nef-with-digikam>Geotagging NEF with digiKam (including screencast)</a></li>
-<li><a href=" http:="" tutorialgeek.blogspot.com="" 2011="" 02="" how-to-add-watermarks-in-batch-to-your.html="">How to Add Watermarks in batch to Your Photos with digiKam</a></li>
- Support for RAW pictures using <a href="http://www.libraw.org">LibRaw</a> included in libKdcraw<br>
- Support of more 800 proprietary RAW camera file formats.<br>
- Complete camera list is given <a href="http://lxr.kde.org/source/KDE/kdegraphics/libs/libkdcraw/libraw/src/libraw_cxx.cpp#1584">here</a>
- </li></ul>
- </td>
- <td width="40%" align="right">
- </td>
- </tr>
- <tr>
- <td width="60%">
- <ul><li>
- Easy comparing similar pictures using Light Table:
- <ul>
- <li>Files displayed side by side</li>
- <li>Synchronized panning and zooming</li>
- <li>Navigation by pair</li>
- <li>Raw files support</li>
- </ul>
- </li></ul>
- </td>
- <td width="40%" align="right">
-
- </td>
- </tr>
- <tr>
- <td width="60%" align="left">
- <ul><li>
- digiKam core, image editor and image filters support 16 bits color depth pictures (RAW, TIFF, PNG, JPEG2000).<br>
- Image Editor has a full Color Management support using ICC color profiles.
- </li></ul>
- </td>
- <td width="40%" align="right">
- </td>
- </tr>
-
- <tr>
- <td width="60%" align="left">
- <ul><li>
- Thumbnail sizes can be adapted to your screen size on the fly
- </li></ul>
- </td>
- <td width="40%" align="right">
- </td>
- </tr>
-
- <tr>
- <td width="60%" align="left">
- <ul><li>
- Sidebar used everywhere to display
- <ul>
- <li>metadata
- <ul>
- <li>Image information</li>
- <li>Metadata</li>
- <li>Geolocation</li>
- </ul>
- </li>
- <li>image file properties
- <ul>
- <li>comments/tags/rating/date</li>
- <li>tag filter information</li>
- <li>colors information: histogram and ICC profile</li>
- </ul>
- </li>
- </ul>
- </li></ul>
- </td>
- <td width="40%" align="right">
- </td>
- </tr>
-
- <tr>
- <td width="60%" align="left">
- <ul><li>
- Fast preview pictures mode embedded into albums interface with zoom and panning features
- </li></ul>
- </td>
- <td width="40%" align="right">
- </td>
- </tr>
-
-</tbody></table>
-
-<h1>Plugins architectures</h1>
+### Summary
+
+The following is a concise overview of features and tools available in digiKam. The application covers the photographic workflow consisting of five major stages:
+
+* Import photos, raw files, and videos
+* Organize your library
+* Browse and view items in the library
+* Process and edit raw files and photos
+* Share and publish photos
+
+#### Import
+
+* Support for all digital camera models that [work with Gphoto2](http://www.gphoto.org/proj/libgphoto2/support.php)
+
+* Import module supports the following actions:
+ * Delete images
+ * Upload images
+ * Lock images
+ * Auto-rename pictures during import
+ * Auto-rotate pictures during import
+ * Auto-creation of albums during import
+ * Lossless conversion during import
+ * Show camera information
+
+#### Organize
+
+* Group photos, raw files, photos, and videos into albums and sub-albums
+* Add tags and comments to albums
+* Sort albums by folder, category, and creation date
+* Sort items in albums by name, path, date, and file size
+* Filter album items by rating, filename, file type, tags, and labels
+
+### View
+
+* Support for RAW pictures using [LibRaw](http://www.libraw.org) included in libKdcraw
+ Support of more 800 proprietary RAW camera file formats.
+ Complete camera list is given [here](http://lxr.kde.org/source/KDE/kdegraphics/libs/libkdcraw/libraw/src/libraw_cxx.cpp#1584)
+
+* Easy comparing similar pictures using Light Table:
+ * Files displayed side by side
+ * Synchronized panning and zooming
+ * Navigation by pair
+ * Raw files support
+
+* digiKam core, image editor and image filters support 16 bits color depth pictures (RAW, TIFF, PNG, JPEG2000). Image Editor has a full Color Management support using ICC color profiles.
+* Thumbnail sizes can be adapted to your screen size on the fly
+* Sidebar used everywhere to display
+ * metadata
+ * Image information
+ * Metadata
+ * Geolocation
+ * image file properties
+ * comments/tags/rating/date
+ * tag filter information
+ * colors information: histogram and ICC profile
+
+* Fast preview pictures mode embedded into albums interface with zoom and panning features
+
+### Plugins architectures
To ease development and to share code with other applications, digiKam make use of kipi-plugins architecture.
- <li>Lossless transformations with JPEG pictures</li>
- <li>Add GPS coordinates to images by synchronizing them with a GPX files (created by GPS receivers and/or GPS tools), or by manually editing the longitude/latitude/altitude or also by using Google Map capabilities.</li>
- <li>Acquire image (eg. with a flat scanner)</li>
+* Export to [PicasaWeb](http://picasaweb.google.com)
+* Export to [SmugMug](http://www.smugmug.com)
+* Export to [Piwigo](http://piwigo.org/)
+* Import From/Export to [FaceBook](http://www.facebook.com)
+* Import From/Export to [Shwup](http://www.shwup.com)
+* Export to [Zooomr](http://www.zooomr.com)
+* Export to [Gallery](http://gallery.menalto.com) powered websites
+* Export to [KML](http://code.google.com/intl/fr-FR/apis/kml/documentation/)
+* Export to a local directory or remote computer using KIO protocols (ftp, ssh, smb, fish, svn, tar ...)
+
+### Create
+
+* Calendar creation wizard
+* Print wizard
+* Create slideshow
+
+### Other tools available in digiKam core
+
+* Lossless transformations with JPEG pictures
+* Add GPS coordinates to images by synchronizing them with a GPX files (created by GPS receivers and/or GPS tools), or by manually editing the longitude/latitude/altitude or also by using Google Map capabilities.
+* Acquire image (eg. with a flat scanner)
+* RAW image converter
+* DNG converter
+* Adjust time and date
+* Edit Pictures Metadata
+* Create slideshow
+* Images batch processing
+
+### Edit
+
+* Fast image editor with keyboard shortcuts and basic photo editing/management features without losing metadata. Features available in Image editor are:
+ * 16 bits image color depth support.
+ * RAW camera image support.
+ * Histogram viewer
+ * Color Management support.
+ * ICC profiles tool to perform advanced color corrections into images
+ * ICC profile viewer
+ * Exporting to another image format
+ * Removing images from current Album
+ * Image comments editing
+ * Image file properties
+ * EXIF/MakerNote/IPTC/GPS viewer
+ * Zooming
+ * Printing images
+
+* Red eyes correction
+* Brightness / Contrast / Gamma correction
+* Hue / Saturation / Luminosity correction
+* Color balance
+* Invert colors
+* Color auto-correction tools: Normalize / Equalize / Auto levels / Stretch Contrast
+* Blur / Sharpen
+* Ratio-cropping with proportion aids and composing tools based on Fibonacci rules
+* Free cropping
+* Black and White and tonality converter using curves adjustments
+* Rotation
+* Flipping
+* Adjust levels : a tool to adjust the photograph histogram levels manually
+* Adjust curves : a tool to adjust the photograph colors using curves
+* Noise Reduction : noise filter based on wavelet algorithm
+* Liquid Rescale : content aware resizing to change ratio of a picture while keeping the content intact
+* Local Contrast : a pseudo HDR-tonemapping tool to recover highlights and shadows while keeping local contrast
+* Unsharp Mask : a photograph unsharp mask filter to unblur picture without increase noise
+* Lens Distortion : a tool for correct lens spherical aberration on photograph
+* Vignetting : a tool for removing or adding vignetting on photograph
+* Channel Mixer : a tool to mix the photograph color channels
+* White Balance : a tool to adjust white color temperature balance of photograph
+* Photograph Inpainting : a tool to remove unwanted photograph area using CImg library
+* Photograph Refocus : a sharpness editor to refocus a photograph
+* Hot Pixels Correction : a tool to remove photograph hot pixels generated by a deficient camera
+* Photograph Restoration : a tool to reduce photograph artifacts using CImg library
+* Free Rotation : a plugin to rotate a photograph with a free angle in degrees
+* Shear Tool : a plugin to shear a photograph horizontally and vertically
+* Perspective Tool : a plugin to adjust the photograph perspective
+* Add Border : a tool to add decorative frame around a photograph
+* Insert Text : a tool to insert text under a photograph
+* Apply Texture : a tool to apply a decorative texture to a photograph
+* Solarize : a tool to solarize a photograph
+* Oil Paint : simulate oil painting on photograph
+* Emboss : an effect filter to emboss photograph
+* Rain Drops : adding the visual effect of raindrops on photograph
+* Charcoal : simulate charcoal drawing on photograph
+* Film Grain : simulate film grain on photograph
+* Infrared : simulate infrared film effect on photograph
+* Blur FX : apply blurring special effects on photograph
+* Distortion FX : apply distortion special effects on photograph
description: "A brief description of the digiKam sotware."
category: "about"
aliases: "/about/overview"
---
<div class="content"><h3>A digiKam Overview</h3>
<p>digiKam is an advanced digital <b>photo management application</b>, which makes importing and organizing digital photos a "snap". The photos are organized in albums which can be sorted chronologically, by folder layout or by custom collections.</p>
<a href="https://www.flickr.com/photos/digikam/5508779067" title="digiKamsc by Caulier Gilles, on Flickr"><img src="https://farm6.staticflickr.com/5055/5508779067_11c67b8a40_z.jpg" alt="digiKamsc" width="640" height="418"></a>
-<p>Tired of the folder constraints? Don’t worry, digiKam also provides <b>tagging</b>. You tag your images which can be spread out across multiple folders, and digiKam provides <a href="http://www.digikam.org/drupal/node/324">fast and intuitive ways</a> to browse these tagged images. You can also add comments to your images. digiKam makes use of a fast and robust database to store these meta-informations which makes adding and editing of comments and tags very reliable.</p>
+<p>Tired of the folder constraints? Don’t worry, digiKam also provides <b>tagging</b>. You tag your images which can be spread out across multiple folders, and digiKam provides <!-- a href="http://www.digikam.org/drupal/node/324" -->fast and intuitive ways<!-- /a --> to browse these tagged images. You can also add comments to your images. digiKam makes use of a fast and robust database to store these meta-informations which makes adding and editing of comments and tags very reliable.</p>
<p>digiKam makes use of <a href="https://projects.kde.org/projects/extragear/graphics/kipi-plugins">KIPI plugins </a>for lots of added functionalities. KIPI is an initiative to create a common plugin infrastructure for digiKam, <a href="http://ktown.kde.org/kimdaba">KPhotoAlbum</a>, and <a href="http://gwenview.sourceforge.net">GwenView</a>. Its aim is to allow development of image plugins which can be shared among graphical applications.</p>
-<p>An easy-to-use interface is provided that enables you to <a href="http://www.digikam.org/node/328">connect to your camera</a> and preview, download and/or delete your images. Basic auto-transformations can be deployed on the fly during image downloading.</p>
+<p>An easy-to-use interface is provided that enables you to <!-- a href="http://www.digikam.org/node/328" -->connect to your camera<!--/a --> and preview, download and/or delete your images. Basic auto-transformations can be deployed on the fly during image downloading.</p>
-<p>Another tool, which most artists and photographers will be familiar with, is a <a href="http://www.digikam.org/node/329">Light Table</a>. This tool assists artists and photographers with reviewing their work ensuring the highest quality only. A classical light table will show the artist the place on the images to touch up. Well in digiKam, the light table function provides the user a similar experience. You can import a photo, drag it onto the light table, and touch up only the areas that need it.</p>
+<p>Another tool, which most artists and photographers will be familiar with, is a <!-- a href="http://www.digikam.org/node/329" -->Light Table<!-- /a -->. This tool assists artists and photographers with reviewing their work ensuring the highest quality only. A classical light table will show the artist the place on the images to touch up. Well in digiKam, the light table function provides the user a similar experience. You can import a photo, drag it onto the light table, and touch up only the areas that need it.</p>
<a href="http://www.flickr.com/photos/digikam/2583231945/" title="frontpage by cauliergilles, on Flickr"><img src="http://farm4.static.flickr.com/3080/2583231945_311054dca4.jpg" alt="frontpage" width="500" height="388"></a>
-<p>The digiKam <b>Image Editor</b> has its own plugin subsystem with some <a href="http://www.digikam.org/drupal/node/325">common tools</a> e.g. red eye correction or colors correction. Additional plugins are provided with the main application to process <a href="http://www.digikam.org/node/327">advanced corrections</a> on image like color management, noise reduction, or special effects. digiKam Image Editor supports all camera RAW file formats, 16 bits color depth, Exif/Makernote/IPTC/GPS/XMP metadata, Color management, tagging/rating/comments pictures, etc.</p>
+<p>The digiKam <b>Image Editor</b> has its own plugin subsystem with some <!-- a href="http://www.digikam.org/drupal/node/325" -->common tools<!-- /a --> e.g. red eye correction or colors correction. Additional plugins are provided with the main application to process <!-- a href="http://www.digikam.org/node/327" -->advanced corrections<!-- /a --> on image like color management, noise reduction, or special effects. digiKam Image Editor supports all camera RAW file formats, 16 bits color depth, Exif/Makernote/IPTC/GPS/XMP metadata, Color management, tagging/rating/comments pictures, etc.</p>
-<p>A stand-alone image editor version named <a href="http://www.digikam.org/node/326">ShowFoto</a> is also available. It runs without digiKam images database support, but provides all Image Editor functions.</p>
+<p>A stand-alone image editor version named <!-- a href="http://www.digikam.org/node/326" -->ShowFoto<!-- /a --> is also available. It runs without digiKam images database support, but provides all Image Editor functions.</p>
-<p>You want to know more about digiKam? Continue to <a href="http://www.digikam.org/node/341">Features page</a>
+<p>You want to know more about digiKam? Continue to <a href="/about/features/">Features page</a>
-description: "All of the splashscreens from the digiKam releases!"
-category: "about"
-aliases: "/splashcreens"
----
-
-
-<div class="content"><h1>Notice To Contribe</h1>
-
-<p>You are a photographer, and you use digiKam to manage your collections. Why not to propose your best shots as splash-screens. It's your chance to join the ranks of the precious few who have had their artwork associated with a release of digiKam!</p>
-
-<p>Splash-screens are a simple way for users to contribute to the digiKam project. The pictures must be correctly exposed and composed, and the subject must be chosen using a real photographer inspiration.</p>
-
-<p>We need two new splash-screens: one dedicated to digiKam and another one to Showfoto. You can send us <a href="mailto: caulier dot gilles at gmail dot com">by e-mail</a> your color or black and white pictures, taken horizontally. We need only scaled-down photos. No need to put few marks about program name and version. We have two SVG templates <a href="http://inkscape.org/">created with Inkscape</a> for <a href="https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/raw/data/pics/splash-digikam.svgz">digiKam</a> and for <a href="https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/raw/data/pics/splash-showfoto.svgz">showfoto</a> to try your images with application logo and chart. Shots will be review by team and best selected...</p>
-
-<p>As example, see below the official digiKam and Showfoto splash-screens release used until now releases.</p>
-
-<p>Have fun to contribute to digiKam project... and thanks in advance...</p>
+Want to show your photos to thousands of digiKam users? Consider submitting your best photos for use with digiKam splash screen. This is also the easiest way to contribute to the digiKam project.
+
+We need two new splash screens: one for digiKam and another one for Showfoto. Send your photos in the landscape format to *caulier dot gilles at gmail dot com*. Do not add any text, watermark, or other elements to the photo.
+
+We have two SVG templates <a href="http://inkscape.org/">created with Inkscape</a> for <a href="https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/raw/data/pics/splash-digikam.svgz">digiKam</a> and for <a href="https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/raw/data/pics/splash-showfoto.svgz">Showfoto</a>. You can use them to try your photos with application logo. Once you'be submitted your photos, we'lol review them and notify you if they've been selected.
+
+Thank you in advance!
+
+Take a look at the official digiKam and Showfoto splash screens
+
+## digiKam and Showfoto 5.x Splash Screens
+
+digiKam 5.4.0 splash screen by [Wolfgang Scheffner](https://plus.google.com/u/0/118393660693739377704/about)
-description: "Hear what others have to say about digiKam"
-category: "about"
-aliases: "/testimonials"
----
-
-<div class="content"><p><i>Hey: this digikam is just fantastic! How could I ever organize my photos in the old days (some weeks ago) when I still had to work on win and had only photoshop and a file-maker database, where I had to write all the scripts on my own...? You've got a fan with me :-))</i></p>
-<p>Daniel Bauer, <a href="http://www.daniel-bauer.com"> photographer from Basel, Switzerland</a> from digiKam user mailing list.</p>
-<hr>
-<p><i>I'm surprised I got the black and white photos look almost like film texture-wise, a process I couldn't do before with conventional Levels, Curves and Saturation adjustments in Photoshop or Gimp. I am getting more and more impressed with the power digiKam's editing tools<br>
-have! I don't think I would be needing GIMP for photos anymore.</i></p>
-<p><a href="http://glibberish.org/archives/171"> From Joon Guillen blog's</a> a digiKam user from Hong Kong.</p>
-<hr>
-<p><i>digiKam is great! Just thought I'd thank you and your team for great program. I have been using it to organize my photos since starting to use my Powershot camera and now have nearly 25000 photos neatly arranged. thanks to your program. digiKam has been working nicely through different versions with minor bugs now and then. Keep up the good work and thanks for making it open source.</i></p>
-<p>From a private mail sent in April 2008 to Gilles Caulier by a digiKam user.</p>
-<hr>
-<p><i>I am using digiKam since version 0.6.0, and i am more and more amazed of it. Thats just all i want to tell you. I am a professional C++ programmer, and my judgment is: excellent, really, really excellent work! I thank you and the team very much. "Chapeau!"</i></p>
-<p>From a private mail sent in April 2008 to Gilles Caulier by Edgar Hermanns.</p>
-<hr>
-<p><i>For my picture albums I use digikam, and I always install the kipi-plugins, that allow me to do batch resizing and other fun stuff with my pictures. digiKam is quickly growing into a respectable application, that rivals paid alternatives...</i></p>
-<p><a href="http://ruipires.blogspot.com/2008/05/what-i-do-right-after-installing.html"> From Rui Pires blog's</a> a digiKam user from Lisbon, Portugal.</p>
-<hr>
-<p><i>I fell in love with <a href="http://www.panopixel.org">panorama photography...</a> Creating, editing and storing high resolution panoramas is not an easy task because they can reach great file sizes very easily, and most programs are optimised to work only for what most people use them for - small photos. Luckily I found digiKam, it stores my growing collection in an intuitive manner, and I can access my panoramas quickly and easily. Showfoto, digiKam's image editor, lets me do crucial global adjustments (white balance, curves, etc) to my panoramas in 48bpp mode, which guarantees smooth skies and plenty of space for maneuver, and then I can export to Gimp (which currently only supports 24bpp images) to do reprojection, tripod removal and local corrections. My digiKam typically handles 15 000 x 7 500 px panoramas at 48bpp, but I can also easily cross the 1 gigapixel barrier.</i></p>
-<p>From a private mail sent in Mai 2008 to Gilles Caulier by Maciek Dworak, a digiKam user from Poland.</p>
-<hr>
-<p><i>The FOSS world offers an abundance of excellent digital image-editing applications. Here is a sampling of my favorites: digiKam is an awesome all-in-one photo archiving and management, editing, and printing application. It's not an advanced editor like Gimp and Krita, but its feature set is comprehensive enough that you won't need Gimp or Krita for every editing job. It includes dcraw for high-quality RAW file manipulation, all kinds of handy batch processes, tags for organizing vast quantities of photos, and a super-nice composition and cropping editor.</i></p>
-<p><a href="http://www.e-linux.it/news_detail.php?id=6677"> From Carla Schroder web paper</a> named <b>Professional-Level Photography With Linux, And Nobody Goes To Jail</b>.</p>
-<hr>
-<p><i>I run SUSE Linux and have since 2004. One of the aps that come with my distro is Digikam; which is a photo organiser and a fairly powerful image editor; and integrates with flickr. I like that-it simplifies things greatly. Another feature integrated with Digikam is Simpleviewer, which generates Flash photo galleries. You can caption photos with Digikam; and use Simpleviewer to generate a gallery.</i></p>
-<p><a href="http://surewhynotnow.blogspot.com/2008/10/im-back-and-im-beautiful.html"> From Otto Yamamoto blog's</a> a digiKam user from New York, USA.</p>
-<hr>
-<p><i>After a lot of research I chose digiKam which is amazing. It allows you to import images, organize them in a database, tag, comment, rate and all the rest of that stuff. It also comes with an image editor which supports 16 bits. You also get a slide show feature and a very handy Light table. Colors profiling and calibration are also supported and integrated in digiKam.</i></p>
-<p><a href="http://paulindigo.blogspot.com/2008/10/credit-crunch-photo-software.html"> From Paul Indigo blog's</a> a photographer from UK.</p>
-<hr>
-<p><i>Honestly, I do not see the need for Windows these days. I have even stopped using Picasa because digiKam is so amazing - it has automatic DSLR lens correction built in! So unless anybody can give me a damn solid reason for Windows 7, I’m going to keep using my combination of Linux (for the most part) and the Mac (for my mobile computing) and will keep recommending that combination to everyone I meet.</i></p>
-<p><a href="http://carlmenezes.blogspot.com/2009/04/convince-me-windows-7-is-better.html"> From Carl blog's</a> a digiKam user.</p>
-<hr>
-<p><i>I thought I'd drop you a note to thank you for your work on digiKam. My wife has been using digiKam for over 4 years now (under Gnome). We just upgraded her system to Ubuntu 10.4 and she *really* likes some of<br>
-the new features. You've made her very happy (and thus me too).</i></p>
-<p>Mark Elendt, from digiKam user mailing list.</p>
-<hr>
-<p><i>At the moment, I am investing a good bit of energy into learning my way around Arch Linux, and digiKam is probably my favorite piece of software ever. I am investing a lot of energy into learning to be a good photographer, and Digikam is my digital photo workhorse. It's an amazing piece of work that keeps getting better.</i></p>
-<p><a href="http://www.linuxpromagazine.com/Online/News/The-Audacity-of-Carla-Schroder"> From Carla Schroder article's</a>, writer at linuxpromagazine.com.</p>
+The easiest way to contribute is to spread the word about digiKam. We also encourage you to test digiKam, report bugs, and submit feature requests. You might also want to subscribe to the [digikam-users](https://mail.kde.org/mailman/listinfo/digikam-users) mailing list and help other digiKam users with their questions and problems.
+
+## Reporting Bugs and Submitting Feature Requests
+
+Use the bug tracking system for all bug reports and new feature requests. Take a look at the [support page](/?q=support) for further information.
+
+## Dealing with Crashes in digiKam
+
+In case digiKam crashes, you can provide a backtrace using GDB debugger. digiKam needs to be compiled with all debug info; otherwise the backtrace will be useless. If you installed digiKam using the packages provided by your distribution, make sure to install the corresponding debug package. [The debugging guide](https://community.kde.org/Guidelines_and_HOWTOs/Debugging) provides further information on debugging.
+
+To get a backtrace on Linux with GDB, use following commands:
+
+```
+$ gdb digikam
+(gdb) catch throw
+(gdb) run
+(gdb) ...
+(gdb) _crash here_
+(gdb) ...
+(gdb) bt
+(gdb) _the backtrace is here_
+(gdb) quit
+```
+
+On Windows, the binary installer comes with a dedicated GDB, while macOS users can run **lldb** debugger as follows:
+On Linux, run digiKam from the command line to get the output generated by the application. On macOS, digiKam executable is installed in _/opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam_, and you can use it to start the application from the command line to view debug traces. On Windows, trace is not sent to the console. You need to install [DebugView tool](http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx) to capture debug traces generated by digiKam.
+
+## Submitting Patches
+
+Before you submit patches, please read the [HACKING file](https://cgit.kde.org/digikam.git/tree/HACKING). Send patches against the current version of the code (latest git/master revision) and not the stable release or an old beta version. Patches can be created using the following command:
+
+ git diff HEAD > mydiff.patch
+
+The patches must be attached to a new entry in [Bugzilla](https://www.digikam.org/support). Please do not use mailing lists or private mail.
+
+## Translations
+
+If you want to contribute to the digiKam internationalization effort, contact the translation teams at [http://l10n.kde.org/](http://l10n.kde.org/). Also, please read the [Translation HOWTO](http://l10n.kde.org/docs/translation-howto/).
+
+## Documentation
+
+Help with digiKam documentation is always welcome. For all documentation-related matters, write to [digiKam-devel mailing list](https://mail.kde.org/mailman/listinfo/digikam-devel). Our [documentation](http://docs.kde.org/development/en/extragear-graphics/digikam/index.html) is based on the [docbook format standard](http://l10n.kde.org/docs/doc-primer/index.html). The [README](https://cgit.kde.org/digikam-doc.git/tree/README) file explains in detail how structure the documents, take screenshots, etc.
+
+It's also possible to submit additions and changes in the ASCII format. To do this, create a new Bugzilla entry with a patch against git/master code, so it can be incorporated in the documentation.
+
+### Pictures Samples
+
+We need raw and JPEG files from different manufacturers (Canon, Nikon, Sony, Olympus, Sigma, etc.). We use these files to analyze embedded metadata to improve camera support in digiKam. We also need sample files produced by different applications (including other platforms and proprietary software like Adobe Photoshop) that include IPTC/XMP metadata. This can help us to improve compatibility with other tools and implement automatic import of this data into the digiKam database.
+
+## Splash Screens
+
+As a photographer, you can submit your best photos for use as digiKam splash screen. Take a look [at this page](http://www.digikam.org/splashcreens) for further information.
description: "Frequently asked questions about digiKam"
category: "documentation"
aliases: "/faq/digikam"
---
-## My camera is not in the list of supported cameras in digiKam.
+### My camera is not in the list of supported cameras in digiKam.
Can you add drivers for my camera ?
Only if you pay me. ;)
Seriously, digiKam doesn't included any camera drivers with it. It makes use of <a href="http://www.gphoto.org/">gphoto2</a> to do camera operations. If your camera is not in the supported list, i would recommend doing some <a href="http://www.google.com">searching</a> around. Many of the new cameras actually provide a USB MassStorage Device Interface, so that you can access the camera like a hard disk. (See, the FAQ about using a USB MassStorage Camera with digiKam).
If you have still have no luck, i would recommend contacting the gphoto2 people.
-## How can I inform you about bugs and wishes?
+### How can I inform you about bugs and wishes?
-##### Reporting bugs and wishes
+##### Reporting bugs and wishes
Please use the KDE bug tracking system for all bugreports and new feature wishlists. You can checkout the current bugreports and wishlists at these urls
* <a href="http://bugs.kde.org/buglist.cgi?product=digikam&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED">digiKam bugs and wishes</a>
* <a href="http://bugs.kde.org/buglist.cgi?product=digikamimageplugins&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED">digiKamImagePlugins bugs and wishes</a>
* <a href="http://bugs.kde.org/buglist.cgi?product=kipiplugins&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED">KIPI bugs and wishes</a>
-## I have a USB Mass Storage Camera. How do I use it with digiKam ?
+### I have a USB Mass Storage Camera. How do I use it with digiKam ?
-### The Easy Way!
+#### The Easy Way!
If you have a relatively modern Linux distribution that is pre-configured to work with USB Mass Storage Devices, there's nothing you need to set up!. It should be truly "plug and play":
* Plug your device in to the USB slot
* It will be automatically detected by the kernel, and an appropriate entry in /etc/fstab will be added automatically.
* The device will be mounted under /mnt/flash or /mnt/camera
-* Run digikam setup and add a "Mounted Camera". Set the path to the above path, where the camera is mounted.
+* Run digiKam setup and add a "Mounted Camera". Set the path to the above path, where the camera is mounted.
-### Manual Setup
+#### Manual Setup
If you're running a Linux distribution that doesn't set up USB Mass Storage devices automatically, here are the steps you need to follow:
-* Most users using a recent Linux Distribution can skip this step. Configure the Linux Kernel:
- * Add SCSI Support
- SCSI Support (CONFIG_SCSI)
- SCSI IDE Support (CONFIG_BLK_DEV_IDESCSI)
- SCSI disk support (CONFIG_BLK_DEV_SD)
- SCSI generic support (CONFIG_CHR_DEV_SG)
- * Add USB Support
- Support for USB (CONFIG_USB)
- USB drivers. One or more of: ECHI HCD (CONFIG_USB_EHCI_HCD), UHCI (CONFIG_USB_UHCI), OHCI (CONFIG_USB_OHCI)
- Preliminary USB device file system (CONFIG_USB_DEVICEFS)
- USB Mass Storage support (CONFIG_USB_STORAGE)
+* Most users using a recent Linux Distribution can skip this step. Configure the Linux Kernel:
+ * Add SCSI Support
+ SCSI Support (CONFIG_SCSI)
+ SCSI IDE Support (CONFIG_BLK_DEV_IDESCSI)
+ SCSI disk support (CONFIG_BLK_DEV_SD)
+ SCSI generic support (CONFIG_CHR_DEV_SG)
+ * Add USB Support
+ Support for USB (CONFIG_USB)
+ USB drivers. One or more of: ECHI HCD (CONFIG_USB_EHCI_HCD), UHCI (CONFIG_USB_UHCI), OHCI (CONFIG_USB_OHCI)
+ Preliminary USB device file system (CONFIG_USB_DEVICEFS)
+ USB Mass Storage support (CONFIG_USB_STORAGE)
* Load the required kernel modules: modprobe ide-scsi sd_mod sg vfat modprobe usb-ohci (or usb-uhci depending on your usb bus) modprobe usb-storage (or usb-uhci depending on your usb bus)
* Plug in your USB device. You should see your device listed in /proc/bus/usb/devices. If not, you need to fix the kernel or check your cabling.
* Use the sg3-utils package to determine the device name of your USB Mass Storage Device:
* Install the sg3-utils package (e.g. on Debian, Lindows: apt-get install sg3-utils)
* Connect the camera and turn it onto the picture display mode
- * List your raw SCSI devices by running sg_scan -i. The output will look something like this:
+ * List your raw SCSI devices by running sg_scan -i. The output will look something like this:
* This tells me that I have 2 SCSI devices on my system: My CD drive on /dev/sg0, and a OLYMPUS D-380 Camera on /dev/sg1
* Determine the real SCSI device associated with your USB Mass Storage Device with sg_map. The output looks like: /dev/sg0 /dev/sr0 /dev/sg1 /dev/sda
* Now we can match the results of these last two steps. For example the Olympus camera is on the /dev/sda device.
* In most cases, USB Mass Storage Devices will only have one partition on them, so we can safely assume that the final, mountable device is /dev/sda1 (the first partition on /dev/sda).
* Make a directory where you can mount the camera: mkdir /mnt/camera; chmod 666 /mnt/camera
* Try mounting the camera now: mount -t vfat /dev/sda1 /mnt/camera
- * If no errors show up, then you have performed all the steps correctly. To verify everything is right, point you file manager to /mnt/camera and you should be able to see the folder/pictures on the camera
+ * If no errors show up, then you have performed all the steps correctly. To verify everything is right, point you file manager to /mnt/camera and you should be able to see the folder/pictures on the camera
* Add an entry to /etc/fstab for the mount point: /dev/sda1 /mnt/camera auto defaults,user,noauto 0 0
* Now it's ready to go. Any user can mount the device: mount /mnt/camera
* Make sure you unmount it before taking the card out or unplugging it: umount /mnt/camera
-* Run digikam setup and add a USB MassStorage Camera. Set the path to the above path, where the camera is mounted.
+* Run digiKam setup and add a USB MassStorage Camera. Set the path to the above path, where the camera is mounted.
-## Thumbnail generation fails on large files
+### Thumbnail generation fails on large files
-Q: On all my albums, digikam fails to generate thumbnails on some images. The only pattern I can spot is that it fails on largish files (bigger than 1MB). When the thumnails are generated, the ones that fail appear at first and then are replaced by the broken picture icon.
+Q: On all my albums, digiKam fails to generate thumbnails on some images. The only pattern I can spot is that it fails on largish files (bigger than 1MB). When the thumnails are generated, the ones that fail appear at first and then are replaced by the broken picture icon.
A: try changing the following setting:
kcontrol->kde components->file manager->Previes & Metadata (tab)->Maximum file size
-## Using hotplugging with digiKam
+### Using hotplugging with digiKam
-### Introduction
+#### Introduction
With Kernel 2.4 came a hotplug support into Linux. This feature is also supported by gPhoto, which is used as camera driver from digiKam. So it should (and is) possible to add an hotplug feature into digiKam. This article tells you what are the requirements and what you have to do.
When you put a device into a hotplug bus like USB, the kernel detects it and looks if it has a suitable driver compiled inside. If not, the hotplug module is called and asked what to do. <a href="http://www.gphoto.org/">gPhoto2</a> offers a way to configure hotplug for USB cameras. Doing so, the hotplug module will call a gphoto2 library to add a driver and afterthat a customizable script calls the application that should interact with the device. This implementation uses two scripts. The first one, usbcam, is called as root and his job is to determine the active user and call the 2nd script digikam-hotplug using the users id. Both scripts could be downloaded here.
-### Requirements
+#### Requirements
The following requirements should be fullfilled to use digiKam with the hotplugging feature. Notice, it is also possible to change some of the requirements, but then you&apsll have to do additional research to get the solution up and running.
* Linux with Kernel >= 2.4, compiled with hotplugging Support
* gphoto 2.x and libgphoto 2.x
* Perl 5.6.x
* KDE 3.x
* digiKam digiKam 0.7.1+
As an additional remark, i should mention that the digikam-hotplug script that you could donwload requires KDE not only installed, it has to be the active Window Manager.
-### Installation and Configuration
+#### Installation and Configuration
This section gives the same information like <a href="http://www.gphoto.org/doc/manual/permissions-usb.html#setting-up-linux-hotplug/">chapter 4.3</a> from the gPhoto manual. It simply describes howto setup the kernel hotplugging feature. The only difference are digiKam specific <a href="http://digikam.free.fr/hotplug/usbcam.tar.gz">scripts</a>.
-#### Checking the kernel hotplugging feature
+##### Checking the kernel hotplugging feature
First you should check whether your kernel comes with the required hotplugging feature. Therefore look if you have a file
`cat /proc/sys/kernel/hotplug`
and if it points to a valid hotplug binary. If not, you'll have to compile a new kernel with hotplugging support. It does'nt matter whether the hotplugging support is directly compiled into the kernel or if it is compiled as module.
libgphoto comes with the program print-usb-usermap which is usually located under
`/usr/lib/libgphoto2/print-usb-usermap` or `/usr/local/lib/libgphoto2/print-usb-usermap`
This program tells the hotplug module, which cameras are supported by the installed version from gPhoto. All you have normally to do is
Now you have to download the scripts, untar them using
`tar xvzf usbcam.tar.gz`
<strong>Notice:</strong> There are two versions of the scripts. The 0.2.x series support digiKam 0.6.x and the 0.3.x series digiKam 0.7.1+. Rename your version to usbcam and digikam-hotplug, and copy them to
`/etc/hotplug/usb/usbcam`
and make usbcam executable for root and digikam-hotplug executable for the users that it should work for. For security reasons you should also check, that only root has write permissions on each file.
To test your installation, you'll have to unplug your camera, wait a few seconds and plug it in again. After a few moments digiKam should start and connect automaticly to your camera.
If you have problems doing this, you should read the original gphoto documentation and check the syslog for notices from the two scripts.
-### Copyright
+#### Copyright
This script was writen by Oliver Dörr based on the usbcam script original distributed from the gPhoto Project. Because i'm using their code using the GPL license, this code is also distributed under the same license.
-## Which file format should I use?
+### Which file format should I use?
Most digital cameras store images in jpeg format on the memory card. JPEG is a compressed format, whose compression causes loss of quality. Heavy compression may make the loss of quality visible to the eye. Every time you open a JPEG image, edit it, save the file and close it, the image is compressed and quality is lost. Lost quality can not be regained.
-To avoid this repeated loss of quality you should save your edited files in a lossless format. Digikam understands two of these: Tiff and png. In digiKam it is advisable to use png. Digikam supports the exif data in png files, whereas (currently) for tiff files, exif data are lost.
+To avoid this repeated loss of quality you should save your edited files in a lossless format. digiKam understands two of these: Tiff and png. In digiKam it is advisable to use png. digiKam supports the exif data in png files, whereas (currently) for tiff files, exif data are lost.
So the recommendation is to save any edited files as png.
You have now finished editing your photos and are content with the results. Should you keep the png-files or convert them to the far smaller JPEG files for storage?. If you are very concerned about storage space, you can do the latter. You could, however rather keep the lossless png files and only create JPEG copies in the moment you want to take your images to the print shop, send them by email or post them on the web.
-## Why are my RAW images so dark?
+### Why are my RAW images so dark?
In 16-bit mode, many are surprised that a relatively dark photograph shows up after RAW conversion with digiKam, even so the 'ColorManagement' and 'RAW Conversion' options have been meticulously set-up for the intended purpose. The simple reason is that digiKam uses Dave Coffin's <a href="http://cybercom.net/~dcoffin/dcraw/">dcraw</a> for linear conversion, and if the ICC profile does not include gamma correction and/or tone mapping (most Canon profiles), the result is dark (in 8-bit mode the gamma correction is applied automatically). But nothing is lost, read on!
A RAW file is a container including the raw sensor data, EXIF metadata, and often a JPEG preview thumbnail. It does normally not include an ICC profile. The embedded JPEG file is used by digiKam to display RAW image thumbnails or in slide shows, and it can be used for TV display from the camera. This is fast, but a preview only, no raw data.
RAW conversion requires a couple of steps in order to produce a satisfying result, better adapted to your needs than JPEG out-of-the-camera images:
1. Choice of the internal working space in regard to the intended use
2. Adjust tonal range - define thresholds for highlights and shadows
3. Adjust gradation - adjust mid tones, for example using numerical numbers in the histogram or curves like features
4. Alter white balance if necessary
5. Color cast removal ideally using color temperature (or an according eyedropper tool) as well as a tint / tone slider. An according eye-dropper tool can be applied simply by clicking inside the image on neutral grey subject tones. This procedure doesn't always create the expected result, because quite often the light situation while capturing the image wasn't neutral either.
6. Smoothing and noise removal (if not done in the conversion process already)
7. Apply sharpening (refocus, unsharpmask)
8. Choose final color bitdepth (saving as JPEG always reverts to 8-bit depth, use PNG or TIFF for 16-bit)
9. Select output and pixel dimensions – upsampling on the RAW file often gives better results in comparison to already processed files
10. Continue editing for example retouching or small enhancements in the favorite imaging application
Now, most profiles that come with the camera OEM software are not so suited for linear conversion. If you'd like a good profile, do it yourself or via a service. It will be more precise than the standard profile and it will <b>include gamma correction</b> - no dark images anymore in 16-bit mode!
* [European Color Initative ECI](http://eci.org/eci/en/020_eci.php)
-## digiKam doesn't work when album library is on a network share (nfs, samba)
+### digiKam doesn't work when album library is on a network share (nfs, samba)
DigiKam freezes when I store my album library on a NFS server, NAS, windows shared folder, etc. What can I do ?
digiKam uses sqlite to store informations about images (tags, comments, rates, ...). Sqlite relies on file locking features provided by filesystems (check <a href="http://www.sqlite.org/faq.html#q5">this FAQ entry</a>). But, network file systems often have troubles with locking and this can cause unexpected problems with sqlite.
In order to solve this problem, try one of the following workarounds :
* Use a <a href="http://thoughtsonrails.wordpress.com/2007/03/03/digikam-albums-on-network-filesystem/">symlink for some albums stored on a network path</a>
* Use a <a href="http://lists.kde.org/?l=kde-bugs-dist&m=117536777106366&w=2">symlink for the sqlite database file</a>. This method is preferred if you want to have all your album library on a network path.
Note: the digiKam team is aware of this problem and is working on it. In the future, it will be possible to use another database backend to solve it.
-## How to create a digikam theme?
+### How to create a digiKam theme?
#### Header
Since 0.9.3 release, theme are based on pure XML format. Comments in the theme are done by using common XML markers to include comments. The header is the place where you can add some comments, give credit to yourself... Look an existing XML theme file for details.
-#### Base Properties XML Markers
+##### Base Properties XML Markers
name: Marine
CaseColor: #FFFFFF
TextRegularColor: #000000
TextSelectedColor: #000000
TextSpecialRegularColor: #658857
TextSpecialSelectedColor: #FFFFFF
-BaseColor is the background color which shall be used for the thumbnail view on the right and album/tag tree on the left.
-TextRegularColor is used for regular (unselected) text and TextSelectedColor is used for selected text. usually the selected region tends to be brighter or darker and the selected text needs to contrast with it. TextSpecial... are the colors which are used for rendering of some special text like the tags at the bottom of the thumbnails and the collection/date names in the left view.
+BaseColor is the background color which shall be used for the thumbnail view on the right and album/tag tree on the left.
+TextRegularColor is used for regular (unselected) text and TextSelectedColor is used for selected text. usually the selected region tends to be brighter or darker and the selected text needs to contrast with it. TextSpecial... are the colors which are used for rendering of some special text like the tags at the bottom of the thumbnails and the collection/date names in the left view.
The color specification is done by using standard HTML color format (RGB/hexadecimal).
-#### Banner Properties XML Markers
+##### Banner Properties XML Markers
BannerColor: #4BFF9C
BannerColorTo: #35B56F
BannerBevel: RAISED
BannerGradient: HORIZONTAL
BannerBorder: TRUE
BannerBorderColor: #2FA062
-These specifications are used to render the banner at the top of the thumbnail view.
-BannerBevel indicates the type of bevel to use for the banner, possible choices are RAISED (for a raised appearance), SUNKEN (for a sunken appearance), FLAT (for a flat appearance). BannerGradient is used for rendering a gradient; the possible choices are SOLID (no gradient), HORIZONTAL (horizontal gradient), VERTICAL (vertical gradient), DIAGONAL (diagonal gradient). There are two color specifications: Color and ColorTo. If a SOLID gradient is specified only "Color" is used, for other cases the gradient is rendered from "Color" to "ColorTo". BannerBorder indicates whether a border should be drawn around the banner, using BannerBorderColor. set it to "TRUE" for rendering a border and to "FALSE" otherwise.
+These specifications are used to render the banner at the top of the thumbnail view.
+BannerBevel indicates the type of bevel to use for the banner, possible choices are RAISED (for a raised appearance), SUNKEN (for a sunken appearance), FLAT (for a flat appearance). BannerGradient is used for rendering a gradient; the possible choices are SOLID (no gradient), HORIZONTAL (horizontal gradient), VERTICAL (vertical gradient), DIAGONAL (diagonal gradient). There are two color specifications: Color and ColorTo. If a SOLID gradient is specified only "Color" is used, for other cases the gradient is rendered from "Color" to "ColorTo". BannerBorder indicates whether a border should be drawn around the banner, using BannerBorderColor. set it to "TRUE" for rendering a border and to "FALSE" otherwise.
-#### Thumbnail Properties XML Markers
+##### Thumbnail Properties XML Markers
ThumbnailRegularColor: #E7FFF4
ThumbnailRegularColorTo: #C4D8CF
ThumbnailRegularBevel: RAISED
ThumbnailRegularGradient: HORIZONTAL
ThumbnailRegularBorder: TRUE
ThumbnailRegularBorderColor: #769286
ThumbnailSelectedColor: #4BFF9C
ThumbnailSelectedColorTo: #35B56F
ThumbnailSelectedBevel: RAISED
ThumbnailSelectedGradient: HORIZONTAL
ThumbnailSelectedBorder: TRUE
ThumbnailSelectedBorderColor: #2FA062
These specifications are used for rendering the thumbnails. Regular... is used for unselected thumbnails and Selected... for selected thumbnails. The specifications are similar to that of the banner.
-#### Listview Properties XML Markers
+##### Listview Properties XML Markers
ListviewRegularColor: #FFFFFF
ListviewRegularColorTo: #FFFFFF
ListviewRegular.bevel: FLAT
ListviewRegular.gradient: SOLID
ListviewRegular.border: FALSE
ListviewRegularBorderColor: #FFFFFF
ListviewSelectedColor: #4BFF9C
ListviewSelectedColorTo: #35B56F
ListviewSelectedBevel: RAISED
ListviewSelectedGradient: HORIZONTAL
ListviewSelectedBorder: TRUE
ListviewSelectedBorderColor: #2FA062
These are used for rendering the items on the left treeview. again, the specifications are same as that of the banner.
-Notes:
+Notes:
-* Case sensitivity is important for specifiying the property names, but not for the property values.
-* System level installation of themes is done in $(INSTALLATION_PREFIX)/share/apps/digikam/themes and user level installation in $(HOME)/.kde/share/apps/digikam/themes
+* Case sensitivity is important for specifiying the property names, but not for the property values.
+* System level installation of themes is done in $(INSTALLATION_PREFIX)/share/apps/digikam/themes and user level installation in $(HOME)/.kde/share/apps/digikam/themes
* Theme names appear in the menu with the filename. Make sure to capitalize the first letter of the filename
-* Its not necessary to restart digikam if you modify the theme. switch to a different theme and switch back. But if you add a new theme, you will have to restart digikam for the new theme to be recognized.
+* Its not necessary to restart digiKam if you modify the theme. switch to a different theme and switch back. But if you add a new theme, you will have to restart digiKam for the new theme to be recognized.
-#### Theme editor
+##### Theme editor
You can also try the theme editor include in digiKam since 0.9.3 release.
<a href="http://www.digikam.org/?q=system/files&file=images/digikamthemedesigner_0.png"><img src="http://www.digikam.org/?q=system/files&file=images/digikamthemedesigner_0.preview.png" width="800" height="549" alt="TimeAdjust kipi-plugin for KDE4 in action">
</a>
-## Color Management with X on Linux
+### Color Management with X on Linux
Color management of your monitor is possible with digiKam from version 0.9.0 onwards, but it is slow. The better and more fundamental way is to include the display color management in your X server using profiles. Then all other applications will profit as well.
This <a href="http://linux.vilars.com/">site</a> explains it all, go there for the installation procedure and the How-To's.
Note:
The best way to color-manage the display is to establish a custom profile and use that one, a procedure to be repeated every other year or so for aging reasons. But if you go the easier way and use the profiles delivered from the manufacturer, it is paramount to do a normalization as described for example on the<a href="http://www.alpenglowimaging.com/monitor-calibration.htm"> alpenglow</a> web site.
-## Thumbnail generation fails on video files
+### Thumbnail generation fails on video files
-#### Why don't I have thumbnails for my video files?
+#### Why don't I have thumbnails for my video files?
-#### Why thumbnail generation stops at the first video file I have ?
+#### Why thumbnail generation stops at the first video file I have ?
First, check if it's the same in konqueror.
-Digikam uses KDE to generate thumbnails and KDE rely on aRts to do that.
+Digikam uses KDE to generate thumbnails and KDE rely on aRts to do that.
So, you should check your aRts configuration. ARts can use xine plugin for video files, so try if xine is able to play your video files. You may have to use additional codecs (eg libxine-extracodecs on debian/ubuntu if you already have libarts1-xine) for that.
Try also to play your video files using xine (if libarts1-xine is installed).
Remember that if it doesn't work in konqueror, it won't work in digikam...
-## How can I change the default video player ?
+### How can I change the default video player ?
-#### When I double-click on a video thumbnail, it opens -unwanted video player-, how could I change it to another video player ?
+#### When I double-click on a video thumbnail, it opens -unwanted video player-, how could I change it to another video player ?
-Start kcontrol then go to KDE Components/File Associations, then
-click on video. Here you have a list of file types with the list of
+Start kcontrol then go to KDE Components/File Associations, then
+click on video. Here you have a list of file types with the list of
applications that can open them.
-E.g. if you want another video player for your .avi files, go to
+E.g. if you want another video player for your .avi files, go to
x-msvideo. The first application listed here will be the default one.
-## How can I change the text font size ?
+### How can I change the text font size ?
-#### Size of fonts for text and menus is too big/too small in Digikam. How can I adjust it ?
+#### Size of fonts for text and menus is too big/too small in Digikam. How can I adjust it ?
Start kcontrol then go to Appearance & Thems", then click on "Fonts". Here you can adjust the font size but also choose another font.
Please be warned that this will change the font behavior of all KDE applications !
-## Single-click on a thumbnail opens digikam editor
+### Single-click on a thumbnail opens digiKam editor
-#### When I click on a thumbnail, it opens the digikam editor. How can I disable that ?
+#### When I click on a thumbnail, it opens the digiKam editor. How can I disable that ?
-Start kcontrol then go to Peripherals/Mouse and choose "double-click
+Start kcontrol then go to Peripherals/Mouse and choose "double-click
to open files and folders"
-## Some "Properties" in digikam sidebar are unknown or unavailable
+### Some "Properties" in digiKam sidebar are unknown or unavailable
-#### Why can't I get Image Properties Dimensions or other items ?
+#### Why can't I get Image Properties Dimensions or other items ?
Digikam uses KDE metainfo plugins to display the file properties.
If the "Dimensions" value is "unknown", it means you don't have this plugin.
On debian based distribution (eg Ubuntu), install kdegraphics-kfile-plugins package.
Note: even if you have the right plugin, some other properties (Bits depth, Sensitivity, Compression, ...) can still be unavailable depending on the image file (and your digital camera).
-## digiKam uses konqueror and kmail
+### digiKam uses konqueror and kmail
The kipi-plugins use the default KDE application settings to invoke web browser and email clients.
#### In Metadata/GPS sidebar, when I click on "More Info...", it opens konqueror, how could I change it to another browser (firefox or anything else) ?
Start kcontrol (or systemsettings), then go to "KDE Components/Component Chooser", navigate to "Default Applications", then click on "Web Browser" and choose "in the following browser" where you can put any command.
-#### In Menu->Image->Email Images, kmail is invoked, but I use Thunderbird (or any other email client)
+#### In Menu->Image->Email Images, kmail is invoked, but I use Thunderbird (or any other email client)
Start kcontrol (or system settings), then go to "KDE Components/Component Chooser", navigate to "Default Applications", then click on "Email Client" and select you preference
The email client can also be specified in the ->Email Images dialog itself on the mail page. The setting will be remembered by digiKam.
Note: If you use Ubuntu, the kcontrol or systemsettings menus will not be available to you, you have do do in the digiKam dialog box as described above.
-## How to deal with utf-8 encoding ?
+### How to deal with utf-8 encoding ?
-#### I just upgraded my preferred linux distribution but now I have warnings about utf-8. I have a warning when starting digiKam about new character encoding. What should I do ?
+##### I just upgraded my preferred linux distribution but now I have warnings about utf-8. I have a warning when starting digiKam about new character encoding. What should I do ?
Nowadays, most linux distributions use utf8 by default for the character encoding. It includes the content of files, but also the file names.
Digikam will warn you when you change your locale with a new encoding.
Eg, if you switched from iso latin1 (iso8859-1) to utf8, digiKam will send you this warning :
<pre><small>Your locale has changed from the previous time this album was opened.
Old Locale : ISO 8859-1, New Locale : UTF-8
-This can cause unexpected problems. If you are sure that you want to
-continue, click on 'Yes' to work with this album. Otherwise, click on 'No'
+This can cause unexpected problems. If you are sure that you want to
+continue, click on 'Yes' to work with this album. Otherwise, click on 'No'
and correct your locale setting before restarting digiKam
</small></pre>
-Before accepting this modification, you should migrate at least the file names in your albums to utf-8 or you might have troubles because digikam won't be able to access directories which contains accents non encoded in utf-8.
+Before accepting this modification, you should migrate at least the file names in your albums to utf-8 or you might have troubles because digiKam won't be able to access directories which contains accents non encoded in utf-8.
For that purpose, linux distributions propose various solutions and tools, but mainly based on convmv :
</p>
-##### Gentoo
+###### Gentoo
Gentoo has a very nice page about using UTF-8 :
<a href="http://www.gentoo.org/doc/en/utf-8.xml">Using UTF-8 with Gentoo</a>
This could also be useful for users of other distributions.
-##### Mandriva
+###### Mandriva
For Mandriva 2007, it seems that the same convmv can be applied.
The most used tool to do that is <a href="http://j3e.de/linux/convmv/man/">convmv</a> (written in perl)
Eg (try it first in a test directory and backup everything before!) :
<small>
<pre>convmv --notest -r -f latin1 -t utf-8
</pre>
</small>
-## Is Digikam available in my language ?
+### Is digiKam available in my language ?
-#### How can I use another language instead of the default (english) one ?
+##### How can I use another language instead of the default (english) one ?
-##### Distribution package
+###### Distribution package
-If you installed digikam using your distribution package, language files should be included with it and you can run digikam in any supported language.
+If you installed digiKam using your distribution package, language files should be included with it and you can run digiKam in any supported language.
You can change the default language by using KDE Control Center (kcontrol) :
Go to "Regional & Accessibility" and then in "Country/Region & Language" to use your default language.
Note, that will affects all your KDE applications.
-You can also change the language used in digikam with the $LANG environment variable.
+You can also change the language used in digiKam with the $LANG environment variable.
Eg :
<pre>export LANG=fr.UTF-8 ; digikam</pre>
-##### Compiled from stable or beta release
+###### Compiled from stable or beta release
-If you compiled yourself digikam using the official tarballs, you can use digikam in any supported language. The language files are installed with digikam.
+If you compiled yourself digiKam using the official tarballs, you can use digiKam in any supported language. The language files are installed with digikam.
See above for details about how to use another language.
-##### Compiled from svn (Subversion)
+###### Compiled from svn (Subversion)
-If you compiled yourself digikam from the latest trunk files, you will have to get the languages files you need. Check the <a href="http://www.digikam.org/?q=download/svn#homeinstall">svn download page</a> for more details (eg: sample script to compile digikam in your homedir).
+If you compiled yourself digiKam from the latest trunk files, you will have to get the languages files you need. Check the <a href="http://www.digikam.org/?q=download/svn#homeinstall">svn download page</a> for more details (eg: sample script to compile digiKam in your homedir).
-## Digikam doesn't compile
+### digiKam doesn't compile
-#### I can't compile digikam. What can I do ?
+##### I can't compile digikam. What can I do ?
-First, check that you have development files installed in your linux system. digikam depends on a lot of libs and you must have the headers to compile it.
+First, check that you have development files installed in your linux system. digiKam depends on a lot of libs and you must have the headers to compile it.
Usually, linux distributions have <b>-dev</b> packages when you want to compile something against a specific library. For a list of required dependencies, read the README file. Here's the <a href="http://websvn.kde.org/branches/stable/extragear/graphics/digikam/README?view=markup">current README (svn version)</a>.
On debian-based distribution (eg Debian, Ubuntu), you can install the required packages with :
<pre>apt-get build-dep digikam</pre>
If there are some warnings about unsermake, set the $UNSERMAKE environment variable as "no". Eg :
<pre>export UNSERMAKE=no</pre>
Look also at the <a href="/?q=download">download page</a> for more informations (tarball and svn sections). If you still have problems, check the <a href="http://www.digikam.org/?q=support">support page</a>.
-## Digikam always crashes when doing xxxx. What can I do ?
+### digiKam always crashes when doing xxxx. What can I do ?
-#### When editing IPTC, playing with tags, assigning keywords or doing xxxx, digikam crashes. What's the problem ?
+##### When editing IPTC, playing with tags, assigning keywords or doing xxxx, digiKam crashes. What's the problem ?
It could be a problem with exiv2. It's mandatory to use at least version 0.11 with digikam. So, install a recent version (0.14 is highly recommended).
-If digikam still crash, first check if you already have a former exiv2 library with version < 0.11 installed on your system. There are been many reports about crashes due to old exiv2 libs still present in /usr/lib or /usr/local/lib.
+If digiKam still crash, first check if you already have a former exiv2 library with version < 0.11 installed on your system. There are been many reports about crashes due to old exiv2 libs still present in /usr/lib or /usr/local/lib.
If you found one old lib, remove it if possible, or try at least to rename it to see if it solves the problem.
It's strongly recommended to use the latest stable exiv2 version (0.14 now).
-Then, check the <a href="/?q=support">support</a> and the <a href="/?q=contrib">contrib</a> pages.
+Then, check the <a href="/?q=support">support</a> and the <a href="/?q=contrib">contrib</a> pages.
Try to see if your problem has already been reported by another user in bugs.kde.org .
-If it's not the case, check the contrib page, you will find instructions on how to compile digikam with full debug and how to send us a backtrace.
-
-
+If it's not the case, check the contrib page, you will find instructions on how to compile digiKam with full debug and how to send us a backtrace.
+The digiKam documentation comes as a package usually called _digikam-doc_ that you can install locally. You can also read it online (updated automatically every Friday). Some options might differ from your local installation, because the online manuals cover to the development version:
+
+* [digiKam HTML version](http://docs.kde.org/development/en/extragear-graphics/digikam/index.html)
+* [Showfoto HTML version](http://docs.kde.org/development/en/extragear-graphics/showfoto/index.html)
+* [digiKam PDF version](http://docs.kde.org/development/en/extragear-graphics/digikam/digikam.pdf)
+* [Showfoto PDF version](http://docs.kde.org/development/en/extragear-graphics/showfoto/showfoto.pdf)
+
+[digiKam tutorials](https://userbase.kde.org/Digikam/Tutorials) wiki offers tutorials that cover various digiKam tools and functionality.
+
+#### API and Database Schema
+
+If you plan contribute as a developer to digiKam, you might find the following links useful:
+Use [SQliteBrowser](http://sqlitebrowser.sourceforge.net) or the sqlite [Firefox add-on](https://addons.mozilla.org/en-US/firefox/addon/5817) to work with SQlite3 database files.
+We encourage you to improve the existing documentation by submitting comments, corrections, and patches. If you'd like to contribute to the documentation, have a look at the [Contributing](?q=contrib#documentation) page.
-The digiKam documentation comes as a separate package usually called <em>digikam-doc</em>) which you have to install for local use. But you can read it online as well (updated automatically each Friday). Some options might differ from your local installation because the online manuals belongs to the development version:
-</p>
-<ul>
-<li><a href="http://docs.kde.org/development/en/extragear-graphics/digikam/index.html">digiKam HTML version</a></li>
-<li><a href="http://docs.kde.org/development/en/extragear-graphics/showfoto/index.html">Showfoto HTML version</a></li>
-</ul>
-<ul>
-<li><a href="http://docs.kde.org/development/en/extragear-graphics/digikam/digikam.pdf">digiKam PDF version</a></li>
-<li><a href="http://docs.kde.org/development/en/extragear-graphics/showfoto/showfoto.pdf">Showfoto PDF version</a></li>
-</ul>
-<p>A <b>wiki page</b> hosted by KDE project is under contruction. Every one can contribute to add and fix wiki contents. Look <a href="http://userbase.kde.org/Digikam">here</a> for details.</p>
-<h1>API and Database schema</h1>
-<p>If you plan contribute as developer to digiKam, you might find these links interesting:</p>
-<p>Use <a href="http://sqlitebrowser.sourceforge.net">SQliteBrowser</a> or the sqlite <a href="https://addons.mozilla.org/en-US/firefox/addon/5817">firefox extension</a> to play with SQlite3 database files.</p>
-<p>We'll be happy to take up your remarks, corrections or patches to make our manuals even better, we care for details like wrong plural forms etc.</p>
-<p>If you'd like to contribute to the documentation, have a look at the <a href="?q=contrib#documentation">contrib</a> page.</p>
+This page contains information about contributing to the digiKam website.
+
+There are two URLs in use for the website:
+
+* https://www.digikam.org
+
+ The main digiKam website.
+
+* https://staging.digikam.org
+
+ The test/staging website.
+ This should normally mirror the main website for the most part.
+ This is where new content is tested before pushing to the main site.
+
+**Other meta pages:**
+
+* [Design](/documentation/meta/design/) - Colors, typography, layout ideas for the migration.
+* [Writing](/documentation/meta/writing/) - How to write content for the new site.
+* [Markdown Reference](/documentation/meta/markdown/) - A reference for markdown formatting.
+
+### Overview
+
+The site is now being served as a statically built website.
+
+This means that the website is now being pre-compiled from various source files ahead of time.
+These files are then made available through the web server as static assets (nothing needs to be dynamically created on the server).
+This significantly reduces the server requirements (no in-between scripting language or database required) as well as reduces the possible attack vectors for malicious actors.
+
+The website will now be managed in a git repository.
+Pushes to the git repo will be reflected on the server for the branch that was pushed (see below).
+
+
+### Git Repository
+
+The digiKam website is now being version controlled in a [git repository][].
+
+If you have a [developer account][] (you have been granted push access) you can get the website by cloning it with this address:
+
+
+ git clone git@git.kde.org:websites/digikam-org
+
+If you want to view the website or write content and create a patch to publish (that you'll submit to someone with push access) you can get the website by cloning it with this address:
+Note: If you just need to write new content for the website, you can do this step and send a patch to the developers (or you can zip up your markdown file + assets and send that along as well).
+1. Download or install Hugo (at least v0.19) (and put it in your path).
+2. Clone the [digikam-org website from the git repository].
+3. Open a terminal and navigate to `/path/to/digikam-org/`
+4. Use the `hugo new` command to create new content. For example, the command `hugo new news/2017-01-01-my-new-post.md` creates a new News article with the necessary metadata.
+5. Open the new file in your text editor of choice.
+6. Fill in the YAML metadata at the top of the file.
+7. Write the page content in markdown.
+4. Visually inspect your new post using the command `hugo serve`. Open a web browser and go to http://localhost:1313
+
+### Markdown
+
+Markdown is a method for marking up plain text files with basic information and formatting using a very simple syntax.
+
+### File Naming Convention
+
+News items have been using a naming convention:
+
+`YYYY-MM-DD_The_News_Item_Descriptive_Name.md`
+
+You can use the `hugo new` command to create new content using a template. The template will automatically be chosen according to what path your choose to create your new content. For example, `hugo new news/2000-01-01-the-party-is-over.md` will use the news template located in `digikam-org/archetypes/news.md`.
+
+Contributors can help ease management of data by following a similar convention. :)
+
+If they do not, the committer should probably remember to rename contributed files if possible (it won't break the build or anything, just makes it easier to manage files).
+For example, `digikam-org/static/img/news/2017-01-01_happy_new_year/ball-drop.jpg` would be the file system path to your image. You could then reference it from your news article ``. Note that the path starts with `/` making it an absolute location from the web server root.
+
+For other pages: `digikam-org/static/img/<page category>/`
+
+For example, `digikam-org/static/about/digikam-team-photo.jpg` would be the file system path to your image. You could then reference it from your news article ``. Note that the path starts with `/` making it an absolute location from the web server root.
+
+### Viewing the Site Locally
+
+Before submitting a patch or pushing to the git repo, you should preview the site locally and ensure that everything appears as you would like it to.
+
+You can view the site locally by completing the following steps:
+
+1. Download or install Hugo (at least v0.19) (and put it in your path).
+2. Clone the [digikam-org website from the git repository].
+3. Open a terminal and navigate to `/path/to/digikam-org/`
+4. Run the command `hugo serve`.
+5. Open a web browser and go to http://localhost:1313
+
+ You see the digiKam website.
+
+[digikam-org website from the git repository]: {{< ref "documentation/meta/index.md#git-repository" >}}
+
+### Publishing Changes
+
+#### Git Access
+
+If your account is a developer account (has push access to the repository), you can publish news items by committing and pushing to the repository.
+This should normally be done against the `dev` branch first to check that everything works and looks good.
+
+If so, it can then be merged into the `master` branch.
+
+#### Out-of-band Submissions
+
+If you do not have developer access to the website repository or did not want to clone the repo, you can submit your article in several ways:
+
+* Email the markdown content and images to someone with a developer account
+* Post the content to the mailing list
+* Use a gist or pastebin service to post the text, then send the link to someone with access
+* Open a bugzilla bug and include the text of the post
Version ported to Qt5 and KF5 frameworks. See this <a href="https://techbase.kde.org/Projects/Digikam/CodingSprint2014">wiki page</a> for details.</p>
<p>This version will include also GoSC 2015/2016 projects. See ideas at this <a href="https://community.kde.org/GSoC/2015/Ideas#digiKam">wiki page</a> for details.</p>
<ul>
<li>18/10/2015: 5.0.0-beta1</li>
<li>29/11/2015: 5.0.0-beta2</li>
<li>17/01/2016: 5.0.0-beta3</li>
<li>28/02/2016: 5.0.0-beta4</li>
<li>27/03/2016: 5.0.0-beta5</li>
<li>24/04/2016: 5.0.0-beta6</li>
<li>29/05/2016: 5.0.0-beta7</li>
<li>03/07/2016: 5.0.0</li>
<li>07/08/2016: 5.1.0</li>
<li>18/09/2016: 5.2.0</li>
<li>06/11/2016: 5.3.0</li>
<li>08/01/2017: 5.4.0 (ported to QtAv for Video Files support)</li>
-<a><h5>digiKam Software Collection 2.x Release Plan (not maintained anymore)</h5></a>
+<a><h3>digiKam Software Collection 2.x Release Plan (not maintained anymore)</h3></a>
<p>
Version including XMP Sidecar support, Face Recognition, Image Versioning, and Reverse Geo-location, Color and Pick labels, Tags keyboard shortcuts, Group of items, etc...
+One of the best ways to help and support our work is to donate to the project.
+We use funds to purchase equipment relevant to photography that we want to support in digiKam.
+We also find value in being able to attend open source events such as meetings and coding sprints.
+Donations help to offset the costs that team members incur for attending these events.
+
+As described in <a href="http://www.packtpub.com/article/the-economics-of-open-source-donations">The Economics of Open Source Donations</a>, financial contributions play a crucial role in support Free/Libre and Open Source Software projects.
+
+Almost every person and every organization can support the digiKam project. Whether you are an individual, or represent a company, an administration or a University, your contribution can take many forms:
+
+
+### For individuals
+
+#### Make a Donation
+
+If you would like to help digiKam project to promote the development and usage of the digiKam photo manager and its by-products, you can use Paypal buttons listed below or use the Flattr link. Making payments with **PayPal** or donations with **[Flattr][]**, is fast, free and secure.
+
+[Flattr]: https://flattr.com/profile/digikam "digiKam on Flattr"
+<a href="https://flattr.com/profile/digikam" title="digiKam on Flattr"><img src="http://farm9.staticflickr.com/8111/8518458812_720cd7256a_m.jpg" alt="digiKam on Flattr" width="240" height="81"></a>
+
+Your name will be added to the list below.
+
+
+
+### For companies and administrations
+
+Companies or administrations willing to become a new sponsor of digiKam project can reach us <a href="mailto:caulier dot gilles at gmail dot com">by e-mail</a> for details.
+<img src="https://farm4.staticflickr.com/3940/15028102934_b9f16f1849_o.png" title="Entertainment where You want it (excito.com)" width="151" height="72">
+
+* Per Jensen
+* Joel Hallklint
+* George Shuklin
+* John Bestevaar
+* Norbert Eisinger
+* Thomas Arnold
+* John Bestevaar
+* Matti Rintala
+* Eric Keller
+* Philip M Thomas
+* Dmitri Popov
+* Thierry Nemes
+* Thomas Guettler
+* Stephan Martin
+* Philippe Quaglia
+* Sankarshan Mukhopadhyay
+* Alexey Chelmodeev
+* Steffen Eibicht
+* Rinus Bakker
+* Carla Schroder
+* Daniel Baer
+* Vincent Audibert
+* Sam Shefrin
+* Chieh Teng
+* Robert Zmigrodzki
+* Fabrizio Arias
+* Manfred Mislik
+* Chambers Tristan
+* Radek Jun
+* Philippe Dezac
+* Orlando Gonzalez
+* Alan Alpert
+* Robert Rader
+* Jean-Baptiste Rouquier
+* Martin Senftleben
+* Jörg Platte
+* Moritz Klingmann
+* Sam Shefrin
+* Vincent Körber
+* Michael Gajda
+* Roger Larsson
+* Mark Fraser
+* Francois Guay
+* Sylvain Leterreur
+* Harald Ulver
+* Denis Zalevskiy
+* Krzysztof Onak
+* Raymond Meijer
+* Kamil Stepinski
+* Christoph Baldauf
+* Martin Zahnd
+* Andreas Schroeder
+* Michael Beckmann
+* Franck Costa
+* Harald Wilmersdorf
+* Bernhard Hennlich
+
+---
+
+#### 2010
+
+
+<img src="https://farm6.staticflickr.com/5600/15462642628_ba22acb219_o.gif" title="Sino-Pictures, a photo agency from China (sinopictures.com)" width="167" height="67"><br>
-You can start by promoting digiKam to your friends and colleagues by showing them how powerful digiKam is :)
-</p>
-
-<p>
-You are also welcome to strongly test all digiKam features and to report bugs, see below.
-</p>
-
-<p>
-Subscribing to digiKam-users and helping newbies is also a good way to increase the number of digiKam users !
-</p>
-
-<p>
-If you are new to the free software world, we recommend to take a look at <a href="http://schlitt.info/opensource/blog/0541_10_golden_rules_for_starting_with_open_source.html">this article</a> which summarizes they way open source projects work very well.
-</p>
-
-<a name="bugsreport"><h1>Reporting bugs and wishes</h1></a>
-
-<p>
-Please use the bug tracking system for all bug-reports and new feature wishlists. Take a look at <a href="/?q=support">support page</a> for details.
-</p>
-
-<h1>If you are experiencing crashes with digiKam</h1>
-
-<p>
-If you found a context to crash digiKam, you can provide a backtrace using GDB debugger.
-digiKam needs to be compiled with all debug info else the backtrace will be useless.
-If you installed digiKam using the packages provided by your distribution please install the corresponding debug package. To find the name of these packages more information can be found <a href="http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports"> here</a>.
-
-In order to test recent changes made by the developers, it would be even better to build the current development version yourself,
-the instructions are given <a href="https://www.digikam.org/download?q=download/GIT">here</a>.
-
-</p><p>To get a backtrace under <b>Linux</b> with GDB, use following command:</p>
-
-<p>
-</p><pre>$ gdb digikam
-(gdb) catch throw
-(gdb) run
-(gdb) ...
-(gdb) _crash here_
-(gdb) ...
-(gdb) bt
-(gdb) _the backtrace is here_
-(gdb) quit
-</pre>
-<p></p>
-
-<p>
-For a detailed and very helpful guide on providing useful crash reports see <a href="http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_cra
-sh_reports">this guide</a>.
-</p>
-
-<p>
-For <b>Windows</b> users, The binary installer come with a dedicated GDB available in same installation directory than digiKam.
-</p>
-
-<p>
-For <b>MacOS</b> users, you can use <b>lldb</b> debugger from XCode command line tools-set as under Linux with GDB.
-digiKam trace main debug statements into the console while it run. Under Linux, just run digiKam from a console.
-</p>
-
-<p>Under <b>MacOS</b>, digiKam executable is installed at <i>/opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam</i>, and can be started directly from the console to see debug traces.</p>
-
-<p>Under <b>Windows</b>, no trace is printed to the console directly. You need to install <a href="http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx">DebugView tool</a> to capture debug traces generated by digiKam while it's running.</p>
-
-<h1>Submitting patches</h1>
-
-<p>
-You are welcome to propose patches. But, please read the <a href="https://cgit.kde.org/digikam.git/tree/HACKING">HACKING file</a> first.
-</p>
-
-<p>
-Send patches against the current version of the code (latest git/master revision), not the stable release or an old beta version published. Patches can be created with :
-</p>
-
-<p>
-</p><pre>git diff HEAD > mydiff.patch
-</pre>
-<p></p>
-
-<p>The patches must be attached to a new file in <a href="https://www.digikam.org/support">Bugzilla</a>. Please do not use mailing list or private mail.</p>
-
-<a name="translations"><h1>Translations</h1></a>
-
-<p>
-If you want to contribute to the digiKam internationalization effort, you need to contact directly the translation teams at <a href="http://l10n.kde.org/">http://l10n.kde.org/</a>.
-</p>
-
-<p>You can start by reading the <a href="http://l10n.kde.org/docs/translation-howto/">Translation HOWTO</a>.
-Help to our excellent documentation is always welcome. For all matters concerning it, write to digiKam developers mailing list. Our <a href="http://docs.kde.org/development/en/extragear-graphics/digikam/index.html">documentation</a> is established in <a href="http://l10n.kde.org/docs/doc-primer/index.html">docbook format standard</a>. This <a href="https://cgit.kde.org/digikam-doc.git/tree/README">README</a> file explains in more detail how to do structure the documents, how to do screenshots, compress them and so on.
-</p>
-
-<p>
-Even small additions/changes in ASCII format are possible, and should be create a new bugzilla entry with a patch against git/master code, so that they can be incorporated in the docbook.
-</p>
-
-<a name="samples"><h1>Pictures samples</h1></a>
-
-<p>
-We need some sample files produced by recent digital cameras, especially RAW and JPEG files from different manufacturers (like Canon, Nikon, Sony, Olympus, Sigma and so on).
-</p>
-
-<p>
-With these files, we'll be able to look at metadata (Maker-Notes) embedded in the files to improve their support in digiKam (via the exiv2 and libraw libraries).
-</p>
-
-<p>
-We also need sample files produced by all kind of applications (including other OS and proprietary software like Photoshop) that include IPTC/XMP metadata. It's to ensure compatibility with other tools and to test the new automatic import of this data in the digiKam database (comments and tags update and so on).
-If you is a photographer you can contribute to the digiKam to propose your best shots as splash-screens. Take a look <a href="http://www.digikam.org/splashcreens">at this page</a> for details.
-<p>You love digiKam ? You want to see this project become better and better in the future ? You can help us to sponsor the team... Like you can read in this <a href="http://www.packtpub.com/article/the-economics-of-open-source-donations">paper</a>, money is important for an open-source project.</p>
-
-<p>Almost every person and every organization can support digiKam project. Whether you are an individual, or represent a company, an administration or a University, your contribution can take many forms:</p>
-
-<h1 id="donation">For individuals: make a donation</h1>
-
-<p>If you would like to help digiKam project to promote development and usage of the digiKam photo manager and its by products, you can use Paypal buttons listed below or using Flattr link. Make payments with <b>PayPal</b> or donations with <b>Flattr</b>, is fast, free and secure.</p>
-<a href="https://flattr.com/profile/digikam" title="digiKam on Flattr"><img src="http://farm9.staticflickr.com/8111/8518458812_720cd7256a_m.jpg" alt="digiKam on Flattr" width="240" height="81"></a>
-
-<p></p>
-
-<p>Your name will be added to the list below.</p>
-
-<p>Money will be used to buy new cameras, lens, printers, GPS, or others devices relevant of photography to perform tests with digiKam. Also, it will help team to attend to open-source events as meetings and coding sprints.</p>
-
-<h1 id="enterprise">For companies and administrations</h1>
-
-<p>Companies or administrations willing to become a new sponsor of digiKam project can reach us <a href="mailto:caulier dot gilles at gmail dot com">by e-mail</a> for details.</p>
-
-<p>Thanks in advance for your generous donation...</p>
- <img src="https://farm6.staticflickr.com/5600/15462642628_ba22acb219_o.gif" title="Sino-Pictures, a photo agency from China (sinopictures.com)" width="167" height="67"><br>
- <img src="https://farm4.staticflickr.com/3940/15028102934_b9f16f1849_o.png" title="Entertainment where You want it (excito.com)" width="151" height="72">
<p>You can install digiKam using pre-compiled version. This is done by your distribution. A disadvantage is that in some cases the version provided by your distribution is not the latest stable version the digiKam team has released. The links given below will give you information about which version your distribution packages.</p>
<td><a href="http://packages.debian.org/search?searchon=names&keywords=digikam">here</a> and reason why the latest version of packages is not in testing can be found <a href="http://release.debian.org/migration/testing.pl?package=digikam">here</a></td>
<p>Here, we provide some usefull tips for getting a slightly more up-to-date version:</p>
<p>Under Ubuntu 10.10 you can use some PPA, look <a href="http://scribblesandsnaps.wordpress.com/2010/12/10/install-digikam-1-6-on-ubuntu-10-10/">here</a>.</p>
<p>The list of digiKam packages in FreshPorts can be found <a href="http://www.freshports.org/search.php?query=digikam&search=go&num=10&stype=name&method=match&deleted=excludedeleted&start=1&casesensitivity=caseinsensitive">here</a>.</p>
<p>digiKam for MacOS can installed using our self-contained package available on <a href="http://download.kde.org/stable/digikam/">download.kde.org</a>.</p>
<p>Be careful as digiKam is not as stable under MacOS as under Linux because of some bugs in the underlying KDE Software Collection libraries that digiKam depends on.</p>
<p>digiKam for Windows can installed using our self-contained installer available on <a href="http://download.kde.org/stable/digikam/">download.kde.org</a>.</p>
<p>Be careful as digiKam is not as stable under Windows as under Linux because of some bugs in the underlying KDE Software Collection libraries that digiKam depends on.</p>
-<div class="content"><p>Before you can use digiKam, you must first download and install it. There are many ways to achieve that:</p>
-<ul>
-<li>
-Use a compiled <a href="http://download.kde.org/stable/digikam/">official bundle</a> provided by the team.<br>
-This is the most easy way to test the recent stable version everywhere. This include universal Linux AppImage bundle, MacOS Package, and Windows Installer.
-</li>
-<li>
-Use a compiled <a href="?q=download/binary/">package</a> provided by your operating system.<br>
-Take a care, digiKam version can be outdated.
-</li>
-<li>
-Use a compiled <a href="https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM">pre-version bundle</a> provided by the team for testing purpose only.<br>
-This is the most easy way to try the current implementation not yet released officially. This include universal Linux AppImage bundle, MacOS Package, and Windows Installer.
-</li>
-<li>
-Compile the last source code archive from <a href="http://download.kde.org/stable/digikam/">official repository</a>.
-</li>
-<li>
-Compile the latest version from <a href="?q=download/GIT">git repository</a> where we currently work in.<br>
-This is even more complicated, but as recent as it gets. This is needed when you want to help us to find bugs or help us develop. This way is for peoples who want to contribute or if pre-version bundles are not enough to investigates problems at run-time.
-</li>
-</ul>
-<p>You can choose the one which fits you best. We provide detailed instructions for each of them.</p>
-<p>Note: check the <a href="?q=download/dependencies">dependencies</a> before trying to compile digiKam.</p>
-<h1>HOW TO GET DIGIKAM FROM GIT MASTER REPOSITORY</h1>
-<h3>Checkout source code</h3>
-<p>Note: check the <a href="?q=download/dependencies">dependencies</a> before trying to compile digiKam.
-</p>
-<p>To Checkout the <a href="https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation">digiKam Sofware Compilation</a> from GIT master repository, and enter these command lines in a clean directory:
+### How to get digiKam from git master repository
+
+#### Checkout source code
+
+Note: check the <a href="?q=download/dependencies">dependencies</a> before trying to compile digiKam.
+
+To Checkout the <a href="https://projects.kde.org/projects/extragear/graphics/digikam/digikam-software-compilation">digiKam Sofware Compilation</a> from GIT master repository, and enter these command lines in a clean directory:
-<p>To compile the source code under linux you have to give these commands in the source code folder. You should use a separate build folder to help cleaning up sources if something goes wrong. All configuration tasks can be performed by <b>bootstrap.linux</b> script.</p>
-<p><tt><br>
-</tt></p><div dir="ltr" align="left"><tt>
-# ./bootstrap.linux <br>
-# cd build <br>
-# make <br>
-# su <br>
+```
+
+
+
+### Installation in your Linux system
+
+To compile the source code under linux you have to give these commands in the source code folder. You should use a separate build folder to help cleaning up sources if something goes wrong. All configuration tasks can be performed by <b>bootstrap.linux</b> script.
-description: "Build and install digikam from a tarball."
+description: "Build and install digiKam from a tarball."
category: "download"
aliases: "/download/tarball"
---
<div class="content"><p>Installing a tarball will get you the most up-to-date stable version of digiKam. But it can happen that you run into all kinds of problems related to compiling. </p>
<p>So, if your distribution is running behind a lot, you can install a tarball.</p>
<p>Before installing a tarball, it is better to prevent conflicts to uninstall the digiKam and Kipi plugins packages provided by your distribution. </p>
<p>First you have to download digiKam from :</p>
<p>- This repository for <a href="http://download.kde.org/stable/digikam/">stable releases</a>.</p>
<p>- For older releases deprecated and not maintained <a href="http://download.kde.org/Attic/digikam/">look here</a>.</p>
<p>Second you need to install all digiKam <a href="?q=download/dependencies">dependencies</a>.</p>
<p>Extract the tarball via <code>tar -xvjf filename.bz2</code>, enter the extracted directory and then you need to issue a set of commands. You need to specify an installation prefix. This will be the base path of the installation. To determine the correct installation path, use <code>`kf5-config --prefix`</code> and provide it as a parameter for cmake, as shown in the example commands below:</p>
<p><code><br>
bootstrap.linux<br>
cd build<br>
make<br>
su<br>
make install<br>
</code></p>
<p>Notes: </p>
<p>- A bootstrap script is also available to configure for OSX through Macports.<br>
- A bootstrap script is also available to configure for Windows through MXE (cross compiling with MinGW). Forget a native compilation using Microsoft Visual C++. It's a waste of time as this compiler is a big weird puzzle...</p>
Planed at <a href="http://maps.google.de/maps?f=q&source=s_q&hl=de&geocode=&q=Bernhardstra%C3%9Fe+12,+Essen&sll=51.392833,7.024748&sspn=0.006494,0.019119&ie=UTF8&hq=&hnear=Bernhardstra%C3%9Fe+12,+Fischlaken+45239+Essen,+Nordrhein-Westfalen&ll=51.391681,7.026787&spn=0.006494,0.019119&z=16">Essen, Germany</a><br>
Date: 13 - 15 november<br>
Organized and hosted by Marcel Wiesweg<br>
Sponsored by <a href="http://ev.kde.org">KDE-ev</a><br>
<a href="http://www.flickr.com/photos/digikam/4107577420/" title="PICT2891.jpg by cauliergilles, on Flickr"><img src="http://farm3.static.flickr.com/2604/4107577420_71301d1155_m.jpg" alt="PICT2891.jpg" width="240" height="160"></a>
<a href="http://www.flickr.com/photos/digikam/4104932135/" title="PICT2892.jpg by cauliergilles, on Flickr"><img src="http://farm3.static.flickr.com/2602/4104932135_3cb3f69536_m.jpg" alt="PICT2892.jpg" width="240" height="160"></a>
</ul>
<p></p>
-<h5>2010</h5>
+<h3>2010</h3>
<p>
</p><ul>
<li><b>KDE Graphics Coding Sprint</b>:<br>
Planed at <a href="http://maps.google.com/maps?f=q&hl=en&q=1%2C%20Rue%20Emile%20Tavan%2C%2013100%20%2C%20Aix-en-Provence%2C%20France">Maison des associations Tavan, Aix en provence, France</a><br>
Date: 27 - 29 august<br>
Organized by Gilles Caulier<br>
Sponsored by <a href="http://ev.kde.org">KDE-ev</a><br>
description: "Dear digiKam fans and users, Following the 5th release 5.4.0 published in January 2017, the digiKam team is proud to announce the new release 5.5.0"
Following the <a href="https://www.digikam.org/node/764">5th release 5.4.0</a> published in January 2017, the digiKam team is proud to announce the new release 5.5.0 of digiKam Software Collection. As 5.4.0, this version introduces again several improvements in database interface.
</p>
<p>
This time, <b>Mario Frank</b> has significantly improved the threads management done in background to prevent an overload of the computer under intensive workload by batch processing of items. The maintenance now does not generate massive amounts of threads anymore. Instead, we use a queue based approach to level the load on the CPUs more appropriately. This should improve the re-activeness during maintenance.
He has also improved the similarity tool again by tunning the exactness of similarity recognition for external images dropped in fuzzy search. He also introduced a configurable lower bound for the minimum similarity in fuzzy and duplicates search as too low similarity values may make digiKam non-responsive. Also, the results of duplicates searches can now be restricted to the ones that are in the same album as the reference image or in another album. This feature is also usable in maintenance tool. Again, the reference image is more clearly identified by the description reference image in the image information in duplicates view.
</p>
<p>
Furthermore, he implemented a garbage collection for the digiKam databases. The application is now able to identify stale database objects (like deleted images, not used thumbnails and face identities) and to remove them. This garbage collection is a stage of the maintenance.
</p>
<p>
Cleaning the stale (deleted) images from database can also be configured as startup-job.
For SQLite, digiKam is now also able to shrink the database files. This is only done if the database files are not corrupted. For MySQL, the database shrinking support is currently deactivated as some necessary database commands cannot be used properly for the moment.
A student named <b>Ahmed Fathi</b>, has implemented a few enhancements in the batch queue manager Watermark tool. It is now possible to set the size of watermarks, adjust margin sizes, customize the text font, apply rotation manually, and respect orientation of image automatically. He also fix some dysfunctions when a watermark is placed over the image in special conditions.
Another contributor, <b>Jan Wolter</b>, has maintained, adapted, and finalized a patch since a very long time. This patch have been initially proposed for digiKam 4.x, and introducing a very important feature around the database: the ability to ignore some kind of directories while scanning collections. For example, NAS storage includes technical folders in collections used by the device, whose contents we don't want to include in database... for nothing. So, these new settings will be used while scanning collection to bypass these data and make the database registration process more efficient. Which kind of directories are to be ignored can be configured in the database section of the configuration.
<b>Wolfgang Scheffner</b> continue to works on the human <a href="https://docs.kde.org/trunk5/en/extragear-graphics/digikam/index.html">digiKam handbook</a>. He has updated again the contents for your pleasure to discover the photo management application in details. This time he update the Geolocation sections, as Correlator, Map view, and GPS editor. He has also give serious feedback to developers in minds to simplify the graphical interface, or to fix settings layout to be more comprehensive by end users. <b>Simon Frei</b>, after some long talks with Wolfgang, implement all remarks and patched the geolocation correlator interface to improve the ergonomy.
<b>Maik Qualmann</b> works… everywhere, in goal to kill a lot of small but important usability entries in bugs database. He spent a lot of time on improving code elsewhere in digiKam core for better readability for future students who will work with us while this summer. He manage report and users mailing list to ask if reports still valid with pre-release versions published as bundles, and kill redundant entries already reported in the past.
</p>
<p>
Face Management have also been improved a little bit about usability. It is now possible to remove face tags from people sidebar but preserve them in tags sidebar. Also, the recognized but unconfirmed faces are now visible both in the recognized face tags and also in a special tag called Unconfirmed. The list of proposed names have been improved too. For name assignment in people sidebar, you can now limit the recommendation list to face tags with a setup option. Finally, tags listed in the tags sidebar can now be marked as face tags via context menu if they are not already.
-This new digiKam version also includes latest <a href="”http://www.libraw.org/news/libraw-0-18-2”">libraw 0.18.2</a>, whose release coincided with the digiKam release schedule. This version of the raw decoder includes some new Raw camera supported and some fixes about Fuji and Sony camera decoding. The amount of RAW camera supported is about <b>931 models</b>.
+This new digiKam version also includes latest <a href="http://www.libraw.org/news/libraw-0-18-2">libraw 0.18.2</a>, whose release coincided with the digiKam release schedule. This version of the raw decoder includes some new Raw camera supported and some fixes about Fuji and Sony camera decoding. The amount of RAW camera supported is about <b>931 models</b>.
For furher information, take a look at the list of more than <a href="https://bugs.kde.org/buglist.cgi?f1=cf_versionfixedin&list_id=1427730&o1=equals&product=digikam&product=kipiplugins&query_format=advanced&v1=5.5.0"> 100 issues closed</a> in Bugzilla.
</p>
<p>
digiKam software collection source code tarball, Linux 32/64 bits AppImage bundles, MacOS package, and Windows 32/64 bits installers can be downloaded from <a href="http://download.kde.org/stable/digikam/">this repository</a>
</p>
<p>Happy digiKaming!</p>
<div class="legacy-comments">
- <a id="comment-21391"></a>
- <div class="comment comment-published">
- <h3 class="title"><a href="/node/765#comment-21391" class="active">Thank you!</a></h3> <div class="submitted">Submitted by DRB (not verified) on Tue, 2017-03-14 14:15.</div>
+ <div class="submitted">Submitted by DRB (not verified) on Tue, 2017-03-14 14:15.</div>
<div class="content">
<p>Thank you to all the contributors and of course the devs which pull everything together and continue to drive the project forward. I am excited about all the database related improvements!</p>
</div>
- <div class="links">» <ul class="links"><li class="comment_reply first last"><a href="/comment/reply/765/21391">reply</a></li>
-</ul></div>
+
</div>
-<a id="comment-21394"></a>
- <div class="comment comment-published">
- <h3 class="title"><a href="/node/765#comment-21394" class="active">Thank you</a></h3> <div class="submitted">Submitted by Jamou (not verified) on Wed, 2017-03-15 12:57.</div>
+ <div class="submitted">Submitted by Harry (not verified) on Wed, 2017-03-15 22:01.</div>
<div class="content">
<p>THANK you and your contributers very much for this great peace of software! I use it for many years and it's really cool not to be forced to use all these A***E Software, but to have a really good working alternative.</p>
<p>Greatings from Berlin, Germany.</p>
<p>Harry</p>
</div>
- <div class="links">» <ul class="links"><li class="comment_reply first last"><a href="/comment/reply/765/21399">reply</a></li>
-</ul></div>
+
</div>
-<a id="comment-21400"></a>
- <div class="comment comment-published">
- <h3 class="title"><a href="/node/765#comment-21400" class="active">digiKam handbook link bust.</a></h3> <div class="submitted">Submitted by Stephen Goodey (not verified) on Thu, 2017-03-16 10:11.</div>
+description: "digiKam gets a brand new static website."
+category: "news"
+---
+
+Notice something a bit different?
+
+So do we!
+
+The folks from the [PIXLS.US](https://pixls.us) community saw that digiKam needed an update to the old website (previously running on an older Drupal instance) for security reasons and they wanted to help out.
+So after several weeks of hard work, the digiKam team has deployed a new look-and-feel for the website that is easier to navigate and mobile-friendly.
+Don't worry, all the content from the old website has been preserved so all the old links should be fine. You can find the links to this content in the footer of the new site.
+
+There are still things in the new design that need a bit of polish, but none of these things are important enough to keep the new site from our users.
+
+Here is a summary of changes:
+
+- replaced Drupal 6 with [Hugo](https://gohugo.io)
+- posts and pages are now authored in markdown
+- website source and content stored in git and hosted on KDE's infrastructure
+- continuous integration builds and deploys the site on new commits
+
+You can find out more about the new site on the [meta](/documentation/meta/) and [writing](/documentation/meta/writing/) pages.
+
+You also open issues for the website using [digiKam bugzilla ]() or by sending email to the [mailing list][].
+description: "Buy the digiKam recipes book to learn cool tricks!"
+category: "documentation"
+aliases: "digikamrecipes"
+---
+
+digiKam is an immensely powerful photo management application, and mastering it requires time and effort. This book can help you to learn the ropes in the most efficient manner. Instead of explaining every digiKam’s feature, the book offers a collection of techniques that can help you to get the most out of this versatile tool.
+
+
+Five facts about the digiKam Recipes ebook:
+
+1. This is the first and only ebook about digiKam.
+2. The ebook was written in close cooperation with the digiKam developers.
+3. 50% of all ebook sales go to the digiKam project.
+4. The ebook is DRM-free, so you can read it using any ebook reader or software that supports the EPUB or MOBI format.
+5. You’ll receive all future editions of the ebook free of charge.
+
+The ebook released under the [Creative Commons Attribution-NonCommercial-ShareAlike 4.0 Unported](http://creativecommons.org/licenses/by-nc-sa/4.0/) license, so you are free to share the ebook and modify it as long as you share your modifications.
-description: "Buy the digiKam recipes book to learn cool tricks!"
-category: "merchandise"
-aliases: "/node/543"
----
-
-<p>
-digiKam is an immensely powerful photo management application, and mastering it requires time and effort. This book can help you to learn the ropes in the most efficient manner. Instead of explaining every digiKam’s feature, the book offers a collection of techniques that can help you to get the most out of this versatile tool.</p>
-<p>Five facts about the digiKam Recipes ebook:</p>
-<ol>
-<li>This is the first and only ebook about digiKam.</li>
-<li>The ebook was written in close cooperation with the digiKam developers.</li>
-<li>50% of all ebook sales go to the digiKam project.</li>
-<li>The ebook is DRM-free, so you can read it using any ebook reader or software that supports the EPUB or MOBI format.</li>
-<li>You’ll receive all future editions of the ebook free of charge.</li>
-</ol>
-
-<p>
-The ebook can be purchased through the <a href="http://www.amazon.com/dp/B004774LJS">Amazon Kindle Store</a>, <a href="https://play.google.com/store/books/details/Dmitri_Popov_digiKam_Recipes?id=T83DBAAAQBAJ">Google Play Store</a>, and <a href="https://gumroad.com/l/digikamrecipes">Gumroad</a>.
-</p>
-<p>
-The ebook released under the <a href="http://creativecommons.org/licenses/by-nc-sa/4.0/">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 Unported</a> license, so you are free to share the ebook and modify it as long as you share your modifications.
-<strong>First</strong>, read carefully the <a href="/?q=docs">digikam documentation</a>.
+<strong>First</strong>, read carefully the <a href="/documentation/">digikam documentation</a>.
<br> It's actively maintained and you should find most of what you need there.
</p>
<p>
-<strong>Then</strong>, if you still have questions, you should have a look in the <a href="/?q=faq/digikam">FAQ (Frequently Asked Questions)</a>.
+<strong>Then</strong>, if you still have questions, you should have a look in the <a href="/documentation/FAQ/">FAQ (Frequently Asked Questions)</a>.
</p>
<p>
-If you can't find an answer to your question, feel free to <a href="/?q=support#mailinglists">subscribe</a> to the digikam mailing list to get support.
+If you can't find an answer to your question, feel free to <a href="/support/#mailinglists">subscribe</a> to the digikam mailing list to get support.
<br>
If you think it's a bug, you can report it to bugzilla, see below.
</p>
<p></p>
-<a name="bugsreport"><h5>Reporting bugs and wishes</h5></a>
+<h3>Reporting bugs and wishes</h3>
<a href="http://www.flickr.com/photos/digikam/3378415145/" title="digikambugzilla by cauliergilles, on Flickr"><img src="http://farm4.static.flickr.com/3558/3378415145_9c2d19f395.jpg" alt="digikambugzilla" width="500" height="333"></a>
<p>
Please use the bug tracking system for all bug-reports and new feature wishlists. Take a care to use the right component to post a new file at the right place. You can checkout the current bug-reports and wishlists at these urls:</p>
<ul>
<li><a href="https://bugs.kde.org/component-report.cgi?product=digikam">digiKam bugs and wishes</a></li>
<li><a href="https://bugs.kde.org/component-report.cgi?product=kipiplugins">Kipi-plugins bugs and wishes</a></li>
</ul>
<p>digiKam use external libraries to manage metadata (<a href="http://www.exiv2.org">Exiv2</a>) and digital camera (<a href="http://www.gphoto.org">GPhoto</a>). Please use links listed below to reports specifics bugs relevant of these libraries:</p>
<ul>
<li><a href="http://dev.robotbattle.com/bugs/my_view_page.php">Exiv2 library bugs and wishes</a></li>
<li><a href="http://sourceforge.net/tracker/?group_id=8874&atid=108874">GPhoto library bugs and wishes</a></li>
</ul>
<p></p>
-<a name="mailinglists"><h5>Mailing list Subscribtion</h5></a>
+<h3>Mailing list Subscribtion</h3>
<ul>
<li>digikam-users<br>
<a href="https://mail.kde.org/mailman/listinfo/digikam-users">Mailing list subscription</a> for all questions, comments, suggestions, requests, and bug reports by the <b>digiKam users</b>. <a href="http://mail.kde.org/pipermail/digikam-users/">(Archives)</a>
<br>
with Nabble <a href="http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html">web interface and search engine</a>
</li>
<br>
<li>digikam-devel<br>
<a href="https://mail.kde.org/mailman/listinfo/digikam-devel">Mailing list subscription</a> for <b>digiKam developers</b> thread. <a href="http://mail.kde.org/pipermail/digikam-devel/">(Archives)</a>
<br>
with Nabble <a href="http://digikam.1695700.n4.nabble.com/digikam-devel-f1695701.html">web interface and search engine</a>
</li>
<br>
<li>kde-imaging<br>
<a href="https://mail.kde.org/mailman/listinfo/kde-imaging">Mailing list subscription</a> for all questions, comments, suggestions, requests, and bug reports by the <b>Kipi-plugins</b> users. <a href="http://mail.kde.org/pipermail/kde-imaging/">(Archives)</a>
description: "Various contact methods for digiKam"
category: "support"
aliases: "/contact"
---
<p>Please use our <a href="?q=support#bugsreport">Bugzilla links</a> for bugs report and wishes.</p>
<p>Please use our <a href="?q=support#mailinglists">mailing lists</a> for support.</p>
-<h1 class="margintop">IRC CHANNEL</h1>
+<h3 class="margintop">IRC CHANNEL</h3>
<p>You can find us on the <b>irc.freenode.net</b> network, channels <a href="irc://irc.freenode.net/#digikam" class="external" title="irc://irc.freenode.net/#digikam" rel="nofollow">#digikam</a>
<br>
You can use <a href="http://webchat.freenode.net/?channels=digikam">this url</a> to be connected on #digikam IRC channel using a web interface.
</p>
-<h1 class="margintop">TEAM</h1>
+<h3 class="margintop">TEAM</h3>
<p>See the list of current <a href="https://cgit.kde.org/digikam.git/tree/AUTHORS">digiKam team members</a>.</p>
<p>See the list of current <a href="https://cgit.kde.org/kipi-plugins.git/tree/AUTHORS">Kipi-plugins team members</a>.</p>
</div>
diff --git a/i18n/en.yaml b/i18n/en.yaml
index 2c8e5c92c..ec6601c94 100644
--- a/i18n/en.yaml
+++ b/i18n/en.yaml
@@ -1,47 +1,116 @@
- id: about
translation: "About"
- id: home
translation: "Home"
- id: recentPosts
translation: "Recent Posts"
- id: readMore
translation: "Read more →"
- id: translations
translation: "Translations"
- id: share
translation: "Share"
- id: paginatorPrevious
translation: "Previous page"
- id: paginatorNext
translation: "Next page"
- id: cookieMessage
translation: "This website uses cookies."
- id: cookieLink
translation: "Learn more."
- id: cookieDismiss
translation: "Got it!"
- id: backToTop
translation: "Back to top"
+- id: menu
+ translation: "Menu"
+
- id: links
translation: "Links"
+- id: download
+ translation: "Download"
+
+- id: news
+ translation: "News"
+
+- id: latestNews
+ translation: "Latest News"
+
+- id: siteDescription
+ translation: "Professional Photo Management with the Power of Open Source"
+
+- id: screenshots
+ translation: "Screenshots"
+
- id: recipesBookSidebar
translation: "digiKam Recipes Book"
- id: donateTitleSidbar
- translation: "Make a Donation"
+ translation: "Donate"
- id: donateBodySidebar
- translation: "Make your donation to support the digiKam project!"
+ translation: "Donate to support the digiKam project"
+
+- id: features
+ translation: "Features"
+
+- id: largeCollections
+ translation: "Large Collections"
+
+- id: largeCollectionsBody
+ translation: "digiKam can easily handle libraries containing more than 100,000 images"
+
+- id: efficientEditing
+ translation: "Efficient Editing Workflow"
+
+- id: efficientEditingBody
+ translation: "Process raw files, edit JPEGs, publish photos to social media"
+
+- id: openMetadata
+ translation: "Work with Metadata"
+
+- id: openMetadataBody
+ translation: "Harness the power of XMP. View and edit metadata"
+
+- id: freeSoftware
+ translation: "Free and Open Source"
+
+- id: freeSoftwareBody
+ translation: "digiKam is an open-source application that respects your freedom"
+
+- id: by
+ translation: "by"
+
+- id: followUs
+ translation: "Follow us"
+
+- id: documentation
+ translation: "Documentation"
+
+- id: donate
+ translation: "Donate"
+
+- id: support
+ translation: "Support"
+
+- id: copyright
+ translation: "Except where otherwise noted, content on this site is licensed under a [Creative Commons Attribution 4.0 International license](https://creativecommons.org/licenses/by-sa/4.0/)."
+ id="tspan4618">digiKam</tspan> powered by Open Source www.digikam.org</textPath></text>
+ <text
+ style="font-style:normal;font-weight:normal;font-size:10px;font-family:'Bitstream Vera Sans';fill:url(#radialGradient3403);fill-opacity:1;stroke:none"
+ d="m -1650.5066,213.49129 c -83.9581,0 -152.113,68.15468 -152.1128,152.11292 0,50.3445 24.5241,94.98024 62.2488,122.66431 l 81.2701,-72.36106 -28.2168,-13.75032 -112.4661,-9.4247 -0.9454,-4.55479 110.8906,9.22417 -10.2841,-29.8783 -74.9106,-88.31716 2.2918,-3.52352 74.2517,86.65567 13.693,-28.33139 8.9377,-118.13817 4.2397,-0.40105 -8.4221,115.90374 32.17,-11.0862 0.2866,0.14324 85.4144,-80.48994 c -25.3374,-18.39614 -54.07,-26.44745 -88.3365,-26.44745 z m 92.4171,29.5952 -84.4791,79.23286 25.8902,14.06039 116.1931,4.01107 c -6.1335,-38.3839 -28.5375,-75.05806 -57.6042,-97.30432 z m -56.0073,98.19684 9.1383,31.62574 77.6893,81.49929 c 19.0245,-25.39267 28.847,-54.65287 28.847,-88.80415 0,-6.718 -0.4434,-13.33456 -1.2892,-19.82338 l -114.3854,-4.4975 z m 7.1054,36.35016 -12.2904,27.50289 -8.1356,110.80466 c 39.6252,-6.04635 73.6613,-25.97455 97.0268,-56.40776 l -76.6008,-81.89979 z m -17.0171,28.99251 -29.7637,10.82837 -82.903,73.56422 c 25.0994,18.26418 52.7753,26.66988 86.1686,26.66989 6.3136,0 12.5372,-0.39737 18.649,-1.14586 l 7.8491,-109.91662 z"
+ d="m 365.49344,213.49129 c -83.95817,0 -152.11301,68.15468 -152.11282,152.11292 0,50.3445 24.52406,94.98024 62.2488,122.66431 l 81.27007,-72.36106 -28.21675,-13.75032 -112.46616,-9.4247 -0.94539,-4.55479 110.89065,9.22417 -10.28413,-29.8783 -74.91056,-88.31716 2.29172,-3.52352 74.25173,86.65567 13.69303,-28.33139 8.93771,-118.13817 4.23968,-0.40105 -8.42207,115.90374 32.16997,-11.0862 0.28656,0.14324 85.41442,-80.48994 C 428.49246,221.5426 399.75988,213.49129 365.49344,213.49129 Z m 92.4171,29.5952 -84.47913,79.23286 25.89021,14.06039 116.19304,4.01107 c -6.13346,-38.3839 -28.53741,-75.05806 -57.60412,-97.30432 z m -56.00735,98.19684 9.13828,31.62574 77.68931,81.49929 c 19.02449,-25.39267 28.84698,-54.65287 28.84698,-88.80415 0,-6.718 -0.4434,-13.33456 -1.28914,-19.82338 l -114.38543,-4.4975 z m 7.10543,36.35016 -12.2904,27.50289 -8.1356,110.80466 c 39.62521,-6.04635 73.66129,-25.97455 97.02675,-56.40776 l -76.60075,-81.89979 z m -17.01712,28.99251 -29.76366,10.82837 -82.90307,73.56422 c 25.09947,18.26418 52.77529,26.66988 86.16867,26.66989 6.31351,0 12.53718,-0.39737 18.64892,-1.14586 L 391.9915,406.626 Z"
+ style="font-weight:normal;-inkscape-font-specification:'Liberation Sans';fill:#000000;fill-opacity:1">digiKam</tspan> powered by Open Source www.digikam.org</textPath></text>
+ style="font-style:normal;font-weight:normal;font-size:10px;font-family:'Bitstream Vera Sans';fill:url(#radialGradient5805);fill-opacity:1;stroke:none"><textPath
+ style="font-weight:normal;-inkscape-font-specification:'Liberation Sans';fill:url(#radialGradient5805);fill-opacity:1">digiKam</tspan> powered by Open Source www.digikam.org</textPath></text>
+ d="m -1650.5066,213.49129 c -83.9581,0 -152.113,68.15468 -152.1128,152.11292 0,50.3445 24.5241,94.98024 62.2488,122.66431 l 81.2701,-72.36106 -28.2168,-13.75032 -112.4661,-9.4247 -0.9454,-4.55479 110.8906,9.22417 -10.2841,-29.8783 -74.9106,-88.31716 2.2918,-3.52352 74.2517,86.65567 13.693,-28.33139 8.9377,-118.13817 4.2397,-0.40105 -8.4221,115.90374 32.17,-11.0862 0.2866,0.14324 85.4144,-80.48994 c -25.3374,-18.39614 -54.07,-26.44745 -88.3365,-26.44745 z m 92.4171,29.5952 -84.4791,79.23286 25.8902,14.06039 116.1931,4.01107 c -6.1335,-38.3839 -28.5375,-75.05806 -57.6042,-97.30432 z m -56.0073,98.19684 9.1383,31.62574 77.6893,81.49929 c 19.0245,-25.39267 28.847,-54.65287 28.847,-88.80415 0,-6.718 -0.4434,-13.33456 -1.2892,-19.82338 l -114.3854,-4.4975 z m 7.1054,36.35016 -12.2904,27.50289 -8.1356,110.80466 c 39.6252,-6.04635 73.6613,-25.97455 97.0268,-56.40776 l -76.6008,-81.89979 z m -17.0171,28.99251 -29.7637,10.82837 -82.903,73.56422 c 25.0994,18.26418 52.7753,26.66988 86.1686,26.66989 6.3136,0 12.5372,-0.39737 18.649,-1.14586 l 7.8491,-109.91662 z"
+ d="m 365.49344,213.49129 c -83.95817,0 -152.11301,68.15468 -152.11282,152.11292 0,50.3445 24.52406,94.98024 62.2488,122.66431 l 81.27007,-72.36106 -28.21675,-13.75032 -112.46616,-9.4247 -0.94539,-4.55479 110.89065,9.22417 -10.28413,-29.8783 -74.91056,-88.31716 2.29172,-3.52352 74.25173,86.65567 13.69303,-28.33139 8.93771,-118.13817 4.23968,-0.40105 -8.42207,115.90374 32.16997,-11.0862 0.28656,0.14324 85.41442,-80.48994 C 428.49246,221.5426 399.75988,213.49129 365.49344,213.49129 Z m 92.4171,29.5952 -84.47913,79.23286 25.89021,14.06039 116.19304,4.01107 c -6.13346,-38.3839 -28.53741,-75.05806 -57.60412,-97.30432 z m -56.00735,98.19684 9.13828,31.62574 77.68931,81.49929 c 19.02449,-25.39267 28.84698,-54.65287 28.84698,-88.80415 0,-6.718 -0.4434,-13.33456 -1.28914,-19.82338 l -114.38543,-4.4975 z m 7.10543,36.35016 -12.2904,27.50289 -8.1356,110.80466 c 39.62521,-6.04635 73.66129,-25.97455 97.02675,-56.40776 l -76.60075,-81.89979 z m -17.01712,28.99251 -29.76366,10.82837 -82.90307,73.56422 c 25.09947,18.26418 52.77529,26.66988 86.16867,26.66989 6.31351,0 12.53718,-0.39737 18.64892,-1.14586 L 391.9915,406.626 Z"
- plugin[prop] = null; //clean up script to prep for garbage collection.
- }
- return;
- },
-
- /**
- * @function
- * Causes one or more active plugins to re-initialize, resetting event listeners, recalculating positions, etc.
- * @param {String} plugins - optional string of an individual plugin key, attained by calling `$(element).data('pluginName')`, or string of a plugin class i.e. `'dropdown'`
- * @default If no argument is passed, reflow all currently active plugins.
- */
- reInit: function reInit(plugins) {
- var isJQ = plugins instanceof $;
- try {
- if (isJQ) {
- plugins.each(function () {
- $(this).data('zfPlugin')._init();
- });
- } else {
- var type = typeof plugins === 'undefined' ? 'undefined' : _typeof(plugins),
- throw new ReferenceError("We're sorry, '" + method + "' is not an available method for " + (plugClass ? functionName(plugClass) : 'this element') + '.');
- }
- } else {
- //error for invalid argument type
- throw new TypeError('We\'re sorry, ' + type + ' is not a valid parameter. You must use a string representing the method you wish to invoke.');
- }
- return this;
- };
-
- window.Foundation = Foundation;
- $.fn.foundation = foundation;
-
- // Polyfill for requestAnimationFrame
- (function () {
- if (!Date.now || !window.Date.now) window.Date.now = Date.now = function () {
- return new Date().getTime();
- };
-
- var vendors = ['webkit', 'moz'];
- for (var i = 0; i < vendors.length && !window.requestAnimationFrame; ++i) {
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Abide module.
- * @module foundation.abide
- */
-
- var Abide = function () {
- /**
- * Creates a new instance of Abide.
- * @class
- * @fires Abide#init
- * @param {Object} element - jQuery object to add the trigger to.
- * @param {Object} options - Overrides to the default plugin settings.
- // If the pattern name isn't also the type attribute of the field, then test it as a regexp
- else if (pattern !== $el.attr('type')) {
- valid = new RegExp(pattern).test(inputText);
- } else {
- valid = true;
- }
- }
- // An empty field is valid if it's not required
- else if (!$el.prop('required')) {
- valid = true;
- }
-
- return valid;
- }
-
- /**
- * Determines whether or a not a radio input is valid based on whether or not it is required and selected. Although the function targets a single `<input>`, it validates by checking the `required` and `checked` properties of all radio buttons in its group.
- * @param {String} groupName - A string that specifies the name of a radio button group
- * @returns {Boolean} Boolean value depends on whether or not at least one radio input has been selected (if it's required)
- */
-
- }, {
- key: 'validateRadio',
- value: function validateRadio(groupName) {
- // If at least one radio in the group has the `required` attribute, the group is considered required
- // Per W3C spec, all radio buttons in a group should have `required`, but we're being nice
- var $group = this.$element.find(':radio[name="' + groupName + '"]');
- var valid = false,
- required = false;
-
- // For the group to be required, at least one radio needs to be required
- $group.each(function (i, e) {
- if ($(e).attr('required')) {
- required = true;
- }
- });
- if (!required) valid = true;
-
- if (!valid) {
- // For the group to be valid, at least one radio needs to be checked
- $group.each(function (i, e) {
- if ($(e).prop('checked')) {
- valid = true;
- }
- });
- };
-
- return valid;
- }
-
- /**
- * Determines if a selected input passes a custom validation function. Multiple validations can be used, if passed to the element with `data-validator="foo bar baz"` in a space separated listed.
- * @param {Object} $el - jQuery input element.
- * @param {String} validators - a string of function names matching functions in the Abide.options.validators object.
- * @param {Boolean} required - self explanatory?
- * @returns {Boolean} - true if validations passed.
- */
-
- }, {
- key: 'matchValidation',
- value: function matchValidation($el, validators, required) {
- var _this4 = this;
-
- required = required ? true : false;
-
- var clear = validators.split(' ').map(function (v) {
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Accordion module.
- * @module foundation.accordion
- * @requires foundation.util.keyboard
- * @requires foundation.util.motion
- */
-
- var Accordion = function () {
- /**
- * Creates a new instance of an accordion.
- * @class
- * @fires Accordion#init
- * @param {jQuery} element - jQuery object to make into an accordion.
- * @param {Object} options - a plain object with settings to override the default options.
- * Amount of time to animate the opening of an accordion pane.
- * @option
- * @type {number}
- * @default 250
- */
- slideSpeed: 250,
- /**
- * Allow the accordion to have multiple open panes.
- * @option
- * @type {boolean}
- * @default false
- */
- multiExpand: false,
- /**
- * Allow the accordion to close all panes.
- * @option
- * @type {boolean}
- * @default false
- */
- allowAllClosed: false,
- /**
- * Allows the window to scroll to content of pane specified by hash anchor
- * @option
- * @type {boolean}
- * @default false
- */
- deepLink: false,
-
- /**
- * Adjust the deep link scroll to make sure the top of the accordion panel is visible
- * @option
- * @type {boolean}
- * @default false
- */
- deepLinkSmudge: false,
-
- /**
- * Animation time (ms) for the deep link adjustment
- * @option
- * @type {number}
- * @default 300
- */
- deepLinkSmudgeDelay: 300,
-
- /**
- * Update the browser history with the open accordion
- * @option
- * @type {boolean}
- * @default false
- */
- updateHistory: false
- };
-
- // Window exports
- Foundation.plugin(Accordion, 'Accordion');
-}(jQuery);
-'use strict';
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * AccordionMenu module.
- * @module foundation.accordionMenu
- * @requires foundation.util.keyboard
- * @requires foundation.util.motion
- * @requires foundation.util.nest
- */
-
- var AccordionMenu = function () {
- /**
- * Creates a new instance of an accordion menu.
- * @class
- * @fires AccordionMenu#init
- * @param {jQuery} element - jQuery object to make into an accordion menu.
- * @param {Object} options - Overrides to the default plugin settings.
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Drilldown module.
- * @module foundation.drilldown
- * @requires foundation.util.keyboard
- * @requires foundation.util.motion
- * @requires foundation.util.nest
- */
-
- var Drilldown = function () {
- /**
- * Creates a new instance of a drilldown menu.
- * @class
- * @param {jQuery} element - jQuery object to make into an accordion menu.
- * @param {Object} options - Overrides to the default plugin settings.
- * Markup used for JS generated back button. Prepended or appended (see backButtonPosition) to submenu lists and deleted on `destroy` method, 'js-drilldown-back' class required. Remove the backslash (`\`) if copy and pasting.
- * Position the back button either at the top or bottom of drilldown submenus. Can be `'left'` or `'bottom'`.
- * @option
- * @type {string}
- * @default top
- */
- backButtonPosition: 'top',
- /**
- * Markup used to wrap drilldown menu. Use a class name for independent styling; the JS applied class: `is-drilldown` is required. Remove the backslash (`\`) if copy and pasting.
- * @option
- * @type {string}
- * @default '<div></div>'
- */
- wrapper: '<div></div>',
- /**
- * Adds the parent link to the submenu.
- * @option
- * @type {boolean}
- * @default false
- */
- parentLink: false,
- /**
- * Allow the menu to return to root list on body click.
- * @option
- * @type {boolean}
- * @default false
- */
- closeOnClick: false,
- /**
- * Allow the menu to auto adjust height.
- * @option
- * @type {boolean}
- * @default false
- */
- autoHeight: false,
- /**
- * Animate the auto adjust height.
- * @option
- * @type {boolean}
- * @default false
- */
- animateHeight: false,
- /**
- * Scroll to the top of the menu after opening a submenu or navigating back using the menu back button
- * @option
- * @type {boolean}
- * @default false
- */
- scrollTop: false,
- /**
- * String jquery selector (for example 'body') of element to take offset().top from, if empty string the drilldown menu offset().top is taken
- * @option
- * @type {string}
- * @default ''
- */
- scrollTopElement: '',
- /**
- * ScrollTop offset
- * @option
- * @type {number}
- * @default 0
- */
- scrollTopOffset: 0,
- /**
- * Scroll animation duration
- * @option
- * @type {number}
- * @default 500
- */
- animationDuration: 500,
- /**
- * Scroll animation easing. Can be `'swing'` or `'linear'`.
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Dropdown module.
- * @module foundation.dropdown
- * @requires foundation.util.keyboard
- * @requires foundation.util.box
- * @requires foundation.util.triggers
- */
-
- var Dropdown = function () {
- /**
- * Creates a new instance of a dropdown.
- * @class
- * @param {jQuery} element - jQuery object to make into a dropdown.
- * Object should be of the dropdown panel, rather than its anchor.
- * @param {Object} options - Overrides to the default plugin settings.
- * Class that designates bounding container of Dropdown (default: window)
- * @option
- * @type {?string}
- * @default null
- */
- parentClass: null,
- /**
- * Amount of time to delay opening a submenu on hover event.
- * @option
- * @type {number}
- * @default 250
- */
- hoverDelay: 250,
- /**
- * Allow submenus to open on hover events
- * @option
- * @type {boolean}
- * @default false
- */
- hover: false,
- /**
- * Don't close dropdown when hovering over dropdown pane
- * @option
- * @type {boolean}
- * @default false
- */
- hoverPane: false,
- /**
- * Number of pixels between the dropdown pane and the triggering element on open.
- * @option
- * @type {number}
- * @default 1
- */
- vOffset: 1,
- /**
- * Number of pixels between the dropdown pane and the triggering element on open.
- * @option
- * @type {number}
- * @default 1
- */
- hOffset: 1,
- /**
- * Class applied to adjust open position. JS will test and fill this in.
- * @option
- * @type {string}
- * @default ''
- */
- positionClass: '',
- /**
- * Allow the plugin to trap focus to the dropdown pane if opened with keyboard commands.
- * @option
- * @type {boolean}
- * @default false
- */
- trapFocus: false,
- /**
- * Allow the plugin to set focus to the first focusable element within the pane, regardless of method of opening.
- * @option
- * @type {boolean}
- * @default false
- */
- autoFocus: false,
- /**
- * Allows a click on the body to close the dropdown.
- * @option
- * @type {boolean}
- * @default false
- */
- closeOnClick: false
- };
-
- // Window exports
- Foundation.plugin(Dropdown, 'Dropdown');
-}(jQuery);
-'use strict';
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * DropdownMenu module.
- * @module foundation.dropdown-menu
- * @requires foundation.util.keyboard
- * @requires foundation.util.box
- * @requires foundation.util.nest
- */
-
- var DropdownMenu = function () {
- /**
- * Creates a new instance of DropdownMenu.
- * @class
- * @fires DropdownMenu#init
- * @param {jQuery} element - jQuery object to make into a dropdown menu.
- * @param {Object} options - Overrides to the default plugin settings.
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Equalizer module.
- * @module foundation.equalizer
- * @requires foundation.util.mediaQuery
- * @requires foundation.util.timerAndImageLoader if equalizer contains images
- */
-
- var Equalizer = function () {
- /**
- * Creates a new instance of Equalizer.
- * @class
- * @fires Equalizer#init
- * @param {Object} element - jQuery object to add the trigger to.
- * @param {Object} options - Overrides to the default plugin settings.
- * Enable height equalization when stacked on smaller screens.
- * @option
- * @type {boolean}
- * @default false
- */
- equalizeOnStack: false,
- /**
- * Enable height equalization row by row.
- * @option
- * @type {boolean}
- * @default false
- */
- equalizeByRow: false,
- /**
- * String representing the minimum breakpoint size the plugin should equalize heights on.
- * @option
- * @type {string}
- * @default ''
- */
- equalizeOn: ''
- };
-
- // Window exports
- Foundation.plugin(Equalizer, 'Equalizer');
-}(jQuery);
-'use strict';
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Interchange module.
- * @module foundation.interchange
- * @requires foundation.util.mediaQuery
- * @requires foundation.util.timerAndImageLoader
- */
-
- var Interchange = function () {
- /**
- * Creates a new instance of Interchange.
- * @class
- * @fires Interchange#init
- * @param {Object} element - jQuery object to add the trigger to.
- * @param {Object} options - Overrides to the default plugin settings.
- * Rules to be applied to Interchange elements. Set with the `data-interchange` array notation.
- * @option
- * @type {?array}
- * @default null
- */
- rules: null
- };
-
- Interchange.SPECIAL_QUERIES = {
- 'landscape': 'screen and (orientation: landscape)',
- 'portrait': 'screen and (orientation: portrait)',
- 'retina': 'only screen and (-webkit-min-device-pixel-ratio: 2), only screen and (min--moz-device-pixel-ratio: 2), only screen and (-o-min-device-pixel-ratio: 2/1), only screen and (min-device-pixel-ratio: 2), only screen and (min-resolution: 192dpi), only screen and (min-resolution: 2dppx)'
- };
-
- // Window exports
- Foundation.plugin(Interchange, 'Interchange');
-}(jQuery);
-'use strict';
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Magellan module.
- * @module foundation.magellan
- */
-
- var Magellan = function () {
- /**
- * Creates a new instance of Magellan.
- * @class
- * @fires Magellan#init
- * @param {Object} element - jQuery object to add the trigger to.
- * @param {Object} options - Overrides to the default plugin settings.
- * Number of pixels to use as a marker for location changes.
- * @option
- * @type {number}
- * @default 50
- */
- threshold: 50,
- /**
- * Class applied to the active locations link on the magellan container.
- * @option
- * @type {string}
- * @default 'active'
- */
- activeClass: 'active',
- /**
- * Allows the script to manipulate the url of the current page, and if supported, alter the history.
- * @option
- * @type {boolean}
- * @default false
- */
- deepLinking: false,
- /**
- * Number of pixels to offset the scroll of the page on item click if using a sticky nav bar.
- * @option
- * @type {number}
- * @default 0
- */
- barOffset: 0
- };
-
- // Window exports
- Foundation.plugin(Magellan, 'Magellan');
-}(jQuery);
-'use strict';
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * OffCanvas module.
- * @module foundation.offcanvas
- * @requires foundation.util.keyboard
- * @requires foundation.util.mediaQuery
- * @requires foundation.util.triggers
- * @requires foundation.util.motion
- */
-
- var OffCanvas = function () {
- /**
- * Creates a new instance of an off-canvas wrapper.
- * @class
- * @fires OffCanvas#init
- * @param {Object} element - jQuery object to initialize.
- * @param {Object} options - Overrides to the default plugin settings.
- * @param {jQuery} trigger - element that triggered the off-canvas to open.
- */
-
- }, {
- key: 'toggle',
- value: function toggle(event, trigger) {
- if (this.$element.hasClass('is-open')) {
- this.close(event, trigger);
- } else {
- this.open(event, trigger);
- }
- }
-
- /**
- * Handles keyboard input when detected. When the escape key is pressed, the off-canvas menu closes, and focus is restored to the element that opened the menu.
- * @function
- * @private
- */
-
- }, {
- key: '_handleKeyboard',
- value: function _handleKeyboard(e) {
- var _this2 = this;
-
- Foundation.Keyboard.handleKey(e, 'OffCanvas', {
- close: function close() {
- _this2.close();
- _this2.$lastTrigger.focus();
- return true;
- },
- handled: function handled() {
- e.stopPropagation();
- e.preventDefault();
- }
- });
- }
-
- /**
- * Destroys the offcanvas plugin.
- * @function
- */
-
- }, {
- key: 'destroy',
- value: function destroy() {
- this.close();
- this.$element.off('.zf.trigger .zf.offcanvas');
- this.$overlay.off('.zf.offcanvas');
-
- Foundation.unregisterPlugin(this);
- }
- }]);
-
- return OffCanvas;
- }();
-
- OffCanvas.defaults = {
- /**
- * Allow the user to click outside of the menu to close it.
- * @option
- * @type {boolean}
- * @default true
- */
- closeOnClick: true,
-
- /**
- * Adds an overlay on top of `[data-off-canvas-content]`.
- * @option
- * @type {boolean}
- * @default true
- */
- contentOverlay: true,
-
- /**
- * Enable/disable scrolling of the main content when an off canvas panel is open.
- * @option
- * @type {boolean}
- * @default true
- */
- contentScroll: true,
-
- /**
- * Amount of time in ms the open and close transition requires. If none selected, pulls from body style.
- * @option
- * @type {number}
- * @default 0
- */
- transitionTime: 0,
-
- /**
- * Type of transition for the offcanvas menu. Options are 'push', 'detached' or 'slide'.
- * @option
- * @type {string}
- * @default push
- */
- transition: 'push',
-
- /**
- * Force the page to scroll to top or bottom on open.
- * @option
- * @type {?string}
- * @default null
- */
- forceTo: null,
-
- /**
- * Allow the offcanvas to remain open for certain breakpoints.
- * @option
- * @type {boolean}
- * @default false
- */
- isRevealed: false,
-
- /**
- * Breakpoint at which to reveal. JS will use a RegExp to target standard classes, if changing classnames, pass your class with the `revealClass` option.
- * @option
- * @type {?string}
- * @default null
- */
- revealOn: null,
-
- /**
- * Force focus to the offcanvas on open. If true, will focus the opening trigger on close.
- * @option
- * @type {boolean}
- * @default true
- */
- autoFocus: true,
-
- /**
- * Class used to force an offcanvas to remain open. Foundation defaults for this are `reveal-for-large` & `reveal-for-medium`.
- * @option
- * @type {string}
- * @default reveal-for-
- * @todo improve the regex testing for this.
- */
- revealClass: 'reveal-for-',
-
- /**
- * Triggers optional focus trapping when opening an offcanvas. Sets tabindex of [data-off-canvas-content] to -1 for accessibility purposes.
- * @option
- * @type {boolean}
- * @default false
- */
- trapFocus: false
- };
-
- // Window exports
- Foundation.plugin(OffCanvas, 'OffCanvas');
-}(jQuery);
-'use strict';
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Orbit module.
- * @module foundation.orbit
- * @requires foundation.util.keyboard
- * @requires foundation.util.motion
- * @requires foundation.util.timerAndImageLoader
- * @requires foundation.util.touch
- */
-
- var Orbit = function () {
- /**
- * Creates a new instance of an orbit carousel.
- * @class
- * @param {jQuery} element - jQuery object to make into an Orbit Carousel.
- * @param {Object} options - Overrides to the default plugin settings.
- * @param {Boolean} isLTR - flag if the slide should move left to right.
- * @param {jQuery} chosenSlide - the jQuery element of the slide to show next, if one is selected.
- * @param {Number} idx - the index of the new slide in its collection, if one chosen.
- * @fires Orbit#slidechange
- */
-
- }, {
- key: 'changeSlide',
- value: function changeSlide(isLTR, chosenSlide, idx) {
- if (!this.$slides) {
- return;
- } // Don't freak out if we're in the middle of cleanup
- var $curSlide = this.$slides.filter('.is-active').eq(0);
-
- if (/mui/g.test($curSlide[0].className)) {
- return false;
- } //if the slide is currently animating, kick out of the function
-
- var $firstSlide = this.$slides.first(),
- $lastSlide = this.$slides.last(),
- dirIn = isLTR ? 'Right' : 'Left',
- dirOut = isLTR ? 'Left' : 'Right',
- _this = this,
- $newSlide;
-
- if (!chosenSlide) {
- //most of the time, this will be auto played or clicked from the navButtons.
- $newSlide = isLTR ? //if wrapping enabled, check to see if there is a `next` or `prev` sibling, if not, select the first or last slide to fill in. if wrapping not enabled, attempt to select `next` or `prev`, if there's nothing there, the function will kick out on next step. CRAZY NESTED TERNARIES!!!!!
- this.options.infiniteWrap ? $curSlide.next('.' + this.options.slideClass).length ? $curSlide.next('.' + this.options.slideClass) : $firstSlide : $curSlide.next('.' + this.options.slideClass) : //pick next slide if moving left to right
- this.options.infiniteWrap ? $curSlide.prev('.' + this.options.slideClass).length ? $curSlide.prev('.' + this.options.slideClass) : $lastSlide : $curSlide.prev('.' + this.options.slideClass); //pick prev slide if moving right to left
- } else {
- $newSlide = chosenSlide;
- }
-
- if ($newSlide.length) {
- /**
- * Triggers before the next slide starts animating in and only if a next slide has been found.
- * Tells the JS to apply event listeners to nav buttons
- * @option
- * @type {boolean}
- * @default true
- */
- navButtons: true,
- /**
- * motion-ui animation class to apply
- * @option
- * @type {string}
- * @default 'slide-in-right'
- */
- animInFromRight: 'slide-in-right',
- /**
- * motion-ui animation class to apply
- * @option
- * @type {string}
- * @default 'slide-out-right'
- */
- animOutToRight: 'slide-out-right',
- /**
- * motion-ui animation class to apply
- * @option
- * @type {string}
- * @default 'slide-in-left'
- *
- */
- animInFromLeft: 'slide-in-left',
- /**
- * motion-ui animation class to apply
- * @option
- * @type {string}
- * @default 'slide-out-left'
- */
- animOutToLeft: 'slide-out-left',
- /**
- * Allows Orbit to automatically animate on page load.
- * @option
- * @type {boolean}
- * @default true
- */
- autoPlay: true,
- /**
- * Amount of time, in ms, between slide transitions
- * @option
- * @type {number}
- * @default 5000
- */
- timerDelay: 5000,
- /**
- * Allows Orbit to infinitely loop through the slides
- * @option
- * @type {boolean}
- * @default true
- */
- infiniteWrap: true,
- /**
- * Allows the Orbit slides to bind to swipe events for mobile, requires an additional util library
- * @option
- * @type {boolean}
- * @default true
- */
- swipe: true,
- /**
- * Allows the timing function to pause animation on hover.
- * @option
- * @type {boolean}
- * @default true
- */
- pauseOnHover: true,
- /**
- * Allows Orbit to bind keyboard events to the slider, to animate frames with arrow keys
- * @option
- * @type {boolean}
- * @default true
- */
- accessible: true,
- /**
- * Class applied to the container of Orbit
- * @option
- * @type {string}
- * @default 'orbit-container'
- */
- containerClass: 'orbit-container',
- /**
- * Class applied to individual slides.
- * @option
- * @type {string}
- * @default 'orbit-slide'
- */
- slideClass: 'orbit-slide',
- /**
- * Class applied to the bullet container. You're welcome.
- * @option
- * @type {string}
- * @default 'orbit-bullets'
- */
- boxOfBullets: 'orbit-bullets',
- /**
- * Class applied to the `next` navigation button.
- * @option
- * @type {string}
- * @default 'orbit-next'
- */
- nextClass: 'orbit-next',
- /**
- * Class applied to the `previous` navigation button.
- * @option
- * @type {string}
- * @default 'orbit-previous'
- */
- prevClass: 'orbit-previous',
- /**
- * Boolean to flag the js to use motion ui classes or not. Default to true for backwards compatability.
- * @option
- * @type {boolean}
- * @default true
- */
- useMUI: true
- };
-
- // Window exports
- Foundation.plugin(Orbit, 'Orbit');
-}(jQuery);
-'use strict';
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * ResponsiveMenu module.
- * @module foundation.responsiveMenu
- * @requires foundation.util.triggers
- * @requires foundation.util.mediaQuery
- */
-
- var ResponsiveMenu = function () {
- /**
- * Creates a new instance of a responsive menu.
- * @class
- * @fires ResponsiveMenu#init
- * @param {jQuery} element - jQuery object to make into a dropdown menu.
- * @param {Object} options - Overrides to the default plugin settings.
- * Checks the current screen width against available media queries. If the media query has changed, and the plugin needed has changed, the plugins will swap out.
- * @function
- * @private
- */
-
- }, {
- key: '_checkMediaQueries',
- value: function _checkMediaQueries() {
- var matchedMq,
- _this = this;
- // Iterate through each rule and find the last matching rule
- $.each(this.rules, function (key) {
- if (Foundation.MediaQuery.atLeast(key)) {
- matchedMq = key;
- }
- });
-
- // No match? No dice
- if (!matchedMq) return;
-
- // Plugin already initialized? We good
- if (this.currentPlugin instanceof this.rules[matchedMq].plugin) return;
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * ResponsiveToggle module.
- * @module foundation.responsiveToggle
- * @requires foundation.util.mediaQuery
- */
-
- var ResponsiveToggle = function () {
- /**
- * Creates a new instance of Tab Bar.
- * @class
- * @fires ResponsiveToggle#init
- * @param {jQuery} element - jQuery object to attach tab bar functionality to.
- * @param {Object} options - Overrides to the default plugin settings.
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Reveal module.
- * @module foundation.reveal
- * @requires foundation.util.keyboard
- * @requires foundation.util.box
- * @requires foundation.util.triggers
- * @requires foundation.util.mediaQuery
- * @requires foundation.util.motion if using animations
- */
-
- var Reveal = function () {
- /**
- * Creates a new instance of Reveal.
- * @class
- * @param {jQuery} element - jQuery object to use for the modal.
- this.$element.appendTo($(this.options.appendTo)); // move $element outside of $overlay to prevent error unregisterPlugin()
- this.$overlay.hide().off().remove();
- }
- this.$element.hide().off();
- this.$anchor.off('.zf');
- $(window).off('.zf.reveal:' + this.id);
-
- Foundation.unregisterPlugin(this);
- }
- }]);
-
- return Reveal;
- }();
-
- Reveal.defaults = {
- /**
- * Motion-UI class to use for animated elements. If none used, defaults to simple show/hide.
- * @option
- * @type {string}
- * @default ''
- */
- animationIn: '',
- /**
- * Motion-UI class to use for animated elements. If none used, defaults to simple show/hide.
- * @option
- * @type {string}
- * @default ''
- */
- animationOut: '',
- /**
- * Time, in ms, to delay the opening of a modal after a click if no animation used.
- * @option
- * @type {number}
- * @default 0
- */
- showDelay: 0,
- /**
- * Time, in ms, to delay the closing of a modal after a click if no animation used.
- * @option
- * @type {number}
- * @default 0
- */
- hideDelay: 0,
- /**
- * Allows a click on the body/overlay to close the modal.
- * @option
- * @type {boolean}
- * @default true
- */
- closeOnClick: true,
- /**
- * Allows the modal to close if the user presses the `ESCAPE` key.
- * @option
- * @type {boolean}
- * @default true
- */
- closeOnEsc: true,
- /**
- * If true, allows multiple modals to be displayed at once.
- * @option
- * @type {boolean}
- * @default false
- */
- multipleOpened: false,
- /**
- * Distance, in pixels, the modal should push down from the top of the screen.
- * @option
- * @type {number|string}
- * @default auto
- */
- vOffset: 'auto',
- /**
- * Distance, in pixels, the modal should push in from the side of the screen.
- * @option
- * @type {number|string}
- * @default auto
- */
- hOffset: 'auto',
- /**
- * Allows the modal to be fullscreen, completely blocking out the rest of the view. JS checks for this as well.
- * @option
- * @type {boolean}
- * @default false
- */
- fullScreen: false,
- /**
- * Percentage of screen height the modal should push up from the bottom of the view.
- * @option
- * @type {number}
- * @default 10
- */
- btmOffsetPct: 10,
- /**
- * Allows the modal to generate an overlay div, which will cover the view when modal opens.
- * @option
- * @type {boolean}
- * @default true
- */
- overlay: true,
- /**
- * Allows the modal to remove and reinject markup on close. Should be true if using video elements w/o using provider's api, otherwise, videos will continue to play in the background.
- * @option
- * @type {boolean}
- * @default false
- */
- resetOnClose: false,
- /**
- * Allows the modal to alter the url on open/close, and allows the use of the `back` button to close modals. ALSO, allows a modal to auto-maniacally open on page load IF the hash === the modal's user-set id.
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Slider module.
- * @module foundation.slider
- * @requires foundation.util.motion
- * @requires foundation.util.triggers
- * @requires foundation.util.keyboard
- * @requires foundation.util.touch
- */
-
- var Slider = function () {
- /**
- * Creates a new instance of a slider control.
- * @class
- * @param {jQuery} element - jQuery object to make into a slider control.
- * @param {Object} options - Overrides to the default plugin settings.
- //if left handle, the math is slightly different than if it's the right handle, and the left/top property needs to be changed for the fill bar
- if (isLeftHndl) {
- //left or top percentage value to apply to the fill bar.
- css[lOrT] = movement + '%';
- //calculate the new min-height/width for the fill bar.
- dim = parseFloat(this.$handle2[0].style[lOrT]) - movement + handlePct;
- //this callback is necessary to prevent errors and allow the proper placement and initialization of a 2-handled slider
- //plus, it means we don't care if 'dim' isNaN on init, it won't be in the future.
- if (cb && typeof cb === 'function') {
- cb();
- } //this is only needed for the initialization of 2 handled sliders
- } else {
- //just caching the value of the left/bottom handle's left/top property
- var handlePos = parseFloat(this.$handle[0].style[lOrT]);
- //calculate the new min-height/width for the fill bar. Use isNaN to prevent false positives for numbers <= 0
- //based on the percentage of movement of the handle being manipulated, less the opposing handle's left/top position, plus the percentage w/h of the handle itself
- dim = movement - (isNaN(handlePos) ? (this.options.initialStart - this.options.start) / ((this.options.end - this.options.start) / 100) : handlePos) + handlePct;
- }
- // assign the min-height/width to our css object
- css['min-' + hOrW] = dim + '%';
- }
-
- this.$element.one('finished.zf.animate', function () {
- // only set handle pos when event was handled specially
- e.preventDefault();
- _this._setHandlePos(_$handle, newValue, true);
- }
- });
- /*if (newValue) { // if pressed key has special function, update value
- e.preventDefault();
- _this._setHandlePos(_$handle, newValue);
- }*/
- });
- }
-
- /**
- * Destroys the slider plugin.
- */
-
- }, {
- key: 'destroy',
- value: function destroy() {
- this.handles.off('.zf.slider');
- this.inputs.off('.zf.slider');
- this.$element.off('.zf.slider');
-
- clearTimeout(this.timeout);
-
- Foundation.unregisterPlugin(this);
- }
- }]);
-
- return Slider;
- }();
-
- Slider.defaults = {
- /**
- * Minimum value for the slider scale.
- * @option
- * @type {number}
- * @default 0
- */
- start: 0,
- /**
- * Maximum value for the slider scale.
- * @option
- * @type {number}
- * @default 100
- */
- end: 100,
- /**
- * Minimum value change per change event.
- * @option
- * @type {number}
- * @default 1
- */
- step: 1,
- /**
- * Value at which the handle/input *(left handle/first input)* should be set to on initialization.
- * @option
- * @type {number}
- * @default 0
- */
- initialStart: 0,
- /**
- * Value at which the right handle/second input should be set to on initialization.
- * @option
- * @type {number}
- * @default 100
- */
- initialEnd: 100,
- /**
- * Allows the input to be located outside the container and visible. Set to by the JS
- * @option
- * @type {boolean}
- * @default false
- */
- binding: false,
- /**
- * Allows the user to click/tap on the slider bar to select a value.
- * @option
- * @type {boolean}
- * @default true
- */
- clickSelect: true,
- /**
- * Set to true and use the `vertical` class to change alignment to vertical.
- * @option
- * @type {boolean}
- * @default false
- */
- vertical: false,
- /**
- * Allows the user to drag the slider handle(s) to select a value.
- * @option
- * @type {boolean}
- * @default true
- */
- draggable: true,
- /**
- * Disables the slider and prevents event listeners from being applied. Double checked by JS with `disabledClass`.
- * @option
- * @type {boolean}
- * @default false
- */
- disabled: false,
- /**
- * Allows the use of two handles. Double checked by the JS. Changes some logic handling.
- * @option
- * @type {boolean}
- * @default false
- */
- doubleSided: false,
- /**
- * Potential future feature.
- */
- // steps: 100,
- /**
- * Number of decimal places the plugin should go to for floating point precision.
- * @option
- * @type {number}
- * @default 2
- */
- decimal: 2,
- /**
- * Time delay for dragged elements.
- */
- // dragDelay: 0,
- /**
- * Time, in ms, to animate the movement of a slider handle if user clicks/taps on the bar. Needs to be manually set if updating the transition time in the Sass settings.
- * @option
- * @type {number}
- * @default 200
- */
- moveTime: 200, //update this if changing the transition time in the sass
- /**
- * Class applied to disabled sliders.
- * @option
- * @type {string}
- * @default 'disabled'
- */
- disabledClass: 'disabled',
- /**
- * Will invert the default layout for a vertical<span data-tooltip title="who would do this???"> </span>slider.
- * @option
- * @type {boolean}
- * @default false
- */
- invertVertical: false,
- /**
- * Milliseconds before the `changed.zf-slider` event is triggered after value change.
- * @option
- * @type {number}
- * @default 500
- */
- changedDelay: 500,
- /**
- * Basevalue for non-linear sliders
- * @option
- * @type {number}
- * @default 5
- */
- nonLinearBase: 5,
- /**
- * Basevalue for non-linear sliders, possible values are: `'linear'`, `'pow'` & `'log'`. Pow and Log use the nonLinearBase setting.
- * @option
- * @type {string}
- * @default 'linear'
- */
- positionValueFunction: 'linear'
- };
-
- function percent(frac, num) {
- return frac / num;
- }
- function absPosition($handle, dir, clickPos, param) {
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Sticky module.
- * @module foundation.sticky
- * @requires foundation.util.triggers
- * @requires foundation.util.mediaQuery
- */
-
- var Sticky = function () {
- /**
- * Creates a new instance of a sticky thing.
- * @class
- * @param {jQuery} element - jQuery object to make sticky.
- * @param {Object} options - options object passed when creating the element programmatically.
- * Location in the view the element sticks to. Can be `'top'` or `'bottom'`.
- * @option
- * @type {string}
- * @default 'top'
- */
- stickTo: 'top',
- /**
- * If anchored to a single element, the id of that element.
- * @option
- * @type {string}
- * @default ''
- */
- anchor: '',
- /**
- * If using more than one element as anchor points, the id of the top anchor.
- * @option
- * @type {string}
- * @default ''
- */
- topAnchor: '',
- /**
- * If using more than one element as anchor points, the id of the bottom anchor.
- * @option
- * @type {string}
- * @default ''
- */
- btmAnchor: '',
- /**
- * Margin, in `em`'s to apply to the top of the element when it becomes sticky.
- * @option
- * @type {number}
- * @default 1
- */
- marginTop: 1,
- /**
- * Margin, in `em`'s to apply to the bottom of the element when it becomes sticky.
- * @option
- * @type {number}
- * @default 1
- */
- marginBottom: 1,
- /**
- * Breakpoint string that is the minimum screen size an element should become sticky.
- * @option
- * @type {string}
- * @default 'medium'
- */
- stickyOn: 'medium',
- /**
- * Class applied to sticky element, and removed on destruction. Foundation defaults to `sticky`.
- * @option
- * @type {string}
- * @default 'sticky'
- */
- stickyClass: 'sticky',
- /**
- * Class applied to sticky container. Foundation defaults to `sticky-container`.
- * @option
- * @type {string}
- * @default 'sticky-container'
- */
- containerClass: 'sticky-container',
- /**
- * Number of scroll events between the plugin's recalculating sticky points. Setting it to `0` will cause it to recalc every scroll event, setting it to `-1` will prevent recalc on scroll.
- * @option
- * @type {number}
- * @default -1
- */
- checkEvery: -1
- };
-
- /**
- * Helper function to calculate em values
- * @param Number {em} - number of em's to calculate into pixels
-var _typeof = typeof Symbol === "function" && typeof Symbol.iterator === "symbol" ? function (obj) { return typeof obj; } : function (obj) { return obj && typeof Symbol === "function" && obj.constructor === Symbol && obj !== Symbol.prototype ? "symbol" : typeof obj; };
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Tabs module.
- * @module foundation.tabs
- * @requires foundation.util.keyboard
- * @requires foundation.util.timerAndImageLoader if tabs contain images
- */
-
- var Tabs = function () {
- /**
- * Creates a new instance of tabs.
- * @class
- * @fires Tabs#init
- * @param {jQuery} element - jQuery object to make into tabs.
- * @param {Object} options - Overrides to the default plugin settings.
- * Allows the window to scroll to content of pane specified by hash anchor
- * @option
- * @type {boolean}
- * @default false
- */
- deepLink: false,
-
- /**
- * Adjust the deep link scroll to make sure the top of the tab panel is visible
- * @option
- * @type {boolean}
- * @default false
- */
- deepLinkSmudge: false,
-
- /**
- * Animation time (ms) for the deep link adjustment
- * @option
- * @type {number}
- * @default 300
- */
- deepLinkSmudgeDelay: 300,
-
- /**
- * Update the browser history with the open tab
- * @option
- * @type {boolean}
- * @default false
- */
- updateHistory: false,
-
- /**
- * Allows the window to scroll to content of active pane on load if set to true.
- * Not recommended if more than one tab panel per page.
- * @option
- * @type {boolean}
- * @default false
- */
- autoFocus: false,
-
- /**
- * Allows keyboard input to 'wrap' around the tab links.
- * @option
- * @type {boolean}
- * @default true
- */
- wrapOnKeys: true,
-
- /**
- * Allows the tab content panes to match heights if set to true.
- * @option
- * @type {boolean}
- * @default false
- */
- matchHeight: false,
-
- /**
- * Allows active tabs to collapse when clicked.
- * @option
- * @type {boolean}
- * @default false
- */
- activeCollapse: false,
-
- /**
- * Class applied to `li`'s in tab link list.
- * @option
- * @type {string}
- * @default 'tabs-title'
- */
- linkClass: 'tabs-title',
-
- /**
- * Class applied to the active `li` in tab link list.
- * @option
- * @type {string}
- * @default 'is-active'
- */
- linkActiveClass: 'is-active',
-
- /**
- * Class applied to the content containers.
- * @option
- * @type {string}
- * @default 'tabs-panel'
- */
- panelClass: 'tabs-panel',
-
- /**
- * Class applied to the active content container.
- * @option
- * @type {string}
- * @default 'is-active'
- */
- panelActiveClass: 'is-active'
- };
-
- // Window exports
- Foundation.plugin(Tabs, 'Tabs');
-}(jQuery);
-'use strict';
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Toggler module.
- * @module foundation.toggler
- * @requires foundation.util.motion
- * @requires foundation.util.triggers
- */
-
- var Toggler = function () {
- /**
- * Creates a new instance of Toggler.
- * @class
- * @fires Toggler#init
- * @param {Object} element - jQuery object to add the trigger to.
- * @param {Object} options - Overrides to the default plugin settings.
- this.$element.attr('aria-expanded', isOn ? true : false);
- }
-
- /**
- * Destroys the instance of Toggler on the element.
- * @function
- */
-
- }, {
- key: 'destroy',
- value: function destroy() {
- this.$element.off('.zf.toggler');
- Foundation.unregisterPlugin(this);
- }
- }]);
-
- return Toggler;
- }();
-
- Toggler.defaults = {
- /**
- * Tells the plugin if the element should animated when toggled.
- * @option
- * @type {boolean}
- * @default false
- */
- animate: false
- };
-
- // Window exports
- Foundation.plugin(Toggler, 'Toggler');
-}(jQuery);
-'use strict';
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * Tooltip module.
- * @module foundation.tooltip
- * @requires foundation.util.box
- * @requires foundation.util.mediaQuery
- * @requires foundation.util.triggers
- */
-
- var Tooltip = function () {
- /**
- * Creates a new instance of a Tooltip.
- * @class
- * @fires Tooltip#init
- * @param {jQuery} element - jQuery object to attach a tooltip to.
- * @param {Object} options - object to extend the default configuration.
- * sets the position class of an element and recursively calls itself until there are no more possible positions to attempt, or the tooltip element is no longer colliding.
- * if the tooltip is larger than the screen width, default to full width - any user selected margin
- * @private
- */
-
- }, {
- key: '_setPosition',
- value: function _setPosition() {
- var position = this._getPositionClass(this.template),
- * adds event listeners for the tooltip and its anchor
- * TODO combine some of the listeners like focus and mouseenter, etc.
- * @private
- */
-
- }, {
- key: '_events',
- value: function _events() {
- var _this = this;
- var $template = this.template;
- var isFocus = false;
-
- if (!this.options.disableHover) {
-
- this.$element.on('mouseenter.zf.tooltip', function (e) {
- if (!_this.isActive) {
- _this.timeout = setTimeout(function () {
- _this.show();
- }, _this.options.hoverDelay);
- }
- }).on('mouseleave.zf.tooltip', function (e) {
- clearTimeout(_this.timeout);
- if (!isFocus || _this.isClick && !_this.options.clickOpen) {
- _this.hide();
- }
- });
- }
-
- if (this.options.clickOpen) {
- this.$element.on('mousedown.zf.tooltip', function (e) {
- e.stopImmediatePropagation();
- if (_this.isClick) {
- //_this.hide();
- // _this.isClick = false;
- } else {
- _this.isClick = true;
- if ((_this.options.disableHover || !_this.$element.attr('tabindex')) && !_this.isActive) {
- _this.show();
- }
- }
- });
- } else {
- this.$element.on('mousedown.zf.tooltip', function (e) {
- e.stopImmediatePropagation();
- _this.isClick = true;
- });
- }
-
- if (!this.options.disableForTouch) {
- this.$element.on('tap.zf.tooltip touchend.zf.tooltip', function (e) {
- _this.isActive ? _this.hide() : _this.show();
- });
- }
-
- this.$element.on({
- // 'toggle.zf.trigger': this.toggle.bind(this),
- // 'close.zf.trigger': this.hide.bind(this)
- 'close.zf.trigger': this.hide.bind(this)
- });
-
- this.$element.on('focus.zf.tooltip', function (e) {
- isFocus = true;
- if (_this.isClick) {
- // If we're not showing open on clicks, we need to pretend a click-launched focus isn't
- // a real focus, otherwise on hover and come back we get bad behavior
- if (!_this.options.clickOpen) {
- isFocus = false;
- }
- return false;
- } else {
- _this.show();
- }
- }).on('focusout.zf.tooltip', function (e) {
- isFocus = false;
- _this.isClick = false;
- _this.hide();
- }).on('resizeme.zf.trigger', function () {
- if (_this.isActive) {
- _this._setPosition();
- }
- });
- }
-
- /**
- * adds a toggle method, in addition to the static show() & hide() functions
- * @function
- */
-
- }, {
- key: 'toggle',
- value: function toggle() {
- if (this.isActive) {
- this.hide();
- } else {
- this.show();
- }
- }
-
- /**
- * Destroys an instance of tooltip, removes template element from the view.
- * @function
- */
-
- }, {
- key: 'destroy',
- value: function destroy() {
- this.$element.attr('title', this.template.text()).off('.zf.trigger .zf.tooltip').removeClass('has-tip top right left').removeAttr('aria-describedby aria-haspopup data-disable-hover data-resize data-toggle data-tooltip data-yeti-box');
-
- this.template.remove();
-
- Foundation.unregisterPlugin(this);
- }
- }]);
-
- return Tooltip;
- }();
-
- Tooltip.defaults = {
- disableForTouch: false,
- /**
- * Time, in ms, before a tooltip should open on hover.
- * @option
- * @type {number}
- * @default 200
- */
- hoverDelay: 200,
- /**
- * Time, in ms, a tooltip should take to fade into view.
- * @option
- * @type {number}
- * @default 150
- */
- fadeInDuration: 150,
- /**
- * Time, in ms, a tooltip should take to fade out of view.
- * @option
- * @type {number}
- * @default 150
- */
- fadeOutDuration: 150,
- /**
- * Disables hover events from opening the tooltip if set to true
- * @option
- * @type {boolean}
- * @default false
- */
- disableHover: false,
- /**
- * Optional addtional classes to apply to the tooltip template on init.
- * @option
- * @type {string}
- * @default ''
- */
- templateClasses: '',
- /**
- * Non-optional class added to tooltip templates. Foundation default is 'tooltip'.
- * @option
- * @type {string}
- * @default 'tooltip'
- */
- tooltipClass: 'tooltip',
- /**
- * Class applied to the tooltip anchor element.
- * @option
- * @type {string}
- * @default 'has-tip'
- */
- triggerClass: 'has-tip',
- /**
- * Minimum breakpoint size at which to open the tooltip.
- * @option
- * @type {string}
- * @default 'small'
- */
- showOn: 'small',
- /**
- * Custom template to be used to generate markup for tooltip.
- * @option
- * @type {string}
- * @default ''
- */
- template: '',
- /**
- * Text displayed in the tooltip template on open.
- * @option
- * @type {string}
- * @default ''
- */
- tipText: '',
- touchCloseText: 'Tap to close.',
- /**
- * Allows the tooltip to remain open if triggered with a click or touch event.
- * @option
- * @type {boolean}
- * @default true
- */
- clickOpen: true,
- /**
- * Additional positioning classes, set by the JS
- * @option
- * @type {string}
- * @default ''
- */
- positionClass: '',
- /**
- * Distance, in pixels, the template should push away from the anchor on the Y axis.
- * @option
- * @type {number}
- * @default 10
- */
- vOffset: 10,
- /**
- * Distance, in pixels, the template should push away from the anchor on the X axis, if aligned to a side.
- * @option
- * @type {number}
- * @default 12
- */
- hOffset: 12,
- /**
- * Allow HTML in tooltip. Warning: If you are loading user-generated content into tooltips,
- * allowing HTML may open yourself up to XSS attacks.
- * @option
- * @type {boolean}
- * @default false
- */
- allowHtml: false
- };
-
- /**
- * TODO utilize resize event trigger
- */
-
- // Window exports
- Foundation.plugin(Tooltip, 'Tooltip');
-}(jQuery);
-'use strict';
-
-var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();
-
-function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }
-
-!function ($) {
-
- /**
- * ResponsiveAccordionTabs module.
- * @module foundation.responsiveAccordionTabs
- * @requires foundation.util.keyboard
- * @requires foundation.util.timerAndImageLoader
- * @requires foundation.util.motion
- * @requires foundation.accordion
- * @requires foundation.tabs
- */
-
- var ResponsiveAccordionTabs = function () {
- /**
- * Creates a new instance of a responsive accordion tabs.
- * @class
- * @fires ResponsiveAccordionTabs#init
- * @param {jQuery} element - jQuery object to make into a dropdown menu.
- * @param {Object} options - Overrides to the default plugin settings.
- */
- function ResponsiveAccordionTabs(element, options) {
- var tmpPlugin = new obj.plugin(dummyPlugin, _this.options);
- for (var keyKey in tmpPlugin.options) {
- if (tmpPlugin.options.hasOwnProperty(keyKey) && keyKey !== 'zfPlugin') {
- var objObj = tmpPlugin.options[keyKey];
- _this.allOptions[keyKey] = objObj;
- }
- }
- tmpPlugin.destroy();
- } catch (e) {}
- }
- }
- }
-
- /**
- * Initializes events for the Menu.
- * @function
- * @private
- */
-
- }, {
- key: '_events',
- value: function _events() {
- var _this = this;
-
- $(window).on('changed.zf.mediaquery', function () {
- _this._checkMediaQueries();
- });
- }
-
- /**
- * Checks the current screen width against available media queries. If the media query has changed, and the plugin needed has changed, the plugins will swap out.
- * @function
- * @private
- */
-
- }, {
- key: '_checkMediaQueries',
- value: function _checkMediaQueries() {
- var matchedMq,
- _this = this;
- // Iterate through each rule and find the last matching rule
- $.each(this.rules, function (key) {
- if (Foundation.MediaQuery.atLeast(key)) {
- matchedMq = key;
- }
- });
-
- // No match? No dice
- if (!matchedMq) return;
-
- // Plugin already initialized? We good
- if (this.currentPlugin instanceof this.rules[matchedMq].plugin) return;