Awesome

JFXAnimation

CSS keyframe animation for JavaFX.<br> If you are using JFoenix JFXAnimation is included (currently version 1.0.0 only)

Requirements

• JDK 8 and up

Documentation

Version 2.0.0 (Latest)

For details see: JavaDoc

Changelog

• cleanup and refactored code

• JFXAnimationTemplateConfig

  • add reverse method
  • add dynamic interpolator
  • add from/To automatic generation
  • add automatic reset
  • add fluent transition

• JFXAnimationTemplateAction

  • add dynamic end value/interpolator
  • add fluent transition

• JFXTemplateProcess

  • add time method

Details

The JFXAnimation project provides the JFXAnimationTemplate classes, which acts as a builder for JavaFX animations.<br> The building structure of a JFXAnimationTemplate is based on CSS keyframe animations, which have some advantages:

Features

• Define the animation in a relative way, based on different percentage values, related to a total animation duration or with a default absolute time.
• Multiple target observers per action
• Define the animation in a complete lazy evaluated way
• Finish events for every step/action
• Specific or global interpolator for all animation actions
• Use dynamic end values or interpolators which can be exchanged at runtime
• Transfer your current CSS animations easily to JavaFX
• Create animations simply for multiple animation objects

Code comparison

CSS TADA animation from animate.css

Implementation with Keyframe objects

Implementation with JFXAnimationTemplate

Implementation with pure CSS

As you can see, the default approach with KeyFrame objects has more lines of code.<br> Furthermore, there is a repetitive number of KeyFrames (each for a specific animation section) which causes a lot of duplicated KeyValue objects.<br><br> The JFXAnimationTemplate approach can handel one specified KeyFrame (action) on more animation sections due to different percentage values.<br> Moreover, you can specify more target observers for one specific end value.

How To

Create a JFXAnimationTemplate

The created type of JFXTemplate is use case specific. Mostly the JFXTemplateBuilder is used as final type, where T is the default animation object type.<br> A JFXTemplate can be created like that:

...
      JFXAnimationTemplate.create()
...

in this case the default animation object type T is a Node type.<br> It's also possible to set a own default animation object type:

...
      JFXAnimationTemplate.create(MyType.class)
...

After the init creation you have to specify a animation interval like you do in CSS.<br> You can use:

...
      JFXAnimationTemplate.create()
          .from()
...

which means 0%,

...
      JFXAnimationTemplate.create()
          .to()
...

which means 100% or

...
      JFXAnimationTemplate.create()
          .percent(10)
...

which is the percentage value. Furthermore you can specify multiple percentage values:

...
      JFXAnimationTemplate.create()
          .percent(10)
          .percent(20)
          .percent(30)
...

or via varargs:

...
      JFXAnimationTemplate.create()
          .percent(10, 20, 30)
...

Now you have to implement the specific action or actions like:

...
      JFXAnimationTemplate.create()
          .percent(10, 20, 30)
          .action(...)
          .action(...)
...

The action method can be called by value or in a lazy way. If you use the non lazy method you have to create a JFXAnimationTemplateAction.Builder<?, ?> manually like:

...
      JFXAnimationTemplateAction.builder()
...

The more comfortable possibility is to use the lazy approach where such a builder is ready to use like:

...
      JFXAnimationTemplate.create()
          .percent(10, 20, 30)
          .action(builder -> builder...)
...

The next step is to define the specific animation values like:

...
      JFXAnimationTemplate.create()
          .percent(10, 20, 30)
          .action(b -> b.target(Node::scaleXProperty).endValue(1))
...

For example you can use multiple target properties via varargs:

...
      JFXAnimationTemplate.create()
          .percent(10, 20, 30)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
...

There are a lot more functions and also lazy method representations, which also provides access to the actual animation object (like the target method in this example).<br><br>

Configure a JFXAnimationTemplate

Lets assume we have our animation action defined like this:

...
      JFXAnimationTemplate.create()
          .from()
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .percent(14)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1.3))
          .percent(28)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .percent(42)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1.3))
          .percent(70)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
...

