Provide nested key and scoped key built on top of service-tree with general-purpose scoped service manager (2.0) about simple-stack HOT 9 CLOSED

That's funny, if I did that, I could add hierarchical back navigation down to the view (and not just the their backstacks), but only if I bind "controllers" into the tree...

from simple-stack.

Clearly the user needs to bind their presenter into the tree in bindServices(), for example addService(Navigator.BACK_HANDLER, presenter).

from simple-stack.

Navigator and BackstackDelegate must handle this.

from simple-stack.

Consider the fact that Activities and Fragments have first-class support for this using ViewModel.

from simple-stack.

Consider a glance to lyft/scoop to see how they've set this stuff up.

Technically this is just "first-class" ServiceTree integration, most of the work is already done in mortar-sample....

from simple-stack.

I probably have to hack it into the backstackManager instead, that way it's easy to create backstack managers per node.

But what makes it tricky is that Context should expose Services, but that would require stateChange to know about the BackstackManager, or at least the Node needs to be exposed to getSystemService. How?

from simple-stack.

The only way to get it into the context wrapper is if the Backstack does it. But can it truly be so general purpose that this addition even makes sense?

from simple-stack.

Maybe if I read https://github.com/lyft/scoop#scoops enough times I'll eventually figure it out.

from simple-stack.

It's really just something the state changer should handle.

from simple-stack.