Sounds good to me. In that case, I think a "version 2" tag of some sort would be good for ideas, and we could use Milestones once we get the roadmap more nailed down.

You ask concentrate on the new features

You all I meant

I don't want to create any big waves unless we have a good reason for it though, we're kind of in a critical stage of adoption. Without a clear, good reason to break the API I don't think we should.

On the phone here

Typing on the phone is interesting

@edvin Agreed 100%

Yup

Once we get a bigger user base, we will probably get a much better idea for what we want in v2

Yeah, that's a good point Ruckus.

I'll be gone for a while, will be back tonight and will play more with the SmartResize feature. I started using it in a large app today and discovered some bugs. It's a large domain this resize thing 🙂 But so valuable. TableView resizing really sucks by default in JavaFX.

I'll be off most of the rest of the day too. Hopefully tomorrow I'll get some time to actually mess around with all this new awesomeness.

Cool 🙂 Talk to you guys later!

channel settings -> invite

Found it 🙂

Finally @eryzhikov :))

welcome

thanks

I have to run again 🙂 Back tonight!

@edvin regarding table column builders, okay that sounds fine. For TornadoFX 2, I propose to really think of a redone API for

TableView

column builders if our goal is to strive towards perfection and use our hindsight to do that.

and I would love a datadriven treeview /treetableview

I have it working (kind of) but it feels like a hack

@thomasnield Absolutely, that sounds like a good idea. We could start to dream up the perfect API already now and see what we could change without breaking things as well.

@ron I will definitely make that

Eugene you are from the guys behind the mobile javafx?

For version 2, it may not be a bad idea to revisit a lot of things. I'm sure there's a lot in the CSS that could be improved, and the animation stuff could be redesigned to make all animation more unified (for everything from simple node animations to timeline construction and view transitions).

We may find better ways to do a lot of the builders, especially the data driven ones.

@thomasnield: File an issue for it and add the

v2

tag

Just so we can keep track of what we want to look into when we get around to making the road map

@Ruckus Issue #171 is a nice one, although it isn't as bad as it used to. Extending Control and using the

StyleablePropertyFactory

it's very straight forward, but if we throw Kotlin into the mix we can reduce the boiler plate immensely.