Jsonic++
Focused native JSON parsing, validation and transformation tooling for build and application workflows.
Treat JSON as a first-class build input instead of incidental text.
Jsonic++ is the focused JSON member of Gantry’s native build-tool family. Its job is deliberately narrow: parse structured JSON, validate it where a schema or contract exists, and make transformation workflows predictable from native tooling.
That narrowness is useful. Projects should not need to adopt a large framework merely because one stage of a build needs robust structured-data handling, and Gantry does not need to hide JSON processing inside Nift or another unrelated product.
Jsonic++ therefore complements the suite without becoming a mandatory dependency. Use it when dedicated JSON processing is valuable; skip it when the application already has the right parser or validation layer.
Useful capability without mandatory complexity.
The project stays focused on its own job; the surrounding Gantry tools remain optional.
Turn JSON text into structured data through a focused native implementation.
Catch invalid or unexpected data close to the source instead of letting it fail later in generation or runtime code.
Use parsed data as the source for deliberate conversion or generation steps instead of brittle text replacement.
Fit JSON work into C++ applications and command-line pipelines without requiring a JavaScript runtime.
Start with the shortest path.
Advanced deployment or integration features appear only when the workflow actually needs them.
- 01
Use Jsonic++ at the boundary where JSON enters a native build or toolchain.
- 02
Validate the structure before downstream generation so errors are reported close to the source data.
- 03
Transform or hand the parsed data to the next stage—often Nift or another build step—without making Jsonic++ own that stage.
Connections that remove real hand-off friction.
Each product already owns one side of these workflows. The integration exists to remove duplicate navigation, setup or context.
Nift
Nift already has structured-data workflows and schema validation. Jsonic++ is useful when JSON processing needs to happen outside the template engine or as a native preprocessing/application stage before Nift consumes the result.
Explore Nift →Markup++
Jsonic++ and Markup++ solve different source-format problems: structured machine data versus authored document markup. A content pipeline can use either or both without coupling the tools together.
Explore Markup++ →Minify++
Jsonic++ can prepare structured input while Minify++ optimizes final web assets much later in the pipeline. Their relationship is composability rather than direct integration.
Explore Minify++ →Local tool, no my.* indirection.
Jsonic++ is primarily a CLI or embeddable native tool rather than a persistent web service. A my.* instance registry would add a choice where there is no running instance to choose.
It still belongs to Gantry Tools, appears in the project directory and can be exposed from a configurable my.gantry.cv launcher if somebody wants quick access to its website or documentation.
Why my.* is reserved for running applications →Where Jsonic++ earns its place.
Validate and transform data before handing it to templates or generators.
Use JSON without pulling an unrelated runtime into a C++ tool.
Catch malformed input at the boundary rather than debugging its downstream effects.
Explore Jsonic++.
Project-specific installation, commands and release details live on the project site.