Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g. ~x=..., ~y=....

What do you others think?

When porting tests from Scala.js to Scala Native and also creating new tests, developers have been using the following package by just changing the org in the package name:

package org.scalanative.testsuite.javalib...

Initially when the ability to run the tests against the JVM, they were changed to the following for example to avoid using the java package name:

packag

When use "$: react-native dom"
Appears:
No version of 'react-native-dom' found that satisfies a peer dependency on 'react-native@0.56.0'

This is my package.json:

{
"name": "dom",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start",
"test": "jest"
},
"dependencies": {
"react": "16.4.1",
"

Summary

#619 pointed out that we currently have zero resources demonstrating our Assimp bindings, and because Assimp is usually used with C++ there aren't many resources for the C API which we bind to as is.

We should make a demo model loader using Silk.NET.OpenGL and Silk.NET.Assimp.

In my eyes, this looks like:

• An ImGui interface allowing you to paste in a file path and load a 3D