Michael MIGLIORE

> which could be remedied with some form of submesh outline/ transparent unique color render mode. It's not supported for FBX yet, but the geometry mode can help you for...

I agree, VTK should be a private dependency of libf3d. Ideally, f3d executable should only provide the command-line parsing, and config file management.

Here are my inputs. `libf3d` usage should allow the user to call something like that: ```cpp f3d::window w = f3d::createWindow(f3d::context ctx); // create window (external, native, android ...) w.addFile("/path/file.vtp"); //...

@mwestphal I like it! Regarding bindings, we will need Java bindings too for Android. I will take care of it, don't worry 😛

I still think providing C functions can be useful, for C programmers of course, but it will make other bindings easier, like Rust for instance: https://stackoverflow.com/questions/52923460/how-to-call-a-c-dynamic-library-from-rust

Here is an interesting part in space-thumbnails documentation: https://github.com/EYHN/space-thumbnails#speed > Rendering thumbnails for 3D models may not be that fast. To keep your explorer smooth and available, we have made...

Current status: - `VTK` is building fine on arm64 and x64, fixed [here](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8775) but fails for 32-bits architectures. - `libf3d` is building properly without OCCT/Assimp modules (it's currently 42MB, we...

> > Java interface prototype is done, but will need a complete rewrite (ideally in Kotlin) to create a good user experience (let's discuss the specs) > > What does...

Current status: https://user-images.githubusercontent.com/6069752/186754316-5d9a3186-c151-49e3-89f8-4fe67fecca54.mp4

It's an interaction issue