search

aframevr / aframe-inspector

:mag: Visual inspector tool for A-Frame. Hit *<ctrl> + <alt> + i* on any A-Frame scene.
https://aframe.io/aframe-inspector/examples/
MIT License
655 stars 203 forks source link

Added basic component-registry loader #325

Closed fernandojsg closed 8 years ago

fernandojsg commented 8 years ago

Based on the latest changes from https://github.com/aframevr/aframe-registry

screen shot 2016-09-25 at 16 14 16
fernandojsg commented 8 years ago

I'm not sure about which name to use for grouping the components. At first I thought about "core" and "registry/community" but if they user already has some custom components loaded they'll appear on "core" too as it shows really the names of the components already loaded. Any thoughts on that @ngokevin ?

ngokevin commented 8 years ago

For now, it could just be registered + community or registry.

Though you can also check components against the registry to determine whether or not they are core, developer-registered, or community.

But not too important since the dropdown is just temporary right?

fernandojsg commented 8 years ago

I've just changed it to registered + registry. The dropdown as it's right now it will be just temporary but still we'll have a autocomplete dropdown where you can access these components, as discussed on https://github.com/aframevr/aframe-inspector/issues/317: https://cloud.githubusercontent.com/assets/782511/17860914/6b424410-688f-11e6-9c73-b27bc81d59af.gif

Next to this dropdown you'll have a components button that will popup the big dialog similar to Unity's store. You'll use that dialog when you want to know more info about a component, or when you want to discover new components as it will show some descriptions, links to author/components, tags, and so on. But still we want to keep the autocomplete-dropdown as it's faster to include already known and commonly used components such as geometry, material and so on.