I rember someone asked yesterday or before where the resources for an imageview should be placed. Probably one should but some note in the guide because I’m also stuck with this. The example says imageview(“tornado.jpg”) but nothing about where to put tornado.jpg. Most frameworks have some kind of resource folder, but this is not generated by the plugin. What is however the difference between imageview and resources.imageview, found in the Wizard Example? Adding it to the same folder where the view is does not work either. So does it have to be at the project root, in src, main, kotlin? If I need to create a res folder, where is the right place? Entering tornadofx and imageview unfortunately only gives me tutorials without imageview. I would be very happy if someone can give me a hint 🙂

@edvin I am setting a style to my textfield and text area. I want to make the border radius to 0. What and how should I use ? backgroundRadius or borderRadius ?

I was able to find the solution for the graphic after inspecting your stageicontest.rar I saw that the resources folder is und main in the same level as kotlin. I created the folder and added the image and everythings works. This would be easier when the folder is created automatically

@thomasnield I think I'll try to add it tonight 🙂

It might need to support visiting rows that are not empty as well, maybe using an option.

That option could be added to cellFormat as well actually.

@dr.fornax It is up to your build system to copy resources onto the classpath. Both Gradle and Maven copy everything under resources onto the classpath by default. TornadoFX accepts paths relative to the Component. I will update the guide with some more info :) Thanks for mentioning it!

@dr.fornax also watch for non-.java artifacts in your src. they sometimes don't get copied over by build tools because they're not compiled. Specifically, .fxml and images

Yeah, so you need to either place them in resources, or change the build tool configuration to include all or some files in src. I think it's much cleaner to keep them in resources, so you can keep the default config of the build tool.

It's a bit cheating, but what do you think of the followig function:

fun KeyFrame(time: Duration,eventHandler: (ActionEvent)->Unit) = KeyFrame(time, EventHandler { it-> eventHandler(it)}, *arrayOfNulls<KeyValue>(0))

@aayush I think you might want to use both. This post from last year might give you some ideas on their application. http://bekwam.blogspot.com/2016/09/visual-cues-through-javafx.html

I think this is great code for small views:

open class SimpleView constructor(title: String?, icon: Node?, rootGenerator: View.()-> Parent) : View(title, icon){
    constructor(title: String?, rootGenerator: View.()-> Parent) : this(title, null, rootGenerator)
    constructor(icon: Node?, rootGenerator: View.()-> Parent) : this(null, icon, rootGenerator)
    constructor(rootGenerator: View.()-> Parent) : this(null, null, rootGenerator)

    override val root: Parent = rootGenerator(this)
}

this can't break anything, isn't it?

it seems like you get a compiler error when you do something that isn't allowed, sso immediate feedback

@tieskedh We already have support for building inline views 🙂

@edvin Maybe we could use them standard in testapps and tornadofx-examples? Because there, we need to apply the best practices, can we come away everywhere by not having a class? Or does it create a real view, instead of an UIcomponent? I believe that for example the class app needs a class???

@tieskedh I use them seldom, and mostly for dialogs. Let me look up some examples from a real world project.

@User uploaded a file: Untitled

I saw, but you have classes with only a hbox, maybe use them there?

Maybe. I'd like to see a use case before I comment. Most of the time it's worth creating a View IMO 🙂

And that is what you do with my code :-)

You create a view, where you set the root node to whatever you return form the extension-lambda

I have to go to school again....

@tieskedh I guess we can include it for those simple Views. It can't hurt 🙂

I just added button builders that accept ObservableValue<String> that will bind to the textProperty of the button.

@edvin This is my css for text field, all the properties are being applied except -fx-font-size.

.custom-text-field{
    -fx-background-color: rgba(235, 239, 242, 1);
    -fx-background-radius: 0;
    -fx-border-radius: 0;
    -fx-text-fill: #3f465d;
    -fx-font-size: 10px;
    -fx-min-height: 20.0;
    -fx-max-height: 20.0;
    -fx-padding: 5px;
}

@aayush Maybe you need to be more specific with your selector? Try adding !important to the font-size, or increase specificity.

@User uploaded a file:

@edvin How do I use a combo box within my table view (custom table view)?

@ajithprasaad You can override cellFormat and assign the comboBox to the graphicProperty as a simple solution 🙂 More advanced use cases calls for a custom cell or a CellFragment for example. If the guide is lacking examples of this we should add it.

Yeah, there is no such example in the guide. Can you send a small snippet of the implementation?