tornadofx-guide

Workspaces
workspace.dockInNewScope()
When the CustomerList docks the CustomerEditor later on, it happens in this new scope.
But what about the search field?
We would need to provide a separate scope for the CustomerEditor that should show the
result of the search, but were we would also also need to inject the customer model
containing the selected customer into the new scope. This following code is imagined inside
the action that selects a customer from the search result:
fun editCustomer(customer: Customer) {
// Create a view model for the customer
val model = CustomerModel(customer)
// Create a new scope, but keep the current workspace
val newScope = Scope(workspace)
// Insert the customer model into the new scope
newScope.set(model)
// Find the CustomerEditor in the new scope
val editor = find(newScope)
// Dock the editor
workspace.dock(editor)
}
That's a lot of steps. Fortunately, we can do that as well in a single call:
fun editCustomer(customer: Customer) {
}
workspace.dockInNewScope(CustomerModel(customer))
The dockInNewScope function takes a vararg list of injectable objects to insert into the new
scope before looking up our CustomerEditor and docking it.
Separating scopes this way makes sure we can utilize injected view models without being
afraid of other views stepping on our data. It is a pragmatic approach to an intricate problem.
It also gives you a way of bleeding injectables into new scopes, should your use case
require it.
Custom ViewStack optimizations
239