The Branch Terminator

This release comes with only a single major feature:

1. Pluggable Injector

However an extensible DI makes 80% of the current pull requests and branches obsolete. Now you can replace the built-in injection with whatever framework you like.

convenience

Afterburner.fx 1.6.3 introduces the following features:

1. fxml files are loaded as camel and lower case
2. Resources (css) can be case-insensitive
3. FXML uses ExecutorService instead of Executor -> more power to FXMLView subclasses
4. FXMLView inherits from StackPane (needed for custom components in Java FX Scene Builder)
5. getViewAsync refactored -> view initialization is performed asynchronously
6. Threads needed for asynchronous loading are afterburner.fx- (easier to profile in e.g. jvisualvm)
7. Exception reporter added for asynchronous view creation

Mobile Burner

Mobile Edition

Kill The Bug

1. Community ideas incorporated
2. Bug "Per view DI model/service conflict #44" fixed

Demons And Fixes

1. Asynchronous loading uses demon threads.
2. Per-view DI does not interfere with Model and Service injection any more.

Lazy initialization, Asynchronous loading and per-view-instance injection

1. Views and presenters are instantiated lazily
2. The construction of the view can be initiated synchronously or asynchronously.
3. An "injection context" can be passed to a FXMLView's constructor and is going to be used for injection into presenter.

Java 8, Custom Properties and Instance Suppliers

afterburner.fx was rewritten internally to use Java 8.

1. Afterburner 1.5.1 uses Java 8 and will not run on Java 7 any more.
2. Properties are no more limited to files and System.getProperties. You can provide your own function to provide you own configuration.
3. Injector (prior name InjectionProvider) can use an external InstanceSupplier function which is going to be used to fetch models and services. You can "inject" you own instances and bypass the conventional mechanism
4. Internal cache uses weak references. This prevents "memory leaks" -> no more referenced models and services are going to be GCed automatically.