Re: [w3c/manifest] Extending the manifest with 'vendor-specific' properties (#560)

I saw point 15 but I somehow missed point 15.1😅 That indeed covers my use case, thanks for your help!

Instead of adding a configuration file, I was thinking about adding a single proprietary manifest member which has an object with all the configuration at its value (that way I would still keep the number of additional members at one), something like this:

```
 {
    "name": "Pong",
    "scope": "gameFiles",
    "theme_color": "#4B5",
    "background_color": "#000",
    "icons": ... ,
    "clockwork":{
        "components": [
            "components.js"
        ],
        "levels": [
            "levels.xml"
        ],
        "spritesheets": [
            "spritesheets.xml"
        ],
        "screenResolution": {
            "w": 320,
            "h": 200
        },
        "dependencies": {
            "keyboard": "1.0",
            "gamepad": "1.0",
            "pointBoxCollision2D": "1.0"
        },
        "capabilities": [
            "ClockworkRuntime"
        ],
        "enginefps": 60,
        "animationfps": 60
    }
}
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/560#issuecomment-287653739

Received on Sunday, 19 March 2017 22:37:16 UTC