Init might be better.

just pseudocode...main idea is a centralized module config...modules (not sure about java 9) would be the next conceptual grouping above scoping

ex, packing a tornadofx app with different modules to keep the footprint down

not speaking about Java 9 Modules yet

I need to take care of something for work, will probably go to bed after, but will think more about this. Great stuff, Carl!

np. talk to you tomorrow

@carlw Had to try one thing 🙂 What if you can say

DefaultScope.fix(MyController::class, MyView::class)

?

You could also go the other way and say:

MyController::class.fixTo(DefaultScope)

fix

and

fixTo

are probably not the right words.

no, fix isn't a good word for this. Guice supports all three techniques: no marking (default scope), centralized marking (say with the App), and class marking (MyControlller::class)

So

mark

is a meaningful verb for this?

Unless we use annotations it won't be possible to keep this config with the class, only centralized.

maybe scope for the component-level marking, ex "MyController::class.scope(DefaultScope)"

That could work.

and for the centralized marking, some type of init{}, constructor thing

DefaultScope {

MyController::class,

OtherController::clas

}

SingletonScope {

MyDAO::class

}

We might be able to use

invoke

as an operator function on the scope, hang on, will check.

That works, so you can write

DefaultScope(MyController::class, OtherController::class)

init

in the App class is probably a good way to put that stuff.

Another good place would be inside the scope, actually.

Don't forget about the rules for mixing scopes...Wider scopes can be injected into smaller scopes. Everyone can get a singleton. a prototype scope can inherit a custom scope.

That should be easy to account for.

Yeah, I think I've got it.

Committed it so we can play with it tomorrow 🙂 Good night!