It would be cool to show some of the transitions in the guide, if we can take some screenshots of the transitions in action.

Haha, you added both

explode

and

implode

👍

The

NewViewTransition

demos show all the builtin transitions in action (as well as a custom one to show how it's done)

I gotta get Alyssa to bed, will be back ASAP.

I still don't have any 3D effects in there, but that's not a limitation of the code (which should handle it fine), just a limitation on my animation abilities (it will require hotswapping effects for a

PerspectiveTransform

, and potentially bitmap captures, which I don't know how to do well enough yet, but once I learn them I have more ideas for some cool effects like paperfold and dissolve).

@Ruckus: @edvin I am very eager to see this. I'll take a look after I finish my webcast today

@Ruckus: now it's possible at least, and you cleaned up the API, which was probably the most important thing

I'm just hoping it's robust enough to cover most use cases. I don't know if I've missed anything.

Good luck @thomasnield !!

It's a great enhancement in any case though

Sooo... are you creating a fancy screencast for the new transitions @Ruckus or am I? 🙂

You'll have to if you want one, sorry. I can't install fancy screencap software on my work computer, and my home computer can't run IntelliJ and a screencap at the same time 😛

I'll get a better computer for home eventually, but for now I'm more focused on paying for the new car.

Haha 🙂 Yeah, that sounds like a good priority.

If you need any pointers on making custom transitions or anything, let me know.

I don't think I'll do anything crazy in the screencast, mostly show how it works and show the ones you made. But there is one thing I've been thinking about for a while.. When I started writing the framework there really wasn't any need for KDoc/JavaDoc inline because everything was kind of self explanatory. Now we have so much stuff that just discovering it all is hard, and then we have things like

ViewTransition

which is an abstract class with functions meant to be implemented by users. These things should have documentation in the code at the very least. I think maybe eventually we should have documentation for everything, at least with a short explanation of what a function is doing.

Maybe

ViewTransition

is a good place to start?

Fair point. I'll add some quick documentation.

Great. Then I'll start publishing the documentation somewhere too 🙂

I will start looking over the new features and polish them a little/look for bugs or stuff that should be cleaned up and start preparing for a release as well.

Sounds good

@edvin concerning the osgi

when you create a project using your archetype, maybe remove the

DashboardApp

?

starting that without OSGI throws a nice stacktrace 😉

@ron The DashboardApp is in the osgi sample, and that's the one that fails if you don't have OSGi enabled?

@edvin I just created a PR that includes documentation for the

ViewTransition

stuff

I'm not a technical writer by a long shot, so let me know if there's anything that needs to be worded better/differently.

Very nice! I will start doing the same when I add stuff now as well.

Just added the ability to ignore

fx:controller

attribute from FXML files, to enjoy code completion for action methods from FXML. https://github.com/edvin/tornadofx/issues/179

I wished I could detect this so you don't need to specify the parameter though...