Makes sense. I like it

Speaking of TorndadoFX 2 though, we may want to start actually working on a roadmap for it.

That's a great idea!

I don't know how many Kotlin 1.1 features will have much of an effect on TornadoFX, but we could have the releases coincide (to some degree).

Sounds good. For now we should focus on getting these new features in, get rid of any bugs and add small features in the next few releases and finish the guide. Then it would be good to start working on 2.0

Sounds good to me.

What will the roadmap look like?

How much are we sticking to Semver?

Well, we've had breaking changes between 1.4 and 1.5 etc.

Most of the functionality is currently based around making standard javafx nicer

Only the fatso's is something I see as completely new

For example, it would demand we keep the current and last versions up to date, so TornadoFX 1.x and TornadoFX 2 would have to stay up to date if we really want to stick to Semver.

Is this something we want to worry about?

But 1.x would be in maintenance mode

Indeed

Only bug fixing no new functionality and no backporting

Let's not decide until we have created a roadmap, find out how large any breaking changes are, if we can support the old syntax via an optional adapter dependency etc.

Do you really want to go there?

Can I vote against😉

Against which part? 🙂

The adapter

It could be a very minor thing, making old syntax usable in 2.0. But it all depends on what we're going to break.

I don't think we have any large issues right now anyways, and I want to focus on getting these features into 1.5.6 and keep improving them and simultaneously finish the guide.

We would also probably want to document a good migration path from v1 to v2, etc. I think making the roadmap will be quite involved to figure out what we want, so holding off for now isn't a bad idea, but we should have a place to keep ideas. Should we use GitHub, or possibly some other source (like Trello or something)?

I will adapt some of the samples from the samples project

We can start with GitHub and then move to Trello or something similar if needed maybe?

Milestones and release in GitHub are quite good

I think we still have examples that needs updating to the current syntax even

I will have a look at them

Great Ron