[study] refactor: make EngineLines independent of AnalysisController

[tom-anders]

We'll want to reuse it for the study screen. It's easiest to remove the dependency from the widget for now (alternative would be to use an interface that both AnalysisController and StudyController derive from, but as discussed we won't do that for now)

[veloce]

I have now an example of Notifier mixin:

mobile/lib/src/model/settings/preferences_storage.dart

Line 15 in ef9fc55

mixin PreferencesStorage<T extends SerializablePreferences> {

We might eventually use this approach to share engine logic in different controllers. I'm not sure but I suspect it is not that easy to do.

[tom-anders]

I have now an example of Notifier mixin:

mobile/lib/src/model/settings/preferences_storage.dart

Line 15 in ef9fc55

mixin PreferencesStorage<T extends SerializablePreferences> {

We might eventually use this approach to share engine logic in different controllers. I'm not sure but I suspect it is not that easy to do.

Ah that sounds very useful indeed, I'll see if I can use it in the study branch.

But I think for now it's safer to go with the callbacks, we can always refactor again later.