-
-
Notifications
You must be signed in to change notification settings - Fork 39
MAUI support #289
Comments
@BerndStoltefuss actually I was not aware of a Maui port for the Popup Plugin... it is something I will take a look at after the next Prism.Maui release which adds .NET 7 support. Also to be clear it will only support Popups for Dialogs. The Navigation Service in Prism.Plugin.Popups is legacy at this point and you should only be using it for Dialogs anyway |
@dansiegel thanks for the quick response. But i am not sure i understand your "will only support Popups for Dialogs". We currently have a bunch of pages (f.e. DetailViews or views to enter or select something) which are implemented as PopupPage and are navigated to by using NavigateAsync(page, params, modal=true). So the "main/master" view is still visible behind it. That's the same way as in your current sample/MainPageViewModel and the only way i was aware of using the current version of your plugin. |
When the popup plugin was first introduced that was what we needed to do. Popup Pages aren't really pages at all they are dialogs. While I have kept the Navigation Service around for legacy support you should be migrating to use Popup Pages as Dialogs. |
Hmm. So to replicate the old navigation behaviour and regarding to your answers here (https://stackoverflow.com/questions/63801160/difference-between-prism-dialogs-vs-popup) i should be able to drop Rg.Plugin.Popups at all and just use a modal page with transparent background instead? If this is possible it would be my prefered way as i could get rid of 2 dependencies when porting to MAUI (or even before when using Prism 8 according to your post) Rg.Plugin.Popups(Mopups for MAUI) would only be needed when a) we need animations or b) for some strange reason need to popup something outside the navigation stack. Correct? The other way would be to use "popup pages as dialogs" as suggested, resulting in a view which is not part of the navigation stack (this could be an advantage or disadvantage depending on the situation) and is not stackable(or are dialogs stackable as well? We have some detail views which might display dialogs (warnings etc). itself)). Correct? Sorry for the questions but we have until now only used prisms dialog service to display simple messages or yes/no questions and not for something like detail views. |
Any update on this topic @dansiegel? |
FYI: for the maui port of our product i replaced the RG.Popup/Mopup stuff with modal pages (using transparent background). No problems so far and i got rid of two dependencies on one/two men projects ,-) Still looking forward for dialogs in Prism.Maui, as they could be a good replacement at some places where true navigation is not necessary. |
Guys, after researching the source code of Prism NavigationService, and fiddling with hours, I came out with a service to navigate mopup pages similarly to Prism on MAUI. My codes aren't perfect, but it works well for me. It would be very helpful if someone can fine tune the code for me.
|
Popup Support for .NET MAUI will only be available to Commercial Plus license holders. No further releases will be made for Xamarin.Forms. |
Hi,
will this plugin be updated to support the new MAUI implementation of Rg.Plugins.Popups named Mopups (https://github.com/LuckyDucko/Mopups) and the MAUI implementation of Prism itself?
Or do you recommend a different solution for popups in MAUI (f.e. from CommunityToolkit)?
Thanks,
Bernd
The text was updated successfully, but these errors were encountered: