Triton 8 User's Manual
Layout
Layout » Navigation
- Theme image splash page: If selected, the album begins with a splash page consisting of the theme image, album title, album description, and a "play" icon to begin the slideshow. Choosing this option also allows you to choose to autoplay videos, audio clips, and background music, which would otherwise be blocked by the browser.
- Icon size: The size of the navigation icons.
- Home icon: You may choose which icon is used for links in the album that point to the homepage you have entered under Album » Settings » Pages » Link to external homepage » Address (URL).
- Open link in: If you have entered a link to an external home page, this determines whether the link will open in the same browser tab or iframe, a new browser tab, the parent of the iframe, or the topmost frame on the page.
Layout » Options
- Timed slideshow: If selected, a timed slideshow is available to the site visitor. You may set the number of seconds spent displaying each image.
- Autostart slideshow: If selected, the timed slideshow will start automatically. Otherwise, it will start in a paused state.
- Autoplay videos: If selected, videos will start playing when they are opened.
- Use audio clips: If selected, audio clips that have been attached to album objects will be shown in the slide captions.
- Autoplay audio clips: If selected, each audio clip will begin playing as soon as the slide is shown.
- Fullscreen option: If selected, a fullscreen toggle icon is displayed in the caption.
- Restart icon: If selected, a restart icon is displayed in the caption. This simply reloads the page, which has the effect of taking the visitor back to the beginning of the album.
- Zoom: If selected, the site visitor may zoom in on slide images when they are shown smaller than their native size.
Layout » Appearance
- Transition time: The duration of the transition between images, in milliseconds.
- Transition type: The type of transition between images - try a test album to see the differences. On a mobile device, regardless of this setting, the transition is a "slide," which is what users expect to see on such devices.
- Padding width: For the slide image, you may select the width of the padding around the image. See note below about the Dark and Light styles.
- Shadow opacity: If the slide image padding width is greater than zero, you may choose to include a box shadow on the slide image. Opacity of zero means no shadow, with higher values representing a denser shadow. See note below about the Dark and Light styles.
- Minimum box width: For the slide image, you may select the minimum width of the expander. Choosing a larger value can be helpful if you have long captions on portrait-mode images.
- Lightbox border: A thin border can be applied to the entire lightbox. In most cases this is unnecessary, but a thin border around the lightbox can separate it from the page background.
Layout » Caption
- Caption content: The caption may display the image title, the image comment, both, or neither.
- Name if no title: If no image title has been entered, use the image file name (without its extension).
- Caption position: The position of the caption relative to the image.
- Maximum width: The maximum width of the slide caption.
- Display underscores as spaces: If selected, underscores in file names that appear as browser tabs or captions are displayed as spaces. This applies only to the actual file names. User-entered titles and comments are not affected. The file names themselves are not changed.
Layout » Tooltips
- Site home: If a URL and text are entered under Album » Settings » Pages » Link to external homepage, this is the icon that will appear on each slide. The tooltip that appears when a visitor hovers on this icon is entered on that settings page, rather than here. This is intended for a home page that is external to the album.
- Fullscreen: The tooltip that appears when a visitor hovers on the "fullscreen" icon.
- Restart: The tooltip that appears when a visitor hovers on the "restart" icon.
- Music: The tooltip that appears when a visitor hovers on the "music" icon.
Dark & Light Styles
If you choose the Dark or Light style, the padding around the slide image would be the same color as the page background. This would then give the appearance of icons seeming to be positioned badly, and of the slide caption seeming to be too far below (or above) the slide image. Therefore, if either of these two styles is chosen, the padding setting and shadow opacity are ignored, unless you also elect to use a lightbox border. There will be no padding or shadow on the image.
Music
Music » Background Music
- Loop: If selected, the music playlist will loop continuously.
- Playlist: Use the + icon to add music files (MP3 only) and the x icon to remove files. Use the up- and down-arrow icons to rearrange the files. Music files may be previewed with the audio controls (fast rewind, play, stop, fast forward).
- Autoplay background music: If selected, the background music will begin when the visitor begins viewing the images.
Fonts
Fonts » Font Family
- Font family: The font family for the album. The font families are confined to those that are very "web-safe," and will provide acceptable results on most site visitors' computers. However, the only way to be absolutely sure that the album text will be rendered the same way for every visitor is to use Google fonts or WOFF files.
Fonts » Google Font
Fonts » WOFF File
Fonts » Font Styles
- Album title: The font styles for the album title shown on the theme image splash page. The font size may be set to zero, meaning that the title is not displayed. This option might be chosen if the theme image contains its own text or a large logo.
- Album description: The font styles for the album description shown on the theme image splash page. The font size may be set to zero.
- Title: The font styles for the image title on slides.
- Comment: The font styles for the image comment on slides.
Code
Code
- CSS that will be inserted at the end of the common.css file: CSS code entered here will be inserted at the end of the output common.css file when the album is created. jAlbum variables will be replaced with their actual values. This can be used to override the album's own CSS attributes.
Misc
Misc
- Meta "description" tag: The entered text will be inserted into every page as a meta description tag. This is used by most search engines to describe a site when it is listed in search results. Therefore, the text should be a simple description of the site contents. If no text is entered, the skin assembles a description for each page from the folder title and comment or the image title and comment.
- Meta "robots" tag: The chosen tag will be inserted into every page. A meta robots tag may be used to tell search engine robots whether to index this page and whether to follow links on this page.
- Favicon location: Provide the absolute address of the favicon file for the website. Normally, the favicon file would be stored at the root of your domain, for example, http://example.com/favicon.ico. The file should never be added to the jAlbum project itself, and should be uploaded to your web host independently of the album. Note that if you host your album at jalbum.net, a favicon with the default name, i.e., https://yourname.jalbum.net/favicon.ico, will be overridden by the default jAlbum favicon (Dor). To use your own favicon with jalbum.net hosting, it must be given a different name, like mydog.ico. Favicon files may be ICO, PNG, or GIF files, must be square, and must have dimensions of 16x16, 32x32, 48x48, or 64x64.
- Google Analytics code: Copy and paste the entire code snippet provided to you by Google Analytics. It will be inserted at the appropriate location in every page.
- HTML language: Select the language code that corresponds to the predominant language used in your album. This will be used in the <html> tag on every page of the album. It's helpful for search engines, for browser translations, and in some cases for choosing correct typography. It defaults to the language you have chosen for jAlbum. If the language code you want to use is not in the list, you may enter any of the standard codes manually.
Custom
Custom » Create a custom style
- Create a custom style based on an existing style: The user can select one of the preset Triton styles as the starting point for creating a custom style. This resets the color settings to those of the preset style selected.
Custom » Colors
- Body: The color of the body of the page.
- Theme text: The color to use for the album title and description shown on the theme image splash page. Because this text is shown on the theme image, rather than on the body of the page, it is often best to choose a contrasting color (typically white, for visibility against a dimmed image).
- Theme text link hover: The color of link text in the title and description, when hovered on.
- Theme text background tint: The color of the dimming layer that appears behind the title and description.
- Slide background: The color of the slide image background, including the caption area.
- Text: The color of text on the pages.
- Text link hover: The color of link text on the pages, when hovered on.
- Lightbox border: The color of the border around the lightbox image and caption area.
- Background image - Add / Remove: Click Add to select a background image to be shown behind the images. This should be a small texture pattern - it is repeated over the page.
Click Remove to remove the image.
About
About
- Triton: The version number currently installed.
- Triton Release Notes: A link to the release notes.
- Triton User's Manual: A link to this user's manual.
- Triton Home Page: A link to the Triton demonstration page.
- Triton Support Forum: A link to the jAlbum forum section for Triton support.
- Triton License: A link to the Triton licensing terms.
- jAlbum Skin Page: A link to the jAlbum website page for this skin.
Info: HTML Tags and jAlbum Variables
HTML tags and jAlbum variables may be used in a number of different contexts, and will be honored in the album. jAlbum variables will be passed to the jAlbum engine and will be evaluated before they are placed in the completed album. Almost all user entries are treated in this manner:
- Image title and comment
- Tooltips
- Custom CSS
- Meta description
If you use a < or > character in a text string, it is assumed to be part of an HTML tag, and may produce errors if it isn't. If you want to use one of those characters as simple text, use its HTML entity code, instead.
- for <, use <
- for >, use >
Info: Google Fonts & WOFF Files
A longstanding problem with web pages is that fonts are not actually included in the page code. The page simply includes some text, along with an instruction in the CSS that tells the browser what font to use to display that text. But if the visitor's computer doesn't have that font installed, it falls back to a default, or works its way down whatever font stack is indicated in the CSS until it finds a font that it can use. The effect of this limitation is that web page designers are generally forced to rely on a small set of "web safe" fonts, fonts that can reliably be found on most visitors' computers.
Packaging fonts with web pages in a way that allows the site visitor to install the font on his computer, while possible, runs afoul of copyright protections. Most fonts, even those normally distributed with a new computer, are protected by copyright, and you don't have the right to make them available to others.
To address this problem, Google Fonts and Web Open Font Format (WOFF) files can be used. The font is not actually installed on the visitor's computer. It is used only for displaying text on your web page.
In Triton, you may add two Google Fonts and a WOFF file, and tell the skin which font to use for each text element, with the default being the selected regular font family. Decorative fonts can be difficult to read at smaller sizes, and are therefore best used only for page titles. You are likely to find that they look better when displayed with a larger font size than you would use for a regular font, and with normal weight, rather than bold. More traditional fonts may be suitable for all text.
To choose a Google Font, visit the Google Fonts page, and identify the font you want to use. Scroll down on the page to view suggested font pairings. You might want to use a more elaborate font for titles, and a simpler font for captions. Make a note of its name, and enter the name in the Triton settings. Triton does not support the use of Google Font multiple styles. If you see a font listed, and it indicates that there are multiple styles of that font available, when you enter its name in the Triton settings, the skin will use the basic style of that font.
There are now many hundreds of free WOFF files available. Search the web for free woff to find sources (some sites require registration). In most cases, the fonts are free for you to use on your website, even if the website is commercial, but the font designers retain copyright, so you don't have permission to redistribute the files directly to others. Often, these free fonts are provided in a variety of formats - WOFF, OTF, TTF, EOT, SVG, and so on. The format needed for Triton is indicated by a .woff file extension. In many cases, the download will be provided as a zip archive containing several formats - you need to extract the .woff file from that archive and use that one for inclusion in the skin.
The FontSquirrel site is a typical example, offering many free fonts. Find one you like, and then click on the name of the font (not on the Download link). Then look for a Webfont Kit link on the menu bar. There, you can choose the WOFF format. If a font is available in only one format, the Webfont Kit menu bar choice will be absent. In that case, you can download another format, like TTF, then use FontSquirrel's Webfont Generator to upload the TTF and convert it to WOFF - choose the Expert radio button after you've uploaded the TTF version. In short, it may take some exploration to find the WOFF file you need.
See Fonts to include a Google Font and/or WOFF file in your album.
Info: Linking to Originals
If you choose Link to originals in the main jAlbum settings (Album » Settings » Pages), your images will not be scaled or modified in any way. They will be used directly in the slide pages of the album. The skin will adjust the slide display to the visitor's viewport, but because the files have not been scaled, the file sizes may be very large, making this setting a poor choice for a web album. However, you can resize your images before using them in jAlbum, in which case choosing Link to originals might be suitable. If you also select HiDPI images, your original images will be shown at one-half their native dimensions, to preserve clarity on high-density displays.
Info: HiDPI Images
High-density display devices, like Apple's retina displays, have twice the number of physical pixels (or more) within a given area, compared to regular devices. Images will appear sharper on these displays if they are larger, but displayed in half the CSS layout space. For example, an image that is 1200px wide is normally displayed in 1200 CSS pixels on a regular monitor, and is using 1200 physical pixels. But for a high-density device, it is better to provide an image that is 2400px wide, but then display it in 1200 CSS pixels on the monitor. When you do this, the display makes full use of the 2400 pixels that are available in the image, by using 2400 of its physical pixels.
jAlbum includes the option, under Settings » Images » General, of creating high-density slide images, referred to as HiDPI images. This doesn't actually produce images with a higher pixel density - there is no such thing. It simply produces images with double the image bounds - the skin, however, then displays these images in half the space.
Doing this may produce a better-looking image on a high-density monitor. The penalty is that the image files are typically several times the file size. They consume more bandwidth, taking longer to upload and longer to download when someone visits the site. The user with a regular monitor is forced to download much larger files, but gets no benefit from them.
Using HiDPI images may not be desirable. The bandwidth penalty is substantial, but the perceived improvement in display quality is not as dramatic as it is with small images like thumbnails. As the bandwidth available to your site visitors continues to grow, the greater use of bandwidth will become irrelevant. In addition, the skin does a lot of image preloading, so as a visitor moves through the slides, there will often be no delay, even with HiDPI images. Improving technology will eventually make this a non-issue, and you will be able to use HiDPI images in all your albums.
It should be noted that if the images you are adding to your project aren't fairly large to begin with, perhaps 3000x2000 pixels, there is no benefit to be gained by using HiDPI images, and there is no reason to choose that option. jAlbum can't interpolate, and produce more image information than what is present in the original images.
Recent jAlbum versions include the ability to produce albums with two sets of images, but the image display script used in this skin is not constructed to make use of them. In addition, a "2X variant" image in jAlbum is not handled the same way as a HiDPI image - the benefit of the greater density is lost.
If you want to provide HiDPI images to visitors with high-density monitors, but not penalize visitors with regular monitors, the only solution is to produce two copies of the album. Create your project and call it, for example, mydogLR (for "low resolution"), using image bounds that produce good-looking slides on a regular monitor (the skin defaults, for example). Do not choose HiDPI images. Upload your album to https://mysite.com/mydogLR/.
Now duplicate the entire project - click the down-arrow to the right of the project name in the jAlbum project panel, choose Duplicate Project, and call it mydogHR (for "high resolution"). In this duplicate project, choose HiDPI images, make the album, and upload it to https://mysite.com/mydogHR/.
Now you need to provide a steering script on your site, so that visitors will be directed to the appropriate album. Create a directory on your site called https://mysite.com/mydog/ and upload an index.html to it that contains the following:
<!DOCTYPE html>
<meta charset='UTF-8'>
<title>Redirect</title>
<script>
if(screen.width >= 768 && screen.height >= 768 && window.devicePixelRatio >= 2) {
window.location = "http://mysite.com/mydogHR/";
} else {
window.location = "http://mysite.com/mydogLR/";
}
</script>
All visitors can now be provided with a single link to your album: https://mysite.com/mydog/. The steering script will automatically direct visitors to the high resolution album if they are on anything the size of an iPad or larger, and have a high-density display. These are the visitors who can benefit from the larger slide images. Other visitors will be directed to the low resolution album.
Info: Version Updating
New versions of Triton are published with some regularity. These new versions generally include new features, improvements, and bug fixes. The jAlbum application will let you know when a new version is available, and users are encouraged to download and install the new version.
- It is best to install a new version of the skin with the jAlbum application closed, i.e., not running. Save the Triton.jaskin file to your computer, close jAlbum, launch the Triton.jaskin file to do the installation, then launch jAlbum again.
- If you have a project that was created with an older version of Triton and you're happy with it, and don't intend to add any images to it or make any other changes to it, there's no reason to make the album again with the latest version of the skin. However, if you intend to change that project in any way, it should be reprocessed with the newest version.
- Before re-making an existing album with a new version of the skin, read the release notes, and create a small test album to see the effect of newly-introduced features. These new features are sometimes enabled by default in a new version, and will be applied to your existing project unless you choose to turn them off. The time to discover this is not after you've rebuilt an entire 10,000-image album.
- There is no need to invoke Force Remake in jAlbum. This forces jAlbum to reprocess all of the images, rather than just generating new HTML and CSS files. This is almost never required. Just click Make Album, and let jAlbum decide what needs to be updated.
- For an active project, one that you make changes to periodically, it is recommended that you stay abreast of new skin versions. Generally, the process of updating an album by one or two skin versions is easy, and takes very little time. Trying to jump over many versions, however, could require considerable effort. Stay current to avoid problems.
- After you have opened an existing project with the new skin version, it's a good idea to save the project, even if jAlbum doesn't prompt you to do so. This saves newly-defined skin variables with the project, which makes subsequent project opening smoother and less prone to errors.
- If a new version of the Floatbox script becomes available, you should not install it in your existing copy of Triton. The skin may not work with the new version of the script. Wait until the new Floatbox version is included in an updated version of the Triton skin.
Info: Browser Support
Triton produces albums that display properly in most browsers.
- Standards compliance: Triton produces valid HTML5 and CSS3 code. However, no attempt is made to ensure that user-provided code (in titles, comments, etc.) is valid.
- Current desktop browsers: All Triton skin features are supported in the current versions of Chrome, Edge, Firefox, and Safari.
- Other browsers: Triton is not tested in any other browsers. Support for skin features is unknown.
- Tablet browsers: Triton is only occasionally tested on any tablets (e.g., iPad), but all skin features should operate properly.
- Smartphones: Triton is tested in Chrome and Firefox on an Android phone, and is occasionally tested in Chrome and Safari on an iPhone. Most skin features should operate properly.
- Javascript: Virtually all functions of the album are dependent upon Javascript, so the site visitor must have Javascript enabled.
- jAlbum integrated browser: The integrated browser is not reliable. You should preview your album in a real browser (Chrome, Edge, Firefox, or Safari) before concluding that there's a problem with it.
Triton License
The Triton skin for jAlbum, including all supporting files, source code, compiled code, and scripts, ©2022, Jeff Tucker.
The skin uses the following open-source scripts:
You may use the software to create albums for personal or commercial sites. You may distribute copies of the software to others, but for any reuse or distribution, you must make clear to others the license terms of this software. You may modify the software for your own use.
The copyright holder reserves the right to waive any of these terms on a case-by-case basis.
The jAlbum application is free for personal use during the initial trial period, but after that, a Standard license is required. For commercial use, a Pro license is required. Visit the jAlbum site for further information.