I just aquired a project to do visualization in WebGL. My experience is some years C++, OpenGL and GLSL. I did some reading and have a basic idea about what's possible and what not.
So here is what the WebGL widget should be able to do. That picture is from a MRI viewer i wrote a couple of years ago
So there's nothing too fancy. Just some geometry, colored fiber tracts as lines or tubes, textured slices, interaction has to be decided when I know what's possible and what is not.
So here are my questions.
- I already know there's no 3D Textures. That would mean about 160+200+160 2D textures for the 3 directional slices. How would WebGL handle such a large number of textures.
- Is there some sort of native transparency? I guess vertex sorting or multipass rendering is probably not an option?
- How is picking handled. Do I have to keep like my own scene graph and calculate intersections myself?
- Even when downsampled I guess the raw data for a scene like in the picture is something between 20 and 50 MB ( being a bit liberal with the numbers here ). That's quite a big junk that has to be transfered to the browser. Ok that's not a question
That's it for now. I'm sure more question will come to more I learn. Thanks in advance for any answers.