AwaitablePopups 1.1.2
See the version list below for details.
dotnet add package AwaitablePopups --version 1.1.2
NuGet\Install-Package AwaitablePopups -Version 1.1.2
<PackageReference Include="AwaitablePopups" Version="1.1.2" />
paket add AwaitablePopups --version 1.1.2
#r "nuget: AwaitablePopups, 1.1.2"
// Install AwaitablePopups as a Cake Addin #addin nuget:?package=AwaitablePopups&version=1.1.2 // Install AwaitablePopups as a Cake Tool #tool nuget:?package=AwaitablePopups&version=1.1.2
<br /> <p align="center"> <h1 align="center">Awaitable Popups</h3> <p align="center"> Customisable Popups for Xamarin Forms <br /> </p> </p>
Table of Contents
Codacy NuGet CodeFactor Fuget (Use Fuget to see API differences between each package.)
https://www.fuget.org/packages/AwaitablePopups/badges
About The Project
Awaitable Popups is a neat blend of the Rg.Plugins.Popup and AsyncAwaitBestPractices plugins to bring you a quick way to add popups into your Xamarin Forms App using familiar concepts
Built With
Getting Started
First, you must follow the initialisation guide set out by Rg.Plugins.Popup, once you have that, have a look at usage down below
Installation
You can install the nuget by looking up 'AwaitablePopups' in your nuget package manager, or by getting it here
Usage
here is an example of what this plugin makes easy (Looks slow due to giphy)
New Example
To Use the plugin for its inbuilt popup pages in a basic setting (Dual/Single Response, Login, TextInput EntryInput,and loader.) All you need are these one liners
SingleResponse Popup Page
return await SingleResponseViewModel.AutoGenerateBasicPopup(Color.HotPink, Color.Black, "I Accept", Color.Gray, "Good Job, enjoy this single response example", "thumbsup.png");
DualResponse Popup Page
return await DualResponseViewModel.AutoGenerateBasicPopup(Color.WhiteSmoke, Color.Red, "Okay", Color.WhiteSmoke, Color.Green, "Looks Good!", Color.DimGray, "This is an example of a dual response popup page", "thumbsup.png");
Loader Popup Page
await PopupService.WrapTaskInLoader(Task.Delay(10000), Color.Blue, Color.White, LoadingReasons(), Color.Black);
Text Input PopupPage
await TextInputViewModel.AutoGenerateBasicPopup(Color.WhiteSmoke, Color.Red, "Cancel", Color.WhiteSmoke, Color.Green, "Submit", Color.DimGray, "Text input Example", string.Empty);
Entry Input PopupPage
await EntryInputViewModel.AutoGenerateBasicPopup(Color.WhiteSmoke, Color.Red, "Cancel", Color.WhiteSmoke, Color.Green, "Submit", Color.DimGray, "Text input Example", string.Empty);
LoginPage PopupPage
var (username, password) = await LoginViewModel.AutoGenerateBasicPopup(Color.WhiteSmoke, Color.Red, "Cancel", Color.WhiteSmoke, Color.Green, "Submit", Color.DimGray, string.Empty, "Username Here", string.Empty, "Password here", "thumbsup.png", 0, 0);
or, to return from the loader a value
await PopupService.WrapReturnableTaskInLoader<bool>(IndepthCheckAgainstDatabase(), Color.Blue, Color.White, LoadingReasons(), Color.Black);
you can also add in synchronous functions, however they are wrapped in a task
private bool LongRunningFunction(int millisecondDelay)
{
Thread.Sleep(millisecondDelay);
return true;
}
await PopupService.WrapReturnableFuncInLoader(LongRunningFunction, 6000, Color.Blue, Color.White, LoadingReasons(), Color.Black);
That's it! for advanced usage read on
In Version 1.1.0, AwaitablePopups will be starting on a new set of API's
This set of API's will be used for when the basic API wont cut it, without relying on me making another overload for every situation under the sun.
This API introduces
GeneratePopup<TPopupPage>
Which allows you to supply your own popuppage xaml which will then be attached to whatever VM you called it from.
GeneratePopup(Dictionary<string, object> propertyDictionary)
Which allows you have a dictionary of values that a popup uses, pass and automatically attach to the appropriate properties on the VM side
These are both non-static. and require you to have an instance of the ViewModel to work with. Hence
<ViewModelClassNameHere>.GenerateVM()
Which provides you with a new instance of that VM
<ViewModelClassNameHere>.PullViewModelProperties()
Which collects all the properties of a VM, and provides them to you in a dictionary, so you can reuse and also while debugging, check what exists/whats been changed
Returns this Dictionary<string, (object property, Type propertyType)>
However, for initialisation, i internally (and you can use) the following function
<ViewModelClassNameHere>.InitialiseOptionalProperties(Dictionary<string, object> optionalProperties)
Which will attempt to set each of the viewmodel properties with the corrosponding value in the dictionary
So, to fix that, i provide
<ViewModelClassNameHere>.FinalisePreparedProperties(Dictionary<string, (object property, Type propertyType)> viewModelProperties)
Which takes in the Dictionary<string, (object property, Type propertyType)>
and creates Dictionary<string, object> optionalProperties
Hopefully i will add on to make this easier in the future
If you want to make your own Popup Page
This is the real power of this Plugin (Thanks in no small amount to Rotorgames amazing plugin). If you look at the source for DualResponsePopupPage, or the SingleResponse version you'll notice that they are just simple Xaml Pages. Nothing fancy. (except for the rg popup spice).
You can create the full thing yourself
- Create Xaml Page with codebehind
- Create your ViewModel that is associated with the popup, lets call ours
InformationPopupPage
- Ensure your ViewModel inherits from
PopupViewModel<TReturnable>
whereTReturnable
is what you want the popuppage to return to its caller - Ensure that your xaml page codebehind inherits from
PopupPage
(requirement to use rg plugins popup) andIGenericViewModel<TViewModel>
whereTViewModel
is your Viewmodel, in our case it will beIGenericViewModel<InformationPopupPage>
- You're ready to start using it the same as
DualResponsePopupPage
New API Usage (1.1.0)
or you can provide your own Xaml Page, with a codebehind that inherits from PopupPage
and IGenericViewModel<TViewModel>
where TViewModel
is the plugin provided VM you wish to use.
to use this version, just call TViewModel.GeneratePopup<YourXamlPopupPage>()
License
This project uses the MIT License
Contact
My Github, or reach me on the Xamarin Slack, or on my E-mail
Project Link: AwaitablePopups
Acknowledgements
- Brimmick has been a model to follow
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- AsyncAwaitBestPractices.MVVM (>= 4.2.0)
- Rg.Plugins.Popup (>= 2.0.0.3)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated | |
---|---|---|---|
1.1.5 | 2,167 | 1/13/2021 | |
1.1.4 | 838 | 8/26/2020 | |
1.1.3 | 454 | 8/24/2020 | |
1.1.2 | 476 | 8/20/2020 | |
1.1.1-rc | 407 | 8/18/2020 | |
1.1.0 | 469 | 8/7/2020 | |
1.0.2 | 537 | 7/21/2020 | |
1.0.1 | 502 | 7/3/2020 | |
1.0.0 | 596 | 7/1/2020 | |
0.3.8 | 616 | 6/8/2020 | |
0.3.5 | 646 | 5/4/2020 | |
0.3.4 | 607 | 4/20/2020 | |
0.3.3 | 785 | 4/20/2020 | |
0.3.1 | 787 | 4/20/2020 | |
0.3.1-Alpha | 652 | 4/17/2020 | |
0.3.0 | 738 | 3/24/2020 | |
0.2.5 | 1,073 | 3/23/2020 | |
0.2.4 | 1,111 | 3/23/2020 | |
0.2.3 | 1,121 | 3/23/2020 | |
0.2.1 | 1,119 | 3/23/2020 | |
0.2.0 | 1,016 | 3/20/2020 | |
0.1.9 | 1,235 | 3/20/2020 | |
0.1.8 | 950 | 3/11/2020 | |
0.1.7 | 945 | 3/9/2020 | |
0.1.6 | 1,064 | 2/24/2020 | |
0.1.5 | 1,079 | 2/10/2020 | |
0.1.3 | 1,657 | 1/31/2020 | |
0.1.2 | 1,412 | 1/31/2020 |
Added in fixes to GitHub Issues
1. Added ability to generate a popuppage without the need for any constructor
2. fixed bug where custom popuppages werent attached properly
3. Added the ability to use something that implements a viewmodels propertyinterface to be used in generating the viewmodel
4. Added in a fix where exceptions arised from PopAsync can either be ignored (default) or dealt with (action required)