Aardvark.Dom.Bootstrap
1.1.6
See the version list below for details.
dotnet add package Aardvark.Dom.Bootstrap --version 1.1.6
NuGet\Install-Package Aardvark.Dom.Bootstrap -Version 1.1.6
<PackageReference Include="Aardvark.Dom.Bootstrap" Version="1.1.6" />
<PackageVersion Include="Aardvark.Dom.Bootstrap" Version="1.1.6" />
<PackageReference Include="Aardvark.Dom.Bootstrap" />
paket add Aardvark.Dom.Bootstrap --version 1.1.6
#r "nuget: Aardvark.Dom.Bootstrap, 1.1.6"
#:package Aardvark.Dom.Bootstrap@1.1.6
#addin nuget:?package=Aardvark.Dom.Bootstrap&version=1.1.6
#tool nuget:?package=Aardvark.Dom.Bootstrap&version=1.1.6
Aardvark is an open-source platform for visual computing, real-time graphics and visualization.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
- Aardvark.Application (>= 5.6.4)
- Aardvark.Base (>= 5.3.20 && < 5.4.0)
- Aardvark.Dom (= 1.1.6)
- Aardvark.Geometry (>= 5.3.20)
- Aardvark.Rendering.Text (>= 5.6.4 && < 5.7.0)
- Aardvark.SceneGraph (>= 5.6.4 && < 5.7.0)
- FSharp.Core (>= 8.0.100)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 1.1.8 | 85 | 4/28/2026 |
| 1.1.7 | 90 | 4/28/2026 |
| 1.1.6 | 85 | 4/27/2026 |
| 1.1.5 | 94 | 4/26/2026 |
| 1.1.4 | 90 | 4/26/2026 |
| 1.1.3 | 79 | 4/26/2026 |
| 1.1.2 | 88 | 4/26/2026 |
| 1.1.1 | 84 | 4/26/2026 |
| 1.1.0 | 90 | 4/25/2026 |
| 1.0.25 | 92 | 4/15/2026 |
| 1.0.24 | 98 | 4/13/2026 |
| 1.0.23 | 456 | 11/20/2025 |
| 1.0.22 | 320 | 11/13/2025 |
| 1.0.21 | 241 | 11/9/2025 |
| 1.0.20 | 222 | 10/28/2025 |
| 1.0.19 | 214 | 10/28/2025 |
| 1.0.18 | 218 | 10/23/2025 |
| 1.0.17 | 206 | 10/22/2025 |
| 1.0.16 | 202 | 10/22/2025 |
| 1.0.15 | 190 | 8/22/2025 |
refactored pick-chain selector to use FShade 5.7.4's `Effect.Dependencies`. The old logic gated mode A vs B on `Map.containsKey "PickViewPosition" eff.Outputs` (a coarse "does the user effect declare it?" check) and used `hasAllInputs` over a fully-linked module to test whether the with-normal variant was viable (one `Effect.toModule` call per draw setup). Both replaced by a pure-map analysis: for each pick-relevant semantic (`ViewSpaceNormal`, `PickViewPosition`, `PickPartIndex`) we ask "can the user's effect produce this with the geometry's actual vertex attributes?" via `EffectDeps.resolveTop`.
normal handling now has two paths, mirroring how pi/pvp work:
1. user effect produces `ViewSpaceNormal` (per-pixel pick normals — e.g. normal mapping) → use theirs, skip injection
2. geometry has `Normals` attribute → inject `viewSpaceNormalEffect` to synthesise vsn from the model normal
3. neither → no-normal variant
user effects that declare a pick output (e.g. `PickPartIndex`) but whose dep closure isn't satisfied by the geometry (e.g. they read `[<InstanceId>]` from a non-instanced render object) now degrade gracefully to the no-pi variant — previously this caused a silent attribute demand and "no buffer is bound to enabled attribute" at draw time.
extracted `PickShader.chooseChain` / `PickShader.composePickChain` as pure, public helpers; added `Aardvark.Dom.Tests` project with unit tests covering each branch of the selector + the FShade `Positions0` frag-input-renaming quirk.
requires FShade 5.7.4 (deps tracking is upstream).