@ron: The whole error message is a little bizarre. I don't actually think it was the version upgrade that fixed it, I think it was that it stopped using a corrupt index in IDEA. I think a re-index would have solved it as well.

which makes it even more bizar, this is on a completely new machine. My desktop died and I rebuilt it using old parts I had lying around, its lovingly called frankenstein

so where is the corrupt index coming from? everything is a fresh install

@User uploaded a file: Untitled and commented: is this still the best way to link variables to properties?

wow most of my views are now deprecated?

@ron: That's now one of two ways to create properties, and totally valid still. I use that one. Alternative is:

@User uploaded a file: Untitled

The downside to this alternative is that it doesn't create a function to expose the property, only a field. Just stick to how you're already doing it.

@ron: About deprecation: It should only be minor tweaks required. Feel free to post something it says it deprecated and I'll show you how to rewrite.

@User uploaded a file: Untitled

I really liked this way of defining views

now I feel (at a first glance) its a bit overboard with the splitting up

In this case

`top`

and

`center`

are deprecated

Here you simply change to

top = menubar {

and

center= tabpane {

. This change is not driven by a "need" to improve the syntax, but to avoid subtle bugs.

hmmz that does not completely sort it, as the hbox that is also in top is ignored now, I have to move the menubar and the hbox into another container

yup that works

I might change that hbox into form later but I am going to work on the logic first

@ron: Yeah, that's right, I forgot to mention. Instead of giving you a vbox behind the scenes if you add more than one child, you'll have to explicity create the hierarchy you want. It might seem like a regression at first, but imagine if you set some properties of that implicit vbox, and later remove one child - then the child you added will be the top object, and the properties you set on the temporary vbox is lost. That's why we made this change, to avoid issues like that. The issue you now encountered you were able to solve intuitively, but the other issue would be much harder to debug.

The example in the tornadofx guide only shows where other views are used. I would add an example where the view is built the way I showed. I think there are enough use cases for that way too

Making the containers explicit is a good thing™

Hang on, I might be kidding with you. I think we found a way to support the way you built your UI above for 1.5.3. Hang on..

My head is not in the game, this cabin is killing me 🙂

Yes we did.

I much see myself as the typical developer here. I use the framework to create applications not the framework

@ron: Very useful. It's hard to see how the typical user will view the framework when you have more intimate knowledge with the codebase.

And as you have seen I know how to think up the weirdest applications

A bit unfortunate that we didn't get the fix in the same release so we could avoid the deprecation note 🙂 Just keep your current syntax and you should be good. 1.5.3 will be out shortly.

With lua and graphs and such

Haha, yes indeed 🙂

I am the typical nerd I build what I think I need