./gradlew distZip

• Change group from com.github.melix to me.champeau.deck2pdf

• Add ability to export to PNG or JPEG

• Require Java 8

deck2pdf --profile=deckjs <inputfile> <outputfile>

deck2pdf slides.html slides.pdf

deck2pdf --profile=revealjs slides.html slides.pdf

deck2pdf --width=1024 --height=768 slides.html slides.pdf

deck2pdf slides.html slides.png

deck2pdf slides.html slides-%03d.png

deck2pdf --quality=75 slides.html slides.jpg

The easiest way to define a new profile is to create a properties file. For example, here is the file that the deck.js export uses:

The properties files consists of two entries:

• totalSlides is a Javascript snippet which will compute the total number of slides of the deck

• nextSlide is the Javascript code which needs to be called to jump to the next slide

Properties files are very simple, so are only capable of handling decks for which the number of slides is known in advance and the command to jump from one slide to another is always the same. For more complex slide shows, you can use the Groovy profiles.

6.2.1. Example

link:src/main/resources/impressjs.groovy[]

6.2.2. Groovy API

js 'var slideCount = slides.length;'

setup = {
    // disable controls for better rendering
    js 'Reveal.configure({controls: false, progress: false});'
}

isLastSlide = {
    js '''
        var totalSlides = Dz.slides.length;
        var cSlide = Dz.idx;
        cSlide==totalSlides && Dz.step==Dz.slides[cSlide - 1].$$('.incremental > *').length
    '''
}

totalSlides = {
    js (/$$(".step", byId('impress')).length/)
}

nextSlide = {
    js('api.next()')
}

int curSlide = 0
nextSlide = {
    curSlide++
    switch (curSlide) {
        case 1:
            js 'api.next()'
            break;
        case 2:
            js 'api.goto(2)'
            break;
        default:
            js "api.goto($curSlide)"
    }
}

pause = 2000

setup {
    if (Boolean.valueOf(options.verbose)) {
        // --verbose=true on command line
        println "Hello, I'm in verbose mode!"
    }
    String mode = options.mode?:'auto'
    switch (mode) {
        case 'auto':
            ...
            break;
        case 'skip':
            ...
            break;
    }

}

Once you’ve written a new profile, you can use it with the --profile switch:

Of course, you can submit a pull request so that we include your profile into the distribution!

In order to use custom fonts in your presentation, as defined using the CSS3 +@font-face@, you need to use at least JavaFX 3.0 (available in JDK 8). Otherwise, the embedded browser will fall back to using the default system font.

Here’s an example custom font sourced from Google Fonts:

This link element imports the following CSS:

You can now use these two combinations of font-family, font-style and font-weight in your presentation. Unlike a normal browser (e.g., Chrome, Firefox, etc), you cannot use a font combination that is not represented here (or on your system). If you attempt to use a combination not represented here (such as a combination that include font-style: italic;), the embedded browser will fall back to using the default font.

Aside from that exception, custom fonts should just work when using JavaFX 3.0.

If you you’re using JavaFX 2.2 (available in JDK 7), you can still use custom fonts, but you must load them explicitly before the embedded browser loads the presentation.

First, download the TTF file for each font you want to use and copy it to a directory of your choice. The files should be named using the hyphenated form shown in the CSS above. For example:

• YanoneKaffeesatz-Regular.ttf

• YanoneKaffeesatz-Bold.ttf

Now you can use the fontsdir command line option to tell deck2pdf where to load the fonts from: