Fabulous-new
Fabulous-new copied to clipboard
TimLariviere
Fabulous v2 - Work in progress
Based on [Reasonable goals of v2](https://github.com/TimLariviere/Fabulous-new/blob/main/docs/goals-of-v2.md), here are the things we still need to do before releasing the first part of v2. Core: - [x] #9 - [x] #11 -...
Removed the auto-incremented key and the need for `AttributeDefinitionStore` and `WidgetDefinitionStore`. Now their keys are their names, so all definitions **require** a unique name. Attributes and widgets now take a...
There are still somethings are not wrapped . Like Effects, Behaviours, VisualStateManagers, TemplatedView , TemplatedPages, StyleWidgets. Would be good to create a separate issue for all them so we can...
We can enable all the animation methods in : https://docs.microsoft.com/en-us/dotnet/api/xamarin.forms.viewextensions?view=xamarin-forms - [x] ScaleTo - [ ] RelScaleTo - [x] ScaleXTo - [x] ScaleYTo - [x] RotateTo - [ ] RelRotateTo...
In V1 we have some testing helper functions ie findViewElement and the ElementViewers to make the view and Widgets testable . https://fsprojects.github.io/Fabulous/Fabulous.XamarinForms/dev-testing.html Are we doing the same for V2 ?
This will allow us to reduce the use of ViewRef or the need to match against the platform : iOS : https://docs.microsoft.com/en-us/dotnet/api/xamarin.forms.platformconfiguration.iosspecific?view=xamarin-forms Droid : https://docs.microsoft.com/en-us/dotnet/api/xamarin.forms.platformconfiguration.androidspecific.appcompat?view=xamarin-forms
## RelativeToView is missing from v1 and V2 . Would be good to see if there is anyway we can support this as we move forward to stable 2.0 ```csharp...
Would be good if we can add support for XML documentation Add Extension https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/xml-documentation#recommended-tags. This will make really easy to use