You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just posting this as an idea here. What about defining a very high-level API in something like Protocol buffers? Considering there will be a server-like wrapper for the RGX itself that will receive serialized commands via a customizable transport layer (TCP, UDP or inter-process) it will allow this library to serve as a simple graphics system for something like Deno or Wasmer. Obviously, such an API should be centered around a concept of batches to reduce the cost of transporting the requests. That, probably, means something like command queues in normal graphics.
Most probably, something like this should be implementable on the side as an external solution using RGX, however, I am interesting in your input on such an idea.
Cheers!
The text was updated successfully, but these errors were encountered:
Hmm let me understand, you envison a rendering backend that takes commands from some client, and carries out the drawing through rgx?
I guess that could work, but from the perspective of rgx what would be required is perhaps a more streamlined API for rendering, which it currently doesn't have.
One recent change though is that the sprite and shape batch modules are renderer-agnostic, which means these APIs can potentially be used by a librarry without having to depend on wpgu/gl.
Hi there!
Just posting this as an idea here. What about defining a very high-level API in something like Protocol buffers? Considering there will be a server-like wrapper for the RGX itself that will receive serialized commands via a customizable transport layer (TCP, UDP or inter-process) it will allow this library to serve as a simple graphics system for something like Deno or Wasmer. Obviously, such an API should be centered around a concept of batches to reduce the cost of transporting the requests. That, probably, means something like command queues in normal graphics.
Most probably, something like this should be implementable on the side as an external solution using RGX, however, I am interesting in your input on such an idea.
Cheers!
The text was updated successfully, but these errors were encountered: