@thomasnield Oh, and about the wife. This keyboard business doesn't even register on the scale of ludicrous stuff I put her through.

@edvin I'm going through the guide for the first time in probably two months. I think it might help to reorganize and move some topics to the appendix, like Internationalization and OSGi.

It's amazing how much functionality has been added to this.

Hi, I saw the documentation of TornadoFX and its really awesome.

However I found one difficulty with it.

How do I find what builder elements like button, textfield have what properties available.

Like button has a action {} textfield can have something else as well.

Similarly, how do I get the list of shortcuts?

especially I was looking for CommandORControl + Key

on Mac machines its command keys

@thomasnield Please do, that's great! Some of those things are better to look up when you need them

@harshmaur Until you get familiar with the API you can write

this.

and then click

Ctrl+Space

to see available actions on that object. Bear in mind that the actions and properties we added are extension functions, so you file should have an import for

tornadofx.*

so you can discover all these things with content assist. We also want to document each builder some time in the future 🙂

I know about the autocompletion, I will follow that for now. I will also see if I get time, I can document it for you.

Since you are going to document every builder element.

the project i am working on fairly large and a lot of use cases would be covered. I can document as we move.

@harshmaur That would be great! You can ask questions here and we'll answer them so you have enough information to add documentation. The builder elements should show an example of typical usage with some options.

maybe you can create a template

and show one builder

I can do the rest in the same way.

@harshmaur Absolutely, will do it today!

thanks!

I should thank you, getting started on the builder docs is most welcome and probably a big help to beginners

I am a beginner myself, documenting it would help me a lot as well. 😄

Yeah, that's a good way to explore the framework 🙂

So my first question. I want to create a button component that has some style and does an action which I would tell it from wherever I want to use it.

So basically I want to pass action to the button fragment.

from the view.

i use

add(find(com.note.fragment.StyledButton::class))

to add my button to the view

or let me know if I can use a better pattern

Right now its only the styles, I know, but in complex situations, the button could do a lot more things. So I want to keep all my UI components as Fragments and pass

props

to fragments