Following the discussion we had (@dmarcos, @ngokevin) about it last week...
The current structure is:
{
"collider" : {
"author": "Diego Marcos",
"description": "Triggers events when object collide",
"url": "https://rawgit.com/dmarcos/a-invaders/31f5a7/js/components/collider.js"
},
"explode" : {
"author": "Diego Marcos",
"description": "Makes the geometry explode",
"url": "https://rawgit.com/dmarcos/a-invaders/31f5a7/js/components/explode.js"
},
"spawner" : {
"author": "Diego Marcos",
"description": "Spawns an entity on an event",
"url": "https://rawgit.com/dmarcos/a-invaders/31f5a7/js/components/spawner.js"
}
}
Add some new parameters:
help_url: (optional) It will be used in the help button next to the inspector's sidebar.
screenshot_url: (optional) It will be shown in component list in the "add new component" modal dialog.
url: (mandatory) pairs of version and url: {"0.3.0": "http://blabla", "0.4.0": "http://blabla4"}
schema_grouping: (optional): If defined it will be used to group and sort the parameters on the inspector UI as proposed on https://github.com/aframevr/aframe-inspector/issues/303. We could even force to hide the parameters from the schema not defined in this grouping, we could get easily get rid of parameters like mergeTo or similar.
With the changes proposed the JSON could looks like the following:
Following the discussion we had (@dmarcos, @ngokevin) about it last week...
The current structure is:
Add some new parameters:
version
andurl
:{"0.3.0": "http://blabla", "0.4.0": "http://blabla4"}
mergeTo
or similar.With the changes proposed the JSON could looks like the following: