<@U0F3291QE> <@U78L28DMX> To me the scopes are onl...
# tornadofx
@edvin @amanda.hinchman-dominguez To me the scopes are only valuable when there's a substantial partition in the data. I don't think the "editScope" found in the documentation is a good usage. I'd define the model as the set of all people rather than scopes of "all the people" versus "one of the people". I would use scopes in this example for multi-tenancy. Say you're managing a set of people on behalf of someone, like if you organize a set of registered users by customer. Then, you might use a ClientScope to display a tableview{} in one Stage containing the customers from list #1 and a second Stage w. a tableview of customers list #2. https://github.com/edvin/tornadofx-guide/blob/master/part2/Scopes.md