reactiveui / reactiveui/Sextant
viewmodel based navigation as first class citzen for all platforms
@RLittlesII is already working on this.
Since Sep 1, 2018.
- Dominant language
- C#
- Stars
- 161
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Our routing is something that should be overhauled in the future. It is far too prescriptive and platform-specific. ReactiveUI should really provide a general routing mechanism that cares not about how you manifest it in the view. All that logic should be written _once_ (instead of per platform like we have now) and shared with simple shims to integrate at the UI level.
This is a great opportunity to look around and see how others are doing it. @rid00z has mentioned over beers he has suggestions from implementing this type of logic as part of his framework FreshMvvm.
Additionally MvvmCross has the notion of handling this behavior via Presenters
- http://gregshackles.com/presenters-in-mvvmcross-a-primer/
- http://gregshackles.com/presenters-in-mvvmcross-navigating-android-with-fragments/
@jcmm33's team has done a significant amount of work on-top of ReactiveUI and have implemented their own presenter solution. Maybe this is a chance to use this implementation as the golden standard and off-load the burden from his team of having to maintain their own.
Suggested leads for this topic are @jcmm33, @rid00z, @codemillmatt and of course @kentcb / @flagbug
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.