After exiting from editor.

Similar to #7

1. Create an <a-entity>
2. Set position to 2.00 2.00 2.00.
3. Set rotation to 0.01 0.00 0.00.
4. Notice position has changed to 2.00 2.00 0.00 and rotation to 0.0 0.00 0.00.

I noticed a ton of weirdness such as with this. And now when I did it again, the rotation Z value became 0.02. Weird!

Probably something like a wireframe speaker

1. I was surprised to learn that "Create" meant add items to my scene graph.
2. Can we have an "+ Add" button in the scene graph sidebar (perhaps flush left of the trash can)?

If the Editor is opened and no form field or anything is focussed, perhaps just pressing Esc or e or whatever should dismiss the Editor.

And when I'm in non-Editor mode, I should be able to easily invoke the Editor by pressing option + e or something (again, when only document.activeElement is not a form field, contexteditable, etc.).

can we tagName.toLowerCase()?

I'd like to move one entity to be nested within another entity. Or I'd like to just rearrange or group my entities.

The camera lines are persistent and extend across the scene so there's some noise

To have a distributable version

I removed a component by mistake and I cried.

https://davidwalsh.name/html5-context-menu

They've been in Firefox for quite some time now. Coming soon to the other browsers.

using title (and alt) - or use custom tooltips if you'd like

Implement common DCC 2D cameras: Top, Front & Right + Isometric.
As we're not going to use this cameras for a-frame I don't see the point on creating a component for ortho2d in aframe having already a perspective camera. I think we should just use THREE.OrthographicCamera directly.

Definitely could come later, but it'd be nice if there was some (?) help icon or something that could link me to the docs to learn about it.

I know it's like this in the mocks, but because there are no borders around the numbers, they look readonly. Especially since Type: A-ENTITY actually is read only.

to make things easy, you could have a radio form field for each item

I don't see anything in Denys' mocks. Will this "Edit" drop-down menu be used for something?

if right now, all we have is "Save to HTML" and "Copy to clipboard" - can we pull those out of a drop-down menu and make them more visible? We have the horizontal real estate.

It would be super useful to be able to clone a entity.

Not sure if this is expected? Or if you should be able to edit the cursor as part of the controls?

The camera one is obvious, but the rest are really hard to understand. I think we could probably do away with them if the components are already present in the attributes panel and just rely on entity labeling/ID.

The editing camera is locked around the scene origin. It's hard to edit anything in detail without being able to pan around when zoomed in.

I just clicked on the field for the rotation X value, and it changed to -0.02 because I must've dragged my mouse a bit on mousedown.

Otherwise, the footer with the delete action buttons, etc. can be hidden from the view:

When entering transform values by typing (using numeric keys), the entity does not take on these changes.

Seems to work fine when you click and drag the numbers.

It'd be nice to see how my scene is changing as I move the camera, for example. The editor wireframe view is nice, but I can imagine it becoming cumbersome going back and forth.

They keep collapsing when I try to hover over them, because they're overlapping the components below:



That would allow for quick iteration and easy sharing of derivative work.

If we have an entity with an standard material like:

<a-entity geometry="primitive: sphere" material="metalness:0.0;roughness:1.0;shader:standard"></a-entity>

And we change the shader, some of the parameters won't be available on this new shader (metalness, roughness):

<a-entity geometry="primitive: sphere" material="metalness:0.0;roughness:1.0;shader:noise"></a-entity>

So probably we should delete them, as it will keep giving warnings on the console:

core:schema:warn Unknown component property: metalness +0ms
browser.js:112 core:schema:warn Unknown component property: roughness +2ms

To improve usability and ease of use with bigger clicker targets (and the keyboard navigation you get for free with tabindex) - and of course for accessibility too.

Examples:

(this is where I was looking for it)

Didn't catch it at the bottom of the scene graph.

Open to other placement suggestions as well.

1. Click yellowSphere in the scene graph.
2. Press the Exit button.
3. Press the Enter button.
4. Notice the yellowSphere is no longer highlighted in the scene graph.

Related to #7, if we used (hidden) <input type="radio"> fields, this value would be easily persisted with the checked attribute.

I know it's probably obvious to most, but I didn't actually understand that pressing the plus sign was taking the actively selected mixin in the <select> and adding it below.

I originally thought the mixins <select> menu was listing the active mixins on that entity:

It took me a good minute or so to discover that by horizontally dragging in a numeric text field that the value changes. It's neat. But wasn't discoverable. Perhaps make that more obvious or require the field to be focussed first (that's what Dev Tools do, anyway). And possibly consider using the native browser ones: input[type=number], input[type=range].

Mixins could be created directly from an entity by selecting the components and attributes we would like to add to the mixin.

I clicked on the three dots icon and remove the component by mistake. The non reversible operations should be harder to trigger to avoid unintented results.

Implement hover event over each instance on the scene, both using cursor or mouse.
It should highlight the object (using a different color or shape than the selected status) and show some simple attributes on top, like for example ID or entity type.

Look at debug:

We can may be do common non collapsible, add a button in the common space box to add a component to the list below

• shouldn't contain A-Frame injected CSS (i.e., <style type="text/css" data-href="src/style/aframe.css">).
• offer an option to possibly rewrite the URLs to be absolute (if I exported a scene from http://dev.fernandojsg.com/aframe-editor/example/, then <script src="js/aframe.js"> should be written as <script src="http://dev.fernandojsg.com/aframe-editor/example/js/aframe.js">). I know this gets tricky. Because some people will be using the editor to inspect, edit, and fork others' scenes - while others will use it to quickly tweak their scenes
• remove the injected Editor script (i.e., <script src="../build/aframe-editor.js"></script>)
• remove the injected React elements from the Editor (and the <a download>)