FROG is a public graphical dataflow language specification. It is not owned by
one editor, one runtime, one compiler, or one vendor product. A FROG-compatible
editor is an authoring tool built around the public .frog source
model and the specification-owned language boundaries.
This page tracks editor and authoring-tool efforts that are being developed around FROG. Listing an editor here does not make that editor the language, nor does it make the editor a normative implementation of FROG semantics.
| Editor | Status | Role |
|---|---|---|
| Graiphic Studio | In development | Graiphic's user-facing authoring environment with coordinated Front Panel, Block Diagram, and live Source views for creating and editing .frog documents. |
A FROG editor may provide:
- front-panel editing,
- diagram editing,
- widget placement and configuration,
- interface-map editing,
- icon editing,
- validation feedback,
- execution preparation,
- debugging and observability views.
Those conveniences remain tooling behavior. They must serialize to explicit FROG source artifacts and consume specification-owned contracts rather than creating hidden editor-only semantics.
Editor behavior
|
v
Program model
|
v
canonical .frog source
|
v
validation and execution-facing contracts
This repository remains the public home for the FROG language specification. Editor documentation may live in separate repositories when it describes a specific product or user interface. The public language specification keeps owning source shape, semantics, validation expectations, interface boundaries, widget contracts, and execution-facing handoff rules.
Graiphic Studio user documentation lives in the Graiphic Studio documentation site and its source lives in Graiphic/Graiphic-Studio. It should be read as product documentation for the editor, not as a replacement for the FROG specification.
Current product documentation includes the coordinated window workflow, Widget Navigator, Function Navigator, Icon Editor, and Studio Options. Product UI behavior remains editor documentation. Canonical source shape, numeric representation identity, Array typing, interface-map bindings, and other cross-tool contracts remain owned by this public specification.