Open HoraceGonzalez opened 8 years ago
Hi @Tarmil,
Has this changed or is this repository still considered experimental/incomplete?
Thanks
(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!
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 typeWebSharper.Html.Client.Pagelet
instead ofWebSharper.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.