Extension points

One section per seam: what you write, where it goes in, and what is registered through it in this build. Generated from the registries themselves.

Curve type

A shape that can be placed on data and fitted. The only seam whose members self-register, from the unit's own initialization section.

• You write — TCurveClass (class of TNamedPointsSet)
• Entry point — TCurveTypesSingleton.CreateCurveFactory.RegisterCurveType
• Registered here — 13

Data loader

Reads one file format. The Open dialog's filter is built from this registry, so a build can only offer what something can actually read.

• You write — TDataLoaderClass + extensions + format name
• Entry point — RegisterDataLoader
• Registered here — 2

Minimizer

An engine, and the capability answers the client greys choices out from. Its factory returns the IFitBackend that does the work.

• You write — TMinimizerInfo (with a TBackendFactory)
• Entry point — RegisterMinimizer
• Registered here — 2

Loss function

What "best fit" means. Compatibility with a curve type is DERIVED from the two capability flags, never from a table of type names.

• You write — TLossInfo (evaluate + pool)
• Entry point — RegisterLoss
• Registered here — 4

REST action

One verb of the HTTP API the desktop client and any other caller use.

• You write — TActionInfo (with a TActionHandler)
• Entry point — RegisterAction
• Registered here — 14

Explanation

What everything a user meets says about itself: what it is, why it is allowed or refused, whether that rests on the field's sources, on convention or on this software's own choice, what it does not cover, and where to read more. A curve type explains itself through its class; anything else a module adds, through its own provider.

• You write — IExplanationProvider (a namespace and its topics)
• Entry point — RegisterExplanationProvider
• Registered here — 13

Server module

An analysis vertical's server side: the resources it answers and its per-problem session state.

• You write — IAppModule
• Entry point — RegisterAppModule
• Registered here — none. This seam exists for modules; the public framework ships none, and it is yours to claim.

UI module

A module's contribution to the window, declared as data. One declaration serves three surfaces: the menu bar, the Tools pane and the Model panel's context menu - Surface says where an entry is shown and Scope whether it acts on the selected row. Structure for the Model panel is pushed separately under structure_id, and the panel itself belongs to the framework. WHICH contributor fills it is not arbitrated: it follows the selected curve type's placed_by_point_set, reported on the curve_types seam - empty means the framework's flat list of curves, and a named set means the module owning that set describes what its markup produced. The client names no module type.

• You write — IUiModule
• Entry point — RegisterUiModule
• Registered here — none. This seam exists for modules; the public framework ships none, and it is yours to claim.

Python sidecar pack

Names a module's <name>_routes.py, which the sidecar imports on start. Only the name travels; the sidecar finds the file itself.

• You write — a package name
• Entry point — RegisterSidecarModule
• Registered here — none. This seam exists for modules; the public framework ships none, and it is yours to claim.

Curve builder

Builds every curve a marked point set describes. Without one, the engine takes the position-based path.

• You write — point set name -> TCurveBuilder
• Entry point — RegisterCurveBuilder
• Registered here — none. This seam exists for modules; the public framework ships none, and it is yours to claim.

Chart overlay

Redraws a module's own marks after the model is recomputed, so the client need not name the module to refresh it.

• You write — TModuleOverlayProc
• Entry point — RegisterModuleOverlay
• Registered here — none. This seam exists for modules; the public framework ships none, and it is yours to claim.

Home · Architecture