robmikh

#include <unknwn.h>
#include <winrt/base.h>
#include <d3d11_4.h>
#include <filesystem>
#include <fstream>
#include <sstream>
#include <string>
#include <vector>
#include <robmikh.common/d3dHelpers.h>

robmikh

using Microsoft.Graphics.Canvas;
using Microsoft.Graphics.Canvas.Svg;
using Microsoft.Graphics.Canvas.UI.Composition;
using Robmikh.CompositionSurfaceFactory;
using System;
using System.Threading.Tasks;
using Windows.Foundation;
using Windows.Graphics.DirectX;
using Windows.Storage;
using Windows.UI;

robmikh

Compositor _compositor;
SurfaceFactory _surfaceFactory;
CompositionEffectFactory _effectFactory;

SpriteVisual _visual;
TextSurface _textSurface;
CompositionDrawingSurface _colorSurface;


_compositor = new Compositor();

robmikh

So you can write an app using XAML, WinJS, and DirectX. But is there another option? There is! And it's actually what all of the other more traditional options do under the covers. At the end of the day, some Composition content needs to be hooked up to a CoreWindow. The first step is to create a main function that will start our CoreApplication:

static int Main(string[] args)
{
    CoreApplication.Run(/* Some IFrameworkViewSource here */);

    return 0;
}

robmikh

using System;
using System.Collections.Generic;
using System.Collections.ObjectModel;
using System.Linq;
using System.Runtime.InteropServices.WindowsRuntime;
using Windows.UI.Composition;
using Windows.UI.Xaml;
using Windows.UI.Xaml.Controls;
using Windows.UI.Xaml.Data;
using Windows.UI.Xaml.Documents;

robmikh

using Robmikh.Util.CompositionImageLoader;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using Windows.UI.Composition;
using Windows.UI.Xaml;
using Windows.UI.Xaml.Hosting;

robmikh

public sealed partial class MainPage : Page
{
  public MainPage()
  {
    this.InitializeComponent();

    InitComposition();
  }

  //