From November 2017 (the current pom has one from Nov 2013)

maybe they've already solved this ?

Updated 🙂 But tornadofx will automatically create longs for localdatetime so that still has to be configurable

@edvin What do you think about this? Can you mark a data class with an annotation to get this to work?

@carlw That would be a different project, but support for jsonb wouldn't be all that hard.

You're just going to set a global property or register a custom Serializer/Deserializer object?

Would it be worth considering the Kotlin serialization library to deal with JSON?

@carlw In it's current form, I think that would be the easiest. @kastork Which one is that?

@edvin https://github.com/Kotlin/kotlinx.serialization

@kastork Thanks, checking 🙂

in an ItemViewModel i can wrap simple plain values with the ViewModel.bind function.

@iari commented on @iari’s file https://kotlinlang.slack.com/files/U91Q93944/F92TGASPR/wrap_lists_in_data_class_as_javafx_properties_in_an_ItemViewModel.txt: How do I properly do that, with a List or collection?

I am encountering some strange behavior that I fixed but don't quite understand why it works. I have a view that is entering information into a tableview by a textfield and a checkbox. When I commit the information and the model adds the new entity to the tableview, I want focus to return to the initial textfield and have its contents highlighted. I execute the following when committed

lengthTF.requestFocus(); lengthTF.selectAll()

. Now this action works in my initial approach but when I introduce a TextFormatter to filter non-numeric values the previous code snippet does not highlight the contents of the textfield. However, when I wrap the request in

runLater(Duration(0.0)

function, the contents of the textfield are focused and highlighted. Can anyone explain this strange behavior? Here a standalone example.

@bkenn Although, I haven't looked into the code with much detail. You might be falling into a race condition, where your request to focus is called before the TextFormatter completes its job and therefore adding a

runLater

helps. You can confirm this by adding print statments in both

refocus()

and TextFormatter.

I updated the IDEA plugin to try to address some of the issues raised lately. I think there was an API change or two with the kotlin plugin that caused some issues.

What is the best practize to edit/bind the contents of a Map<K,V> with TornadoFX ?

@iari Basically you bind it as any other property, unless you want to bind each individual key. The exact approach would depend on your use case I think.

I would like to bind the individual values (and maybe keys)

@edvin regarding https://github.com/edvin/tornadofx/issues/140#issuecomment-362196272: I did not have an actual issue - just missing documentation. would you like me to create new issues in that case anyways?

I opened a PR to fix the tests not running during

mvn test

locally and at Travis https://github.com/edvin/tornadofx/pull/620. I reverted part of a change by @kastork that sought to increase the isolation between the test cases. I think there may still be some need for that, but I think we'll need to use a different approach

@iari Maybe you could add a small PR to the guide? 🙂

I ran into another FXML bug today. According to the documentation (https://docs.oracle.com/javase/8/javafx/api/javafx/fxml/doc-files/introduction_to_fxml.html#property_elements)

Elements whose tag names begin with a lowercase letter represent object properties.

However, it appears it actually needs to start with more than one letter (e.g.

xOffset

will not work). Has anyone else ever run into this?

@Ruckus I haven't because I'm authoring FXML through Scene Builder (both Oracle and Gluon to this day). I'm not interested in elements versus attributes. However, I would like to see a Custom Properties pane that would give me access to the map on the Node.

I ran into it when I was doing some FXML binding. I got around it for now by changing the property name to

offsetX

, but it's still annoying.

@Ruckus are you using scene builder?

Not at the moment. I'm just writing it by hand for now. Once I get the general layout figured out, I find it much quicker to iterate and test editing the FXML by hand than in SB.

i had high hopes for Scene Builder a few years ago. i was coming off an iOS project and though it was headed in an XCode direction. Specifically, the ability to manage the layouts dynamically within the tool (ex an embedded LayoutDebugger or ScenicView) and drag-and-drop to sync up with Controllers. IntelliJ helps, but it's still a few steps behind what an Apple developer would use

@carlw I haven't used Scene Builder extensively, but what features do you think it's missing? I wanted to try out Scene Builder's event tracker in combination with debugging soon (I've been sick lately and going to bed early, putting me back a bit)

i use scene builder still on projects. however, the development process is fragmented. even though you can bring up a Scene Builder window in IntelliJ -- which I don't do because something like setting a Controller are missing -- it's still a UI (.fxml) versus code (.java) mentality. On the plus side, there is a lot of compatibility so when there was a bad Gluon build a year ago, my Oracle SBs still worked