@harshmaur I am not on my computer now so I can't post any code. If your fragment only contains one button that would be a bit overkill. I would just use the button builder and add a specific style class to every button that should look the same and add an action function to it

button ("button-label") {
 addClass("styleclass")
action {
//do your action here
}
}

Yes I thought so. Add a style and use it.

then I gave it a different thought and thinking if I can create an HOC for a button

and then import button from my custom package

Just exploring different ways to create my UI, I am used to creating UI components with functionality being passed to it from outside and modify the behavior of the component.

@harshmaur On a general note, injecting viewmodels into the scope of that component is a very clean way of passing information between your UI pieces. It could even be used for this purpose, but as it was pointed out, it might be overkill with a View or Fragment for a single button. Styles can also be conditionally toggled based on some property.

Yes right, I was wrong about using a fragment with just a single UI element, what actually meant was using an HOC of button

and instead of importing button from tornadofx.*, I import it from my own UI package.

is that possible?

@harshmaur Possible, but why would you want to? If you want to augment the behavior of a button you could consider adding a style class that changes the skin of the button instead.

majorly because I am using a different pattern, Keeping the styles and logic isolated with the button

instead of creating a global style.

and that button would have holes that would let me use it just like a native button.

Just a pattern I like to use.

also because lets say I want to have same elements across multiple applications

I can just import my components package and use them

that would give me custom styles + custom functionality

does that make sense? 😮

Sure, but you can still do that by exporting styles and skins in a custom component package 🙂

If you want to create other instances of button that what you get from the button builder you'd need to create your own builders. That's pretty easy, but I'm also pretty sure it's not needed.

i watched your video on a custom stylesheet so that i understood.

Okay let me give you another example

Lets say there is a button

which on click first increases the font size

and also fills the color

now I use this button at 10 places

everywhere I have to use button { action { // change color, //change font} }

what if I created my own button

and created my own action