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

I'm sorry, I can't find any relevant example in the spec, do you mean [this one](http://www.w3.org/TR/appmanifest/#example-manifests)? (I only see the standard members defined in point 8).

My extension points would be:

- Frames per second (two different fields, one for the rendering and one for the game loop)
- The screen resolution at which the game is rendered
- Some string arrays indicating files that deserve special treatment (level files, game code files, spritesheet files).
- A capabilities member to specify which features of the engine does the game use
- A dependencies member to specify which external modules does the game use

so ideally the manifest would end up looking something like this: 

```
{
    "name": "Pong",
    "scope": "gameFiles",
    "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"
    ],
    "themeColor": "#4B5",
    "backgroundColor": "#000",
    "tileIcon": "tileIcon.png",
    "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-287652523