First found in #4. This is an issue with the ThreeJS backend.

This is just a rough idea of what all should be present in Compose3D and what all has been done to help me understand which features I should focus on now. Been kind of stuck for the last week.

Geometry Primitives

• Cubes
• Cuboids
• Spheres
• Pyramids
• Tori
• Cylinders
• Parametric Surfaces
  • Functions
  • Matrices
• Planes
• Polyhedrons

Materials and Properties

• Mesh Colors (Rename to Surface Color?)
• Wireframes - This draws all triangles being drawn by the GPU.
• Edge Wireframes - Wireframe of only hard edges (ThreeJS implementation added. Can't be used for mesh plots though.)
• Visibility
• Lambert Materials
• Basic Materials
• Phong Materials
• Normal Materials
• Vertex Colors
• Mesh plot wireframe (Implemented not as a material.)

Lights

• Spot Lights
• Point Lights
• Ambient Lights

Camera

• Perspective Camera
• Modifiable look at -> Currently defaults to origin.

Defaults

• Good default camera and lights.
• default Context dimensions

General Features

• Transforms

Integration with Compose

• Switch to Measures.jl
  • Waiting for this PR to get merged.
• Rewrite Patchwork backend to use new drawpart function.

IJulia integration

• Clarify where to copy the asset files to. See JuliaLang/IJulia.jl#339, jupyter/notebook#320
• Write a writemime for signals in Patchable3D

Escher integration

• Switch to Polymer 1.0

Performance

• Improve parametric update performance.

Documentation

• More examples, screenshots and screencasts.
• API documentation.

Hi There,
it would be great, if we're all using the same geomtric types and mesh types.
I'm doing in GLVisualize probably pretty much the same, though I might have much different goals.
But at least, it would be nice to share as much infrastructure as possible, to make it easy to switch between Compose3D and GLVisualize.
Would you consider using GeometryTypes and FixedSizeArrays? I've seen, that you created your own primitives, which are quite similar to the ones in GeometryTypes.
Things are still a little messy, and I'm still not using tuples for FixedSizeArrays, because of this issue:
SimonDanisch/FixedSizeArrays.jl@21a2c21

But with some more work, this could become a very nice, unified platform for any geometric code ;)

Also you might be interested in the most recent work of Meshes and MeshIO.
Sorry if there is very little documentation...
If you have any questions, or if things are unusable for you in the current state, please consider opening issues :)

I really hope we will be able to create something smooth and unified for Julia, despite that this is all Open Source and everyone has different interests!

Best,
Simon