Features for next major version

Question

Features for next major version

edongashi opened this issue 6 years ago · 4 comments

edongashi commented 6 years ago

Remove dependency on Material Design in XAML and Mahapps.Metro. Create respective packages Forge.Forms.Material and Forge.Forms.Metro. This means that Show.Dialog and Show.Window and other utilities won't be part of the core library.
Target .NET Core 3 WPF - no idea yet how this will work.
Remove humanizer dependency - handle sentence parser manually.
Create abstract Form DOM. This dom can be serialized to XML, XAML, Classes, and custom visitors. This dom can be built from XML, Classes, fluent API. Currently FormElement is too brittle for that.
First class XML parser - generalize FormBuilder.
Make it easier to attach custom controls - placeholders, data templates and data template selectors, return FrameworkElements directly.
Better support for plugins.
First class collections support - easy and intuitive API with in-depth customization.
Nested forms support.

Other suggestions are welcome.

Answer 1 · 2019-01-22T18:39:20.000Z

.NET Core 3 port available at https://github.com/WPF-Forge/Forge.Forms/tree/net3

Answer 2 · 2019-01-23T17:06:27.000Z

Is it possible to reference .NET framework dependencies (for example NuGet) from a .NET core 3 WPF app?

Answer 3 · 2019-01-23T17:07:19.000Z

Yup, it uses wichever version is available for .NET 4.6.1 or beyond, just like .NET Core. Except for some specific cases, such as System.Drawings

Answer 4 · 2019-01-23T17:16:11.000Z

That certainly makes migration easier. We will see how it plays out once it's released. By then we will probably get rid of all dependencies from core library anyway.