We can finalize the animation by calling the config(...) method after the last action(...) method.<br> Again there are the same possibilities as for the JFXAnimationTemplateAction.Builder<?, ?>.<br> So we can use the non lazy version and create a JFXAnimationTemplateConfig.Builder manually like:

...
      JFXAnimationTemplateConfig.builder()
...

or the more comfortable possibility with the lazy approach like:

...
      JFXAnimationTemplate.create()
          .from()
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .percent(14)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1.3))
          .percent(28)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .percent(42)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1.3))
          .percent(70)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .config(builder -> builder...);

...

Now we have to define some config values like:

...
      JFXAnimationTemplate.create()
          .from()
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .percent(14)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1.3))
          .percent(28)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .percent(42)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1.3))
          .percent(70)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .config(b -> b.duration(Duration.seconds(1.3)).interpolator(Interpolator.EASE_BOTH));

...

We have to define the total duration of the animation and we can also define a interpolator which is used by all actions.<br> There are a lot more functions and also lazy method representations.<br> For more see the JFXAnimationTemplateConfig class.<br><br>

Build a JFXAnimationTemplate

After defining the actions and the config method, the last step is to build the final animation.<br> There are different approaches to build an animation.<br>

Default animation objects

Lets assume we have defined our animation for later use like this:

 ...
  private static final JFXTemplateBuilder<Node> HEART_BEAT =
      JFXAnimationTemplate.create()
          .percent(0)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .percent(14)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1.3))
          .percent(28)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .percent(42)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1.3))
          .percent(70)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .config(b -> b.duration(Duration.seconds(1.3)).interpolator(Interpolator.EASE_BOTH));

 ...

Now we want e.g. a Button to animate. We would build the animation like:

  ...
    Button button = new Button("Button");
    Timeline timeline = HEART_BEAT.build(button);
  ...

So the button is the default animation object and needs to be passed to the build(...) method.<br> The default return value is the ready to use Timeline.<br> There is also the possibility to use multiple default animation objects and also named animation objects.<br> For this purpose we have to use again a Builder in our build(...) method. And again we can do it in a non lazy:

  ...
    JFXTemplateBuilder.JFXAnimationObjectMapBuilder.builder()
  ...

or lazy way:

  ...
    Button button = new Button("Button");
    Timeline timeline = HEART_BEAT.build(builder -> builder...);
  ...

So to use multiple default animation objects via varargs we have to do the following:

  ...
    Button button = new Button("Button");
    Button button2 = new Button("Button2");
  ...
    Timeline timeline = HEART_BEAT.build(b -> b.defaultObject(button, button2));
  ...

Now the animation for both buttons are contained in the timeline object.<br>

Named animation objects

Lets assume we have defined our animation for later use like this:

 ...
  private static final JFXTemplateBuilder<Node> HEART_BEAT =
      JFXAnimationTemplate.create()
          .percent(0)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .percent(14)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1.3))
          .percent(28)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .action(b -> b.withAnimationObject("SpecialNode").target(Node::translateYProperty).endValue(20))
          .percent(42)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1.3))
          .percent(70)
          .action(b -> b.target(Node::scaleXProperty, Node::scaleYProperty).endValue(1))
          .config(b -> b.duration(Duration.seconds(1.3)).interpolator(Interpolator.EASE_BOTH));

 ...

Here we are using a named animation object "SpecialNode".<br> So this animation object will be used in exactly this action method.<br> There is also the possibility to define another type for the named animation object like:

  ...
          .action(b -> b.withAnimationObject(Button.class, "SpecialNode")...)
  ...

So a type of Button can be used in the defined animation values.<br> If we don't define a type a Node type will be used.<br> It's also possible to define multiple named animation objects via varargs for a specific type:

  ...
          .action(b -> b.withAnimationObject("SpecialNode", "SpecialNode2", "SpecialNode3")...)
  ...

To build our animation for e.g. a Button and our special Node we have to do the following:

  ...
    Button button = new Button("Button");
    Label specialNode = new Label("Label");

    Timeline timeline = HEART_BEAT.build(b -> b.defaultObject(button).namedObject("SpecialNode", specialNode));
  ...

