Viewer App Tracking Issue

[bschwind]

• Improve camera movement in the current app #61
• Add XYZ grids #62
• Add an XYZ gizmo to visualize current orientation #63
• Add better shading to the rendered models #64
• Support visual 2D sketch editing #65
• Add a timeline view to see the part evolve over time #66
• WASM Modeling API #67
• Add inline GUI widgets to give interactive parameter control #68
• "Source mapping" to show which lines of code generated which geometry #69
• Support parts assembly #70

[tymokvo]

Hello, I thought this might be the best starting point for this question:
Would you be in support of exposing the viewer::ViewerApp publicly? Maybe as a supertrait of simple_game::GameApp?

I'd like to be able to use a lot of the implementation there for viewing models but independently of the Rust -> Wasm -> Viewer pipeline.

[bschwind]

There are probably parts I could "librarify", what in particular are you interested in?

For the most part there's nothing too fancy there - just winit for window creation and input, wgpu for rendering, and a trackball camera (which desperately needs some more work).

The only real integration with opencascade is extracting the triangle mesh, and list of edges from a given Shape

[tymokvo]

I am most interested in the basic opencascade -> wgpu transformations (e.g. meshes & edges -> buffers) such that a library user could:

• create a winit application
• create a wgpu surface & device
• create a Shape
• render the Shape onto the surface via an arbitrary projection matrix
• mutate the projection matrix via WindowEvents

I'd be happy to hack around on it, but thought that you may already have ideas on the direction here.

[bschwind]

I think it's probably best to keep the rendering code contained within viewer for now, and have the OCCT code give you the minimum needed to draw surfaces and edges. The wgpu code for the viewer app is nothing particularly special, it just draws a triangle mesh given to it, and thick lines using the technique from this article.

I will eventually add clipping plane rendering support which does get a little bit specific to rendering CAD models, so maybe when I get back around to working on that I can try to bundle things up in a library which can be used outside of the viewer. I think it's a good goal to have it be organized that way eventually.