Hi Trevor, many thanks for additional info, will be helpful.
but unfortunately, most probably I will not take ways you offered. no one in my company is interested to support to finish silverlight or subset of wpf port to javascript, and there is too much on my plate so that I could hope to finish anything really big in foreseeable future by my spare time efforts. my immediate needs are just to render some xaml in games, because xaml is great as it is compatible with xps documents, and it is much easier to add different interaction capabilities to xaml ( xps ) printed documents ( my interest is to have interactive educational programs with a lot of typographic text with input fileds ), than to pdf. Thus my thoughts due to experience with text games to train people to fill in certrain documents ( I made them in silverlight now think to make it in emscripten after I know the task is feasible ). but maybe if/when I finish even basic xaml rendering via emscripten,base on what I will learn from webkit port, others will catch the ball and will extend this. What I will try to do though, I will let know to those who is heavily involved into C#/xaml that currently it is possible to move along the ways you mentioned and have a lot of ready wpf/silverlight to run on the web. Because now idea to silverlight/wpf via javascript looks quite implementable, and many people might be really keen to finish the task. Best regards Sergey On Tue, Jun 24, 2014 at 4:39 AM, Trevor Linton <[email protected]> wrote: > *Sergey--* > > Certainly there's a few odds and ends that need to be corrected on Cairo, > you can find the commits in the webkit.js folder, mostly around dealing > with cairo's, uhm, "eager" use of casting function signatures. In addition > XML parsing is fairly straight forward. In all honesty it would be > interesting to see a C# runtime compiled down into a javascript asm.js > loop. I'm unsure what additional efforts there would be beyond that but I > know of quite a few projects that would benefit from it (including > Microsoft's own). > > I wonder if like SVG, you could write its own layout document/style tree > for XAML, then add in IDL bindings that instead of javascript could > integrate more elegantly into a C# compiled down javascript reduction. I > only say this as you'd save yourself some headaches implementing things > such as resource fetching, compositing, hi-dpi support and all of the other > anxilary pain in the butt features. You effectively could just fork > webkit.js and start adding in a new style parsing tree similar to SVG then > change the compiler to simply not include the HTML/CSS/SVG tree. Just a > thought... > > - Trevor > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
