yesbird wrote:
> I have an idea how to combine web interface and ray tracing calculations
> using the WASM technology:
> https://webassembly.org/. With a WASM it will be possible to use POV-Ray
> API from Javascript/Typescript and the scene can be stored in JSON
> format.
>
> Having raytracing right inside the browser will open the way for
> creating online editor with many pleasant features, such as spline
> editor, for example:
> https://threejs.org/examples/?q=spline#webgl_geometry_spline_editor
>
> I know this assumes a huge amount of work and before diving into this
> inferno, I would like to ask you about possible approaches to start
> with. If I understand well from reading previous posts about related
> refactoring, the main problem is separating a scene description and
> tracing parts from the parser.
>
> Could you please point me to the modules I should examine first of all
> to create a work plan ?
> --
> YB

Thank you, Sergei.
I'm really glad that you joined us and are also thinking about these things -
and DOING them.

I had one of the demonic AI's look it over and give me its summary, because
blindly picking my way through tens of thousands of lines of opaque code was
beyond my present capabilities.

https://news.povray.org/povray.pov4.discussion.general/thread/%3Cweb.6900faee20e0e8051af05c025979125%40news.povray.org%
3E/

(I can keep hammering on this, is we think we can assemble the breadcrumbs it
drops into a map...)

I know that Chris Cason mentioned that he had some plans of his own, so maybe he
might chime in on this.

If there's some way to scan through the old newsgroup posts to get a summary of
what clipka said about disentangling the parser from the raytracer, then that's
an avenue I'd explore as well.  I think Jim Henderson has some sort of fu that
applies in that area.


- BW

Post a reply to this message