Should we inform the user that their .scene file contains components that are supposed to be attached to nodes that are now missing or renamed?
If not, should we still save those components in the .scene file?

• Combine meshes marked as static with the same material on glTF export. Objects should be marked static by default.
• Combine meshes with the nav-mesh component

Scene helpers are maintained in a separate scene. Also addObject and removeObject are not called when swapping scenes, so the raycaster casts against objects from the previous scene.

• Serialize component data as extensions in the glTF export (resolved in fdf3a9b)
• Move component data from extras.components to extensions.MOZ_components or extensions.HUBS_components
• Update hubs to inflate components from extras.components or extensions.MOZ_components

• spawn-point
• skybox (fix scale)
• hoverable
• spot-light
• scene-shadow
• super-spawner (depends on hoverable)
• sticky-zone
• hide-when-quality
• visible
• nav-mesh (depends on visible)
• collision-filter
• body
• shape
• css-class replaced with interactable which is inflated as setAttribute("css-class", "interactable") in Hubs.
• sound
• layers
• text
• loop-animation
• billboard
• water
• fog (only on scene)
• media-loader

• Set up Maya project structure
• Move Maya files to proper directories and ensure they are using relative paths
• Create avatar export script
• Export all assets as glTF and test
• Publish new project structure as branch

• Panel headers should be differentiated from their content (dd1ef2e)
• Styled checkbox component
• Input group alignment (42eb7ee)
• Scene hierarchy label vertical alignment (dd1ef2e)
• Close button styling (button removed in #73)
• Property group header should have greater font weight
• Property group header should have a greater border-top/bottom

Everything in the editor is pretty dark right now. We should add an ambient light and ensure the directional light is correctly set.

• Translate, Rotate, and Scale tools with icons
• Should show active tool
• Migrate to hamburger menu

Currently, we do not deal with unnamed nodes, so the editor looks like this when we open a gltf file with many unnamed nodes. Any suggestion on how to handle unnamed nodes situation?

I'm thinking about applying [unique_prefix]_x-y-z-... (x, y, z represents the index and layer the node saved in the gltf file) to unnamed nodes in SceneLoader.js.

• Export modal
  • Author info
  • Copyright / license info
  • Thumbnail file picker
  • Output directory picker
• Merge meshes with the same materials
• Merge navigation meshes
• Write component data to extensions
• Remove objects marked as don't export
• Pass optimized scene to THREE.GLTFExporter
• Save exported json and bin files to output directory

After #52, orphaned nodes are displayed in the hierarchy, but you cannot move or modify them. Perhaps users should be able to move them under valid nodes.

There should be an "Extend" context menu item in the asset explorer when you click on a .gltf or .scene file that opens a new scene which inherits from the selected file.

Browser: Firefox

1. Add a node to the scene
2. Add a scene-ref component to the node
3. Select a ref in the component
4. Click on the ArchitectureKit directory

• Buttons at the bottom are pushed out of the window due to the large number of files.
• The panel should be scrollable to handle the large number of files.
  

• Dropping on floor
• Dropping on existing objects

• glTF models should have thumbnail images in the Asset Explorer / File Picker (Generate thumbnails on open project / file change event?)
• material files should have thumbnail images in the Asset Explorer / File Picker (Render material on sphere with default light to thumbnail image)
• Texture previews should be shown next to their respective file picker.

Backspace default behavior should be prevented when input field is not focused. Deleting the selected object in the viewport should still work.

You should be able to have viewports from various perspectives (left/right/top/bottom/front/back).

To Do:

• Split out viewport specific code in Viewport.js
• Figure out viewport panel UI/UX

Things that refer to file paths (references, materials, material textures) can have very inconsistent file paths at the moment. I've seen everything from ./foo.file to /api/files/foo.file to http://hubs.local:9090/api/files/foo.file at various stages of adding, setting and saving components/scenes.
It can sometimes lead to scenes breaking.

This is a big feature. Right now when you edit a referenced scene, it opens that scene in isolation, but you really want to be able to edit it in context of the parent scene. Just putting it here to remember it.

• Issues with editing numbers
• "Scrub" to change number
• Maybe display a slider when there is a fixed range

General documentation on using the editor. Getting started, task-specific tutorials, etc.

Currently images are kept in place when exporting the glTF. In the optimization step, move the images into the output directory and rewrite their paths.

If we allow users to edit children under duplicate roots, there would be one situation that might confuse users when they reopen the .scene file.

Users might move children from one duplicate root to another one and then save the file. The changes won't be saved since we do not modify the gltf file, so users would still see all children attached to the first duplicate root when they reopen .scene file.

Show warnings when these things happen and allow non-destructive recovery.

• Renamed/deleted nodes in inherited scene/gltf
• Duplicate names
• Missing resources

• Author info (Moved to #220)
• Copyright / license info (Moved to #216)
• Thumbnail file picker (Moved to #223)
• Output directory picker

• You should be able to reorganize the positions of the editor panes to better accommodate different screen sizes.
• Your settings should persist between page loads (Probably save to localStorage)
• You should be able to revert to the default layout.

Future additions could include saving layouts and some predefined layouts. As of now there are only 3 panes so I don't think that's necessary.

• Should be able to edit textures and material properties in the properties panel
• Materials should be stored as a separate file and can be referenced by meshes in multiple scenes.
• Should be able to clone an existing material (from a glTF file or material file)

For picking material textures and scene/gltf references

• File
  • New Scene
  • Open Project in Explorer
  • Save
  • Save As
  • Export
• Help (Hotkeys / getting started guide / links to resources)

Should show a swatch (and maybe hex/rgb/hsl) and only open full color picker on click.

Depends on #45

• Should be able to change position, rotation, and scale snap scale.
  • Uniform scale along all axes
  • Scale snapping for each axis individually
  • Hotkey for increasing / decreasing snap resolution

Sample scenes demonstrating various things

• Nodes start dragging as soon as you put your mouse down
• Entire hierarchy should not be outlined when it is focused (5f548e2)