Dot.Pptx 0.1.31

dot-framework

Reusable Windows libraries extracted from dotVista. Each module is published as a separate NuGet package on nuget.org.

Packages

Quick start

In a WinUI 3 app targeting net8.0-windows10.0.22621.0 or later:

<ItemGroup>
  <PackageReference Include="Dot.Ble" Version="0.1.*" />
  <PackageReference Include="Dot.Hybrid" Version="0.1.*" />
  <PackageReference Include="Dot.Pptx" Version="0.1.*" />
  <PackageReference Include="Dot.Utils" Version="0.1.*" />
  <PackageReference Include="Dot.Gateway.Client" Version="0.1.*" />
</ItemGroup>

0.1.* floats to the latest patch automatically; pin a specific version when a build needs to be reproducible.

Architecture note: Dot.Gateway

Dot.Gateway.Client is the in-process API your app uses. The actual BLE radio is owned by a separate broker process (Dot.Gateway.exe) so multiple apps can share one DotPad connection without fighting over it. The first client to connect spawns the broker; the broker self-terminates a few seconds after the last client disconnects. Input events (button presses) route to whichever client owns the OS foreground window; state events (connect/disconnect/battery) fan out to everyone subscribed.

The broker exe itself is not yet on NuGet — for now consumers either bundle it from this repo's build output or wait for the upcoming standalone Dot.Gateway package.

Layout

src/
  Windows/                          ← current platform
    Dot.Ble/
    Dot.Gateway/                    (broker exe; not yet published)
    Dot.Gateway.Client/
    Dot.Hybrid/
    Dot.Pptx/
    Dot.Utils/
  Mac/                              ← future, parallel structure with zero shared abstractions

Mac support, when it lands, mirrors the Windows tree under src/Mac/. Implementations are duplicated rather than abstracted — same module names, same namespaces, no shared base lib. Consumer source code never changes per platform; only the framework path resolves differently.

Releasing

Every push to main runs .github/workflows/publish-nuget.yml, which packs all modules and pushes to nuget.org with version <VersionPrefix>.<run_number>:

• Major.Minor lives in Directory.Build.props (<VersionPrefix> — manually bumped when an API break or feature wave warrants it).
• Patch is ${{ github.run_number }} from the workflow — increments automatically on each push.

So normal flow is: edit, commit, push → nuget.org gets 0.1.<N+1> within a couple of minutes. To bump major or minor, edit VersionPrefix in Directory.Build.props and push.

License

MIT — see LICENSE.