@ron It is the normal tornadofx.jar, yes. We include OSGI metadata by default 🙂

good to know, I will make some example code for the onCommit based on a builder and a readonly object

I can btw imagine the Carl case with the controller in the fxml file

allthough I never use fxml

@ron Great 🙂 The metadata is created by a maven plugin, you can take a look in either tornadofx's pom, or in the default template project you get when you create an osgi sample from IDEA.

I'm eager to hear what Carl thinks about this 🙂

@User uploaded a file: Untitled and commented: yes, you may cry

notice the complete dependance on windows (the webapp\\src path) and the dependency on how eclipse builds a path for a plugin

That's madness 🙂

On the bright side, it's deprecated.. haha

@User uploaded a file: Untitled

now this is madness

yes, that is one method and yes, it works on manually captured objects that hibernate created (there is the same method but then for deletion) and "undoes" what has happened

@edvin I've had success on projects putting graphic designers in front of Scene Builder with a stylesheet. So, anything that keeps the UI code (Tornado or plain JavaFX) in sync with these artifacts is great.

@edvin I'm shooting for the experience you get from XCode -- and I've pulled the Scene Builder code too -- where you drag-and-drop controls onto code and reference code in the WYSIWYG tool.

@edvin I'm going to write a larger TornadoFX program, one that involves Fragments(), to get a better feel for TornadoFX.

@carlw FXML is a first class citizen in TornadoFX, but the only good reason for adding the

fx:controller

attribute is to get content completion for action calls etc. If you add the attribute, just pass

true

to the

fxml()

delegate. If you don't add it, that's also fine, it will be automatically assigned 🙂 I'm very eager to hear your thoughts after trying it a bit at scale 🙂

I just want to make sure that you know that you can just do

override val root : BorderPane by fxml()

and the FXML file is loaded automatically 🙂

And that you don't need the

@FXML

annotation. To "inject" a component from an FXML file, just do

val myButton: Button by fxid()

. That will inject

<Button fx:id="myButton">

automatically.

@edvin I hacked Controller.kt (the setController() version) and got my JavaFX Controller to work. I still don't get the code completion in Scene Builder which looks completely tied to Java.

@carlw Why did you need to change anything? I suspect we are misunderstanding each other here.

Using Scene Builder with TornadoFX is a good practice, and doesn't require any changes to the framework 🙂

@edvin (two messages back) I've been using "by fxml()" and the overall flow of TornadoFX is fine for my skill set.

(Gotta bring Alyssa to Jiu Jitsu training, will try to continue from my mobile, brb)

@edvin I think I was experimenting with my JavaFX Controllers without the attribute and seeing how the controller object was created.

Ah :) Let me know if you run into any pain points or have ideas about how we can improve this :)

I will release 1.5.6 tonight btw :)

Great. I've been working with the SNAPSHOT for the past few weeks

Sweet. Will post here when it's out!

good then I will make the viewmodel onCommit example with a released version 😉