search

reactiveui / Sextant

A ReactiveUI navigation library for Xamarin.Forms
MIT License
158 stars 26 forks source link

feature: Add support to Shell #53

Open giusepe opened 5 years ago

giusepe commented 5 years ago

Is your feature request related to a problem? Please describe.

Currently Sextant don't support Xamarin.Forms.Shell and neither does shell support any MVVM Framework.

Describe the solution you'd like

Once a solution is born from this issue: https://github.com/xamarin/Xamarin.Forms/issues/5166 I suggest to discuss this with the Xamarin team to see how we can make our life easier.

Describe alternatives you've considered

Describe suggestions on how to achieve the feature

Additional context

AFAIK they are still working on a specification and that should be share soon, so let's be ready to participate.

open-collective-bot[bot] commented 5 years ago

Hey @giusepe :wave:,

Thank you for opening an issue. We will get back to you as soon as we can. Also, check out our Open Collective and consider backing us.

https://opencollective.com/reactiveui

PS.: We offer priority support for all backers. Don't forget to add priority label when you start backing us :smile:

ReactiveUI - Open Collective
An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms!
jecarlos14 commented 4 years ago

Any update for this @RLittlesII ?

glennawatson commented 4 years ago

It's not happening anytime soon due to issues on the Microsoft time. There's a reason why prism etc haven't done it either.

There is currently some work the Xamarin.Forms team is doing to support MVVM with Shell. Last I was told that work is being tracked here xamarin/Xamarin.Forms#5166

RLittlesII commented 4 years ago

@jeanberrocalGL As stated in the body of the issue, there is work the Xamarin.Forms team has to do in order to make this feature possible. I have seen some of the work towards that end, and I have seen some of the extension points. I have not gone down the road of attempting an implementation because as I see it the entire API surface may have to change just to support Shell.