+1, would make things a lot cleaner if the two client-side APIs could merged. Having Piglets implemented in UI.Next would be a good starting point.

By on 7/14/2015 12:13 PM ()

Some news since last week: we started merging UI.Next and Html.Client, and Html.Server (!) - so all three languages into a single reactive language. You can check the bridge branches of UI.Next and WebSharper for more details. If this experiment turns out well, this unified language will become the standard WebSharper notation for HTML.

By on 7/14/2015 3:33 PM ()

As for UI.Next - I'd recommend you try it first in its own context (so not mixing it with WebSharper.Html.Client), e.g. using the UI.Next template from the installer. UI.Next has great templating, reactive DOM and dataflow support.

By on 7/5/2015 7:28 AM ()

WebSharper.Html.Server is for server-side HTML, WebSharper.Html.Client and WebSharper.UI.Next are for client-side HTML.

If you have name clashes between server and client, that's a sign that you need to better separate them, say into separate modules and open the right namespace in each.

That said, UI.Next and WebSharper.Html.Client are two different languages for client-side HTML. Unifying these would be nice indeed, and will happens sooner or later.

By on 7/5/2015 7:23 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper