dotnet-websharper / ui.formlets

A terse and composable form abstraction for the web
Apache License 2.0
1 stars 5 forks source link

What's the Difference between this Repo and websharper.formlets? #3

Open HoraceGonzalez opened 8 years ago

Tarmil commented 8 years ago

WebSharper.Formlets is based on IntelliFactory.Reactive, rather than UI.Next. IF.Reactive is a more imperative reactive library, with explicit subscribe/unsubscribe, akin to RX. So it doesn't have bridges to UI.Next such as Controls.InputVar here, and produces markup of type WebSharper.Html.Client.Pagelet instead of WebSharper.UI.Next.Doc.

On the other hand, while both WS.Formlets and UI.Next are production ready, UI.Next.Formlets is still quite experimental and incomplete.

gilbertbw commented 5 years ago

Hi @Tarmil,

Has this changed or is this repository still considered experimental/incomplete?

Thanks

granicz commented 5 years ago

(Reactive) formlets are still incomplete and will likely stay so, mostly because (reactive) piglets, aka. WebSharper Forms) are more flexible and just plain better. They can be bound to external HTML templates or inline HTML via a Render function, instead of a hardwired view representation that formlets offer. This makes them slightly more verbose, but they work better for the vast majority of cases that I encountered. If you have a compelling use case or need to continue supporting formlets, feel free to describe it here and let's figure out what to do, thanks!