Factoring out reusable JS compiler

Dec 15, 2007 at 7:16 PM
The current code-base is very much tied to the web forms life cycle it seems. Whilst this has its uses, I would like to use the F# to JS and server/client workflow model in different ways. For example, I am wanting to make a Model from the MVP pattern that runs on both client and server. The overall idea is to sepearate all business logic from the UI. It is conceivable to make a Model object that can run Silverlight <--> Full .NET as well as JS <--> Full .NET.

I think the winning feature of F# web tools is the workflow syntax. I've been looking at various client-server technologies. So far nothing has made the programming model seemless enough. Even Volta seems to suffer from the clunkiness of manual async callback coding.

Hmm, now there's an idea... Why not target Volta with the async workflow pattern?
Dec 16, 2007 at 8:33 AM
Another approach to consider is to follow Script# by having a "Scriptlet" ASP.NET control that is dropped on a web form.
This control then references F# types that are to be expressed as JavaScript.