We can also use multiple named animation objects via varargs for one name like:

  ...
    Button button = new Button("Button");
    Label specialNode = new Label("Label");
    Label specialNode2 = new Label("Label2");

    Timeline timeline = HEART_BEAT.build(b -> b.defaultObject(button).namedObject("SpecialNode", specialNode, specialNode2));
  ...

<br><br>

Build a specific animation container

The default animation container for a JFXAnimation is Timeline.<br> It can explicitly set at build time like:

  ...
    Button button = new Button("Button");

    Timeline timeline = myAnimation.build(JFXAnimationTemplates::buildTimeline, button);
  ...

Where buildTimeline is just a method which accepts a type of JFXAnimationTemplate, which contains all animation values and configs.<br> To use another animation container except Timeline, just write your own implementation, which handles the JFXAnimationTemplate instance.<br> For orientation the implementation of buildTimeline in JFXAnimationTemplates class can be used and copied.

Since version 2.0.0

Action with absolute duration

It's now also possible to use an action duration like the default behaviour with JavaFX KeyValues:

 ...
      JFXAnimationTemplate.create()
          .time(Duration.seconds(3))
 ...

You can combine time(...) with percent(...) definitions.

Dynamic end values and interpolators

The default behavior of the timeline in JavaFX usually does not allow the end value and/or interpolator to be changed during a running animation.<br> With a dynamic end value/interpolator this is now possible.<br> To use e.g. a dynamic end value you could define it like:

 ...
    JFXAnimationTemplate.create()
        .percent(10)
        .action(
            b -> b.target(Node::rotateProperty).endValue(InterpretationMode.DYNAMIC, node -> 3));
 ...

Now the end value function is called every interpolation step of the action.<br> You could define your own conditions or other methods in it.

The same is valid for the interpolator e.g.:

 ...
    JFXAnimationTemplate.create()
        .percent(10)
        .action(
            b ->
                b.target(Node::rotateProperty)
                    .interpolator(InterpretationMode.DYNAMIC, node -> Interpolator.LINEAR));
 ...

The more CSS way

It is now possible to adjust the animation more according to a CSS behavior.<br> For that purpose the new functions fromToAutoGen and autoReset exist.<br><br> The fromToAutoGen function generates automatically for every action target a related start(from) or end(to) action if it doesn't exist.<br> The generated actions uses as end values the last target values before the animations is build.<br><br> The autoReset function reset all targets to the values before an animation was built.<br> The behavior is similar to the animation-fill-mode: backwards in CSS.<br>

The functions can be used like:

 ...
        JFXAnimationTemplate.create()
            .percent(20)
            .action(b -> b.target(rectangle.translateXProperty()).endValue(150))
            .config(b -> b.duration(Duration.seconds(2))".autoReset()" or/and ".fromToAutoGen()")
            .build();
 ...

Fluent transition

The fluent transition function is useful in some situations and can be seen more or less as a helper function.<br> It can be defined on the whole animation or specific on an action.<br> Useful if an action is interrupted or the animation gets clipped.<br>

In this example an action is ignored and the animation would therefore look choppy:

 ...
        JFXAnimationTemplate.create()
            .percent(20)
            .action(b -> b.target(rectangle.translateXProperty()).endValue(150))
            .percent(60)
            .action(b -> b.target(rectangle.translateXProperty()).endValue(400).ignore())
            .config(b -> b.duration(Duration.seconds(2)).fromToAutoGen().fluentTransition())
            .build();
 ...

Demo

A full blown example of animations can be found in the demo project/package.<br> The demo uses JFoenix and is also included in the JFoenix demo package.<br> It also requires java 8 or 9.

Run the demo with:

 ./gradlew demo:animationDemo

Download

If you are using JFoenix, you don't have to use this dependency (it's already included in JFoenix).<br> If you use this dependency and switch later to JFoenix you can remove this dependency.<br> Furthermore, you have to change the package names from de.schlegel11.jfxanimation.* to com.jfoenix.transitions.template.*.

Gradle

 compile 'de.schlegel11:jfxanimation:2.0.0'

Maven

<dependency>
  <groupId>de.schlegel11</groupId>
  <artifactId>jfxanimation</artifactId>
  <version>2.0.0</version>
</dependency>