That binding snippet stands as to how you'd chain a difference together

can Drawer be used without the sidebar tab-like interface? like open/close it from something else instead? I'm using JFeonix's Drawer for my app which works well enough.

I too am wondering this about Drawer. A collapsible sidebar is what I'm trying to implement in my application

If that's the case, I'd recommend using something like an anchor pane and animate the left anchor between 0 and the node's width (you could also use a stack pane and animate the position).

@Shan the JFoenix drawer is fairly easy to deal with if you don't want to roll your own. In fact i found the drawer to be super easy... the hamburger button that you can use with it on the other hand 🤷

@Spike Baylor I am messing around with a SplitPane layout right now to function as a sidebar and it's actually working quite well. I'm pretty sure I can set the width of one SplitPane item (the sidebar) while clicking on the menu icon so it should function correctly. I wanted the sidebar to be resizable anyways, so this all works out quite nicely 😯

for once 😬

interesting

https://github.com/dlemmermann/WorkbenchFX also has "drawer" you may want to check out. With a nicer "button" 🙂

I created something a bit similar to "drawers" several years ago called

AdjustableBorderPane

(hate the name). It acts like a border pane but has invisible grippers allowing you to adjust the size of the top/bottom/left/right panes and supports a slide animation for showing/hiding them. Its in Java (Java 7 even!) but I'd be happy to convert it over to Kotlin if anyone thinks it'd be useful.

I'm trying to use the tableview, I am copying the table to the clipboard in a csv format like this:

button("copy all").action {
    val clipboard = Clipboard.getSystemClipboard()
    val content = ClipboardContent()
    var copyString = table.items[0].propsToCsv()
    copyString += table.items.joinToString("\n") {rowItem ->
        rowItem.toCsv()
    }
    content.putString(copyString)
    clipboard.setContent(content)
}

but I'm using it in two different places, both models on the table extend a "CsvJsonModel" that generates the correct strings for the header and rows... however if I try to write a function like this:

fun copyTableToClipboard(dataTable: TableView<CsvJsonModel>) {
    val clipboard = Clipboard.getSystemClipboard()
    val content = ClipboardContent()
    var copyString = dataTable.items[0].propsToCsv()
    copyString += dataTable.items.joinToString("\n") {rowItem ->
        rowItem.toCsv()
    }
    content.putString(copyString)
    clipboard.setContent(content)
}

and then implement it with

button("copy all").action {
   copyTableToClipboard(myTable)
}

it throws the error: Error:(95, 54) Kotlin: Type mismatch: inferred type is TableView<CirclePlotModel!> but TableView<CsvJsonModel> was expected

Do I have to make a special TableView<CirclePlotModel>: TableView<CsvJsonModel> or something? or do I need to change my function'sarguments?

fixed it by looking up how to do generics in kotlin:

fun copyTableToClipboard(dataTable: TableView<out CsvJsonModel>)

Sorry for the wall of text!

<deleted reply> (misread an error)

i always wondered what T! meant when it pops up in IDEA

it's kind of a long talk, but it gives an insight why

!

and what alternatives were considered

It's called a platform type: https://kotlinlang.org/docs/reference/java-interop.html#null-safety-and-platform-types

ah

Any time you see things like

Type!

or

(Mutable)Collection<Type!>!

or

Array<(out) Type!>!

, those are types that were sent if from interoperation with other languages, and so Kotlin can't tell you for sure if the type is nullable, mutable, or variant, and lets you handle it instead.

Since Java has no concept of nullable types, mutable vs immutable collections types, etc.

you mean can't tell you?

Yeah, sorry, typo

Fixed

makes sense. Good to know

Is there any library for UI migrated to tornado? Like JFoenix, I'm a fucking design noob 😅

what do you mean? you can use JFoenix or any other javafx based library directly with tornadofx

@Ruckus interesting, why did they renamed them? Seems like flexible types are more general term for the idea behind, while "platform types" gives better understanding.

I have no idea. I wasn't actually aware they were ever called flexible types. Platform types were introduced in 2014 (before that talk, though I haven't watched it): https://blog.jetbrains.com/kotlin/2014/10/making-platform-interop-even-smoother/