native

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?

PLEASE ONLY DO A SINGLE WIDGET/FILE PER PULL REQUEST.

If you want to work on this, comment here and we will put your name next to the widgets you are working on. Just comment between 1 and 3 you think you can tackle within a day or 2. Look at already completed ones for a better idea.

Background

In order to start moving the backend system towards a more "component" based system, we are wo

$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.14.6
BuildVersion:	18G9028

struct utsname name;
    if (uname(&name) == 0) {
        printf("os.name=%s\n",name.sysname);
        printf("os.version=%s\n",name.release);
    }
// os.name=Darwin
// os.version=18.7.0

Seems no way to map Darwin version to Mac OS X version.

/usr/libexec/PlistBuddy -c "Print:

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",
"

We get a lot of frequently asked questions. As such, we should look at creating a FAQ document and linking to it from the readme.

One frequently asked question is "Why am I getting the GLFW is not supported on this platform error?" and present possible solutions like ensure that the Visual C++ redistributable is installed on Windows, or switch to SDL instead by using PrioritizeSdl.

Obvious