I am sticking with TornadoFx for now. It does appear to be moribund, but it just doesn't feel like there's anywhere to jump. I'll tell you one thing, my views are heavily isolated from my models which are heavily isolated from my domain code. 🙂

I also moved to Compose for Desktop. There are a few things that I found I had to put together myself e.g. a Table view, but overall I found it easier to get moving quickly with Compose for Desktop than I did with Tornado.

i still use javafx + kotlin, but i copy the dsl stuff from tornado into my project. I have kicked around the idea of splitting just the dsl into a separate library, but never had had the time to work on it. i dont like the dependency injection and other stuff from tornado as much

but i like java 17, so i cant just use tornadofx out of the box anymore

Yeah, similar here. I was playing with the idea to auto-generate a Kotlin DSL from FXML / JavaFX API via https://github.com/square/kotlinpoet or so...

is there any way to make a tableview editable by a single click rather than double-clicking a cell, think Excel? Also, am I missing some documentation for tornadofx because on the webpage, the guide barely scratches the surface of the api and the kdoc is plain unreadable?

"To allow editing and rendering, TornadoFX provides a few default cell factories you can invoke on a column easily through extension functions.",

useTextField()

for example, but how does one use it? It does not appear to be callable on a column at all.

tv.selectionModel.selectedItemProperty().addListener(fun(obs, oldSelection, newSelection) {
    if (newSelection != null) {
        val row: Int = tv.selectionModel.selectedCells[0].row
        val col = tv.columns[tv.selectionModel.selectedCells[0].column]
        Platform.runLater { tv.edit(row, col) }
    }

appears to work for selecting cells with single click but I have no clue how I'd make it commit edits on focus loss or allow movement between cells using key combinations, as enter boots the focus to the parent element

I'm going to have to either fake a table with just vboxes of hboxes of textfields because tableview is impossible to work with given the zero documentation or find a completely differrent ui lib

How am I supposed to manage global state across views in a tornadofx application?

I'm trying to add a "+" tab in a tabpane to create more tabs. Everything else is working fine, but calling

close()

from the tab itself throws a NPE. Minimal example:

class addTab : View(" + ") {
    override val root = label("You should not see this.")

    override fun onTabSelected() {
        super.onTabSelected()
        with(MainView.tabs) {
            tab("new", nonuniqueTab("foo"))
            tabs[tabs.size - 1].select()
        }
        close()
    }
}

creates a new tab from fragment just fine, tabs is the tabpane, but close causes

java.lang.NullPointerException: Cannot invoke "javafx.beans.value.ChangeListener.changed(javafx.beans.value.ObservableValue, Object, Object)" because "<local3>[<local7>]" is null

Or is it possible to reorder or open a tab between existing tabs to avoid having to close and reopen the + tab?

I have a component where I want to have CSS classes I can toggle to change the appearance. However, this component can't add its Stylesheet to a Scene, since it isn't creating a Scene; the thing that is using this component makes the Scene, and does so after the component is instantiated. What's the right way to go about this?

## (This project is no longer maintained) 😕 https://github.com/edvin/tornadofx/commit/94fd553aced7a2ffe7528b1977a9f8406028432c

Hello guys, is possible debounce click in button?

<sigh> Using unsupported tornadofx is really getting to be a drag. The modules in the snapshot appear to be wrong.

It was good while it lasted, but Compose Desktop seems to be the way forward.

I still think vanilla javafx with kotlin is a good choice. But if we can get something like https://github.com/maroc81/kitfx going, its even better

I may just be a old stick in the mud, but compose desktop seems like a) it is the coming thing, b) it is not really ready for prime-time yet.

Still. I plan to engage with it seriously over the next year. My problem here is that my WIP is JavaFx. I just tore out 100% of my TornadoFX dependency to see if I could get to a proper binary executable w/o it, and it looks like I'm hella close.

I'll have to re-roll my whole UI in plain JavaFx or using kitfx, but if I can just get a damned GUI screen on a stranger's computer with a single link, I'll do whatever's necessary.

I spoze it was just dumb of me to assume that the world's first "highly interoperable programming language" would be able to create an installable exe easily. 🙂

@geepawhill Take a look at https://hydraulic.dev/ - it's got built in javafx support and is used by some javafx apps

you run

conveyor make copied-site

and it packages/signs/uploads your release in such a way that existing installs self-update.

(disclosure: i make it) - it's about as close as you can get to pressing "enter" and getting a link you can send to people

Thanks, Mike. I actually searched for it sometime last week, but it was told to me as "try conveyor", and there is no search term on earth that got me past hardware conveyor system and software. 🙂 I will definitely check it out.

That is indeed a problem with the name.

[conveyor desktop app packaging] does work but that's pretty specific

Latest dead-end: the badass plugin has two open bugs and an overworked caretaker. I can switch between the bugs at will. Further, all of this is w/o tornadofx as a dependency, so even were I to get past one of these bugs, I still have little confidence that I can get all the way to a binary.

I got, ummmm, I think I got, conveyor to work. Here's current status, via mastodon: https://mastodon.social/@GeePawHill/110783935130320427

Quick question I hope someone can help me with. I have a view that uses a borderpane for root, with items in top, center, and bottom. The center item is a fragment (or view, I've tried both) that is supposed to swap out for a replacement fragment (or view). Instead it wipes the entire parent view, except for the original fragment, which is then up in the top left corner. (Simplified code fragments in the thread.) (Fixed)