Inspired by Silverlight; XAML engine using Javascript and rendering to the HTML5 Canvas.
The content of the DataTemplate changes slightly
<DataTemplate DataType="vm:LoginViewModel">
<ContentControl ContentUri="Views/login.fayde" />
</DataTemplate>
This is if you want to bind your ViewModel to a fayde view
Otherwise the way you have it above will work
Thanks, good to know this is possible indeed. I've been already trying it these ways:
<Application.Resources>
<DataTemplate DataType="{x:Type vms:ListItemAutomation}">
<TextBlock Text="{Binding Text}" FontWeight="Bold" />
</DataTemplate>
<DataTemplate DataType="vms:ListItemAutomation">
<TextBlock Text="{Binding Text}" FontWeight="Bold" />
</DataTemplate>
</Application.Resources>(one by one and both together;) — to no good. The type name is a bit different in web version, copypasted it from the .ts class to be sure.
The same template works if planted as ItemTemplate into the list itself.
Is ContentUri significant here?
How do I go about debugging it?
If you do not see any obvious flaws, don't waste time yet; I'll make a minimal repro tomorrow, and that would make things more illustrative. Not too polite of me asking without the full sample, sorry. Just wanted to make sure first hand that what I'm trying to do is in the design at all.
I've made a repro within the
/testsite infrastructure by adding the relevant files to the forked repo
wsick/Fayde#254
14Doing DHTML UI is kind of a trend now. But dealing with browser engine peculiarities and layouting engine quirks has been quite a burden for those who'd go into that.
14IMHO the most valuable part here could be not that it leverages XAML (which is also not bad though) but that it carries the layouting engine around in TS rather than calling into HTML, so it should be as good as ever on any HTML engine. And the layouting primitives are more closely mapped on what you'd want in the desktop or tablet style UI as compared to, say, a flexbox.
14Did you have any sketches maybe on how this could be backended in C#? This ranges widely from running in-process and making .NET objects directly available to the DHTML runtime via some interop (would say ActiveX if it were five-ten-fifteen years ago) to running a RESTlike HTTP inproc server and communicating over HTTP, and hence from almost reusing the old WPF viewmodels to writing smth specific and web-server-like. Just totally not sure which would come out the best.
fayde is all about a simple, extensible, and robust layout and rendering system
