WebSharper 4.1.1 expands and fixes multiple client-server features
Consider a very typical scenario: you have a web application that serves an SPA. The SPA itself has several "pages," each with its own client-side routed URLs (think of Gmail, for instance.) Then people copy some of these URLs from their "session" and send them to others, who in turn expect to find exactly what the sender saw. Except with most SPAs, the server-side knows nothing about the URLs generated on the client and usually throws you back to some initial SPA page. Implementing this properly requires you to share all or a subset of the URLs both on the server and on the client. With WebSharper, this is easy.
WebSharper 4.1 introduces multiple new client-server features
Full stack of `WebSharper.4.0-rc` packages are now available on NuGet.
Fixes and old and recent community requests are released
Compiler and output optimizations, auto-versioning scripts
WebSharper 4 beta now has F#4.1 and C#7 language support
Fixes for tail recursion optimizations, lighter representation of F# unions/records with no extra members
WebSharper 4 beta-6 contains updates to DOM and JQuery bindings, erased union types, JS output optimizations and fixes
One of the most fundamental design considerations any developer must deal with is handling change. In this article, we are primarily concerned with client-side state and changes to it. Change can be brought about by various external factors (user input such as mouse or keyboard events, server push messages, etc.) or by means internal to the application itself.
We started work on WebSharper 4 more than a year ago, open-sourced it in May and published first beta packages in August. It is a project with a big scope and still some features are planned before we would call it stable. This article is an introduction and also a status report.
Introducing new and improved WebSharper 4 beta features for RPCs: customizing both client and server side.
A while ago we rolled out a new UI for Try WebSharper, essentially changing it into a snappy single-page application (SPA). Among others, you can now switch between trying out various snippets and making your own without any noticable delay, no more annoying page refreshes. [more..]
This is a minor release with bug fixes and updates for dependent libraries.
Just over a year ago, last year in December we released WebSharper 3 on Apache, putting it into the hands of every F# web developer. One thing we learned from WebSharper 2 is that more frequent releases are better and this year kept the whole team busy with constant innovation and new releases. Below is a list I cherry-picked from the WebSharper blog.. [more]
This release adds a small client-side cookies library, a function to require resources in client-side markup, and various bug fixes.