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
Copy file name to clipboardExpand all lines: ARCHITECTURE/index.html
+23-2Lines changed: 23 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -389,7 +389,28 @@
389
389
390
390
391
391
<spanclass="md-ellipsis">
392
-
User guide
392
+
User API
393
+
</span>
394
+
395
+
396
+
</a>
397
+
</li>
398
+
399
+
400
+
401
+
402
+
403
+
404
+
405
+
406
+
407
+
408
+
<liclass="md-nav__item">
409
+
<ahref="../drp/" class="md-nav__link">
410
+
411
+
412
+
<spanclass="md-ellipsis">
413
+
Datoviz Rendering Protocol
393
414
</span>
394
415
395
416
@@ -966,7 +987,7 @@ <h3 id="client">Client<a class="headerlink" href="#client" title="Permanent link
966
987
<p>The client provides a thread-safe FIFO queue on which window and input events are sent.</p>
967
988
<p>The GPU-agnostic client and the client-agnostic (static) renderer are linked together via the <strong>presenter</strong>, which allows dynamic processing of the incoming requests by the renderer and appropriate event loop synchronization.</p>
<p>The <strong>Datoviz Intermediate Protocol</strong> is entirely defined in <code>request.h</code>.</p>
990
+
<p>The <strong>Datoviz Intermediate Protocol</strong> is entirely defined in <code>datoviz_protocol.h</code>.</p>
970
991
<p>It provides a generic intermediate-level GPU visualization library that is somewhat similar to the WebGPU API. It deals exclusively with <strong>GPU objects</strong>, NOT visual objects. The protocol comes with NO graphical primitives, it supports arbitrary shaders and graphics pipelines. Graphical primitives and higher-level visualization constructs are implemented in the Visuals library and the Scene API described below</p>
971
992
<blockquote>
972
993
<p><em>Note</em>: although compute shaders are already mostly supported in the renderer, they are not yet implemented in the Datoviz Intermediate Protocol. They will be in the future, depending on user feedback. This should be fairly straightforward (adding functions in <code>requests.h</code>, implementing them in <code>renderer.cpp</code>, writing tests and documentation...).</p>
<p>If packages are not available on your system, you can build Datoviz yourself.</p>
838
+
<p><strong>Note:</strong> Datoviz is currently built and tested with the <strong>Vulkan LunarG SDK v1.3.280</strong> (you normally don't need to install it to build Datoviz on Linux and macOS, only on Windows). We'll regularly update this version.</p>
<li><ahref="https://vcpkg.io/en/">vcpkg</a>. The <code>VCPKG_ROOT</code> environment variable should be set and should be in the <code>PATH</code>.</li>
921
-
<li>Python (e.g. conda).</li>
939
+
<li><ahref="https://vcpkg.io/en/">vcpkg</a>: The <code>VCPKG_ROOT</code> environment variable should be set and should be in the <code>PATH</code>.</li>
940
+
<li><ahref="https://github.com/casey/just/releases">just</a>: Extract the just.exe file into C:\mingw64\bin (created by WinLibs).`</li>
941
+
<li><ahref="https://jqlang.github.io/jq/download/">jq</a>: For example, with winget, use <code>winget install jqlang.jq</code></li>
0 commit comments