Open ghost opened 7 years ago
That's not really the scope of the xaml standard. It's goal is to unify the xaml needed to accomplish a certain feature, not render xaml into something else.
Hi Morten,
But that's what's wrong with XAML as it stands today. MS and the community need to make it portable. Go back to the WinForms and WebForms days - just two platforms. Wouldn't it have been good with a portable language and one UI stack? But now MS are chasing their tail in getting something that's 'just' common on the native side. I think efforts need to go further.
Best. Rod
On Tue, Sep 5, 2017 at 12:20 AM, Morten Nielsen notifications@github.com wrote:
That's not really the scope of the xaml standard. It's goal is to unity the xaml needed to accomplish a certain feature, not render xaml into something else.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Microsoft/xaml-standard/issues/207#issuecomment-327038283, or mute the thread https://github.com/notifications/unsubscribe-auth/AeK4i65gO2GXyp2_mT9xyuylF9ompdFsks5sfIWfgaJpZM4PMSVH .
I think Xaml's future is as an HTML/Browser-app killer. Think about how great it would be to have "web apps" be relegated to where they belong - enhanced web pages providing some additional functionality beyond static content. Native apps, with all of their inherent advantages in performance, functionality, and aesthetics, would once again rule. Ahhh, if only...
@LazyGepid is HTML really likely to be slower than BAML? XBAP's have been tried before. And HTML can be accessed natively via Cordova - but wouldn't things be nicer with C# instead of javascript? Enter WebAssembly?
@rodmac1 Someone is completely free to write a tool that can convert XAML to HTML (whether it be Microsoft or not). That someone can then say that they support all the XAML that is included in the XAML Standard. But this repo is not about writing such a tool, but just establishing that a text block is called a TextBlock
, has a string
property called Text
etc..
like this: http://cshtml5.com
It's the sort of 'embrace and extend' MS used to do and need to do today. Enter Anders H?
We've done this for our Visualisation wich is based on loose XAML and SharpDevelop Designer (https://github.com/icsharpcode/WpfDesigner). We use Polymer as HTML Library, and create a Html Element for each XAML Control we like to support! It's not yet perfect, but workin very well...
like this: http://cshtml5.com It's the sort of 'embrace and extend' MS used to do and need to do today. Enter Anders H?
If the Standard can be kept focused on defining the markup than others and/or Microsoft can make the presentation/visualization renderers to the target platform desired. For Android Android and iOS this for now Xamarin, HTML with XAML for HTML for example but there are also others. And maybe in the future there will be a unified thing for all, but for it to be possible the markup should be properly defined.
see that this discussion is similar to this one https://github.com/Microsoft/xaml-standard/issues/57#issuecomment-329935808
You can write your own converter from XAML to HTML but this has following problems:
Grid
and StackPanel
need either native support or additional wrapper. What happens when you want to use a new layout like DockPanel
or CarouselPanel
.A quick search on Google found a project called x2h, which might be of interest to you.
I started this in my free time: https://github.com/XamlEngine/Samples Example: http://www.xamlengine.com
It's rendering Xaml natively in the browser using WebAssembly & WebGL. It exposes the Xaml to any language that can run in the browser/WebAssembly.
Anyone want to help build it?
Can I please suggest that:
1) in its lightest weight state (fewest APIs), XAML can be compiled into HTML and vice versa, thus creating true portability in development. I want to take my iOS/Android/Windows app and render if for the web also. 2) XAML standard is made 'origami' style so that apps can be expanded from icons/tiles, in stages, according to local device APIs and screen estate. Foldable apps if you will.