Generated API Reference

The hosted SDK Javadoc version, how it is generated, and which review exceptions apply.

The hosted SDK Javadoc automatically follows the latest published Stable release and is generated from that release’s exact source commit. Publication metadata records the live version and source. The baseline snapshot below remains documented for the versioned examples and reviewed exceptions.

Documented baseline: Stable 0.67.4

ItemValue
Generated fromTurboism Stable source 5e0f8b02c (tag v0.67.4)
Identifies itself assdk 0.67.4 API
Public packages63
Searchable public types948
Hosted atturboism.dev/sdk/index.html

This documented snapshot is generated from the Stable 0.67.4 release tag. Use that release’s turboism-sdk-0.67.4.jar and turboism-event-processor-0.67.4.jar with these examples. The template setup script defaults to the stable channel; check gradle.properties and the filenames to confirm the version you are compiling against.

Changes since the 0.67.0 reference

The hosted reference adds 15 public types compared with the previous 0.67.0 reference:

  • dev.turboism.sdk.cubism.model: AtlasPageAppendPlan, Drawables.SourceGeometryRequest, ModelImagePlacement, WarpMorphSnapshot (with WarpMorphSnapshot.Form and WarpMorphSnapshot.Key);
  • dev.turboism.sdk.cubism.textureatlas: TextureAtlasPackingException (with TextureAtlasPackingException.Reason), TextureAtlasPageSize, and TextureAtlasPolygonLayoutPlanner, which is @Incubating;
  • dev.turboism.sdk.plugin: AbstractTurboismPlugin;
  • dev.turboism.sdk.ui.appearance: PaletteRowAction (with PaletteRowAction.State);
  • dev.turboism.sdk.ui.settings: SettingsControl.FilePath;
  • dev.turboism.sdk.ui.window: TurboismProgressDialog.

Documentation update workflow

When the public SDK, its documentation, or its version changes:

  1. generate Javadoc with the source repository's :sdk:javadoc task in release-version mode;
  2. verify the exact version and reject snapshot output;
  3. review every publicly searchable package and type;
  4. confirm that internal implementation types and unapproved Preview APIs are not presented as public contracts;
  5. check generated text for private data, local paths, credentials, host logs, or implementation-only evidence;
  6. synchronize the reviewed output to the documentation site; and
  7. run the documentation lint, type check, and production build.

Successful generation alone does not approve publication.

Reviewed publication exceptions

The documented baseline reproduces the compiled public surface of 5e0f8b02c, so it documents two conditions that review classified as exceptions rather than as hidden problems. Both are re-checked on every synchronisation, and any blocker outside this list still fails the run.

ActiveReadProjections is public but not a contract

dev.turboism.sdk.cubism.ActiveReadProjections is compiled as a public class because CubismFacade and CubismReadCapabilityService default methods share its helpers. The class Javadoc states that it is not part of the stable plugin API surface.

  • Its page is hosted because the type already exists in the generated source bytecode.
  • It is not a supported extension point. Do not call it, and do not treat its signatures as a compatibility promise.
  • It must remain listed as non-contractual here and in the SDK API Guide for as long as the type stays public.

Repaired constant-values anchor

The JDK Javadoc generator writes a contents link to #dev.turboism in constant-values.html without emitting a matching target. The synchronisation script adds the missing anchor, reports the repair on every run, and still fails on any other broken link.

Preview API language

Some public types still describe themselves as Preview contributions. That wording means the type is capability- and version-sensitive, not that it is part of a Stable line. Availability still depends on the permission, the capability Provider, and the exact Cubism Editor version, as described in SDK API Guide.

Using this reference

  • Treat generated Javadoc as documentation of the current source, not as an independent stability promise. The reviewed binary API baseline in the Turboism source repository remains the compatibility gate.
  • For guided behavior, version limits, and readiness boundaries, use the SDK API Guide first.
  • Do not rely on the hosted HTML reference alone for release, deployment, or compatibility claims.