@edvin The section on validation (https://edvin.gitbooks.io/tornadofx-guide/content/11.%20ViewModel%20and%20Validation.html) and how to gather multiple

Validators

into a

ValidationContext

could use an example. I can't figure out how to do that. Also, I belive the the text

Normally you would validate user input from multiple controls or input fields at once.

should read

Normally you would validate user input from multiple controls or input fields one at a time.

@permalmberg Thank you, will fix when I get back home 🙂

@User uploaded a file: and commented: @edvin I finally got around to adding the

squeezebox

. It is freaking awesome. So easy to use and fits perfectly! Only downside is it isn't mentioned in the docs 🙂

How do you guys handle the width and height of an application window at start up? My window covers booth my screens from top to bottom...

Override a method in App called createPrimaryScene. Return Scene(view.root, 800, 600)

@carlw I knew there had to be an easy way! 🙂

Tomas (ReactFX) wrote about a similar problem with garbage-collected listeners. I previously had problems (and wrote about them in this channel) with

selectedCity.onChange()

(see: TornadoFX Guide, chapter 4, "ComboBox" section) not calling the callback on value changes. http://tomasmikula.github.io/blog/2015/02/10/the-trouble-with-weak-listeners.html

No there is no problem with the code in the guide, only with how I implemented it in my example

View

class. 😄

when I have a single

View

in my

App

I use

setPrefSize()

to change the

Stage

size. good for my use-cases, but obviously it is prefered to change the size in the

App

.

class MyApp : App(MyView::class) {
//    override fun createPrimaryScene(view: UIComponent) =
//        Scene(view.root, 800.0, 600.0)
}

class MyView : View() {
    override val root = stackpane {
        setPrefSize(200.0, 200.0)
        label("foo")
    }
}

@permalmberg Ah, great! I will document that as well when I come back home. Thanks for reminding me!

TornadoFX Guide: A screenshot for every source code example (at least for code snippets with significant changes) and a link to an SSCCE in a repository would be nice.

sscce ?

@permalmberg Short, Self Contained, Correct (Compilable), Example. http://sscce.org/

oh

@hastebrot Good idea! I'll try to set that up.

I have the (incomplete) TestFX component for automatic screenshot generation somewhere. I'm exited to continue my work in it, to be able to use it for the screenshots in the guide. It is also possible to find the complete window bounds (including the complete window of the OS) to include it in the screenshot, if needed.

That would be pretty cool!

Maybe I could set up a service with it to create deterministic links to the screenshots which caches the resulting image as well.

@edvin what do you think about renaming the view classes in the examples from

MyView

to e.g.

LayoutStackPaneExampleView

(or maybe something shorter). Does this make sense? maybe the package where the examples are is enough.

we could also put

<!-- example a.b.c -->

into the markdown and use something to replace it with the example source code. I guess there is no need for a markdown parser to mixin the code. disadvange of this would be, that we can't edit the example code directly in the markdown document.

I think it's easier to use something like the example a.b.c comment probably.

I'm still reading the TFX guide. chapter 7 right now.

ViewModel

,

Scopes

and

Workspaces

are concepts I need to get familiar with. then I'll jump into writing code.

Great Benjamin!

@hastebrot Scopes might be of particular interest in testing because you can create and tear down an whole object graph. Ex, use a testing scope in place of singleton for repeated calls involving a complete creation scenario

Good thinking Carl. Actually we could remove all existing scopes and clear the DefaultScope.

yeah. normally an object graph in java might be too broad for a unit test (>1 class file). but in Kotlin, the unit is ambiguous because you can pack a lot into a Kotlin file (>1 class file, data class,e tc)

Just got an idea. The squeezebox should support closable tabs and an icon mode, like the left/right side tool bars in IDEA. Then it could be used as docking targets left/right in the Workspace.

I have code that shows and hides a pane in the kphoto repo

I'm starting to tornado-ize my small application. first thing we have is a file loading service. I'll put the

findFiles()

function into a controller, and the

baseDirectory

and

loadedFiles

into a model. I guess, this should be right. Next up is testing the controller, model, and probably the scope...

A small problem could be, that for the file loading service I don't need a view. Maybe a view that lists loaded files would be ok, the draw a complete arc from model, controller to view and app.