Getting Started
Mount the bundled assets and wire verified solverforge-ui primitives into an Axum app.
solverforge-ui is SolverForge’s frontend component library for
constraint-optimization applications. It ships embedded assets, UI primitives,
solver lifecycle helpers, and scheduling views without requiring npm in the
runtime integration path.
SF.createBackend(...) and
SF.createSolver(...)/sf/* via
.merge(solverforge_ui::routes())[dependencies]
solverforge-ui = "0.3.1"
let app = api::router(state).merge(solverforge_ui::routes()); // serves /sf/*
<link rel="stylesheet" href="/sf/sf.css" />
<script src="/sf/sf.js"></script>
<script>
var tabs = SF.createTabs({
tabs: [{ id: 'plan', content: '<div>Plan view</div>', active: true }],
});
document.body.appendChild(tabs.el);
var header = SF.createHeader({
title: 'SolverForge UI',
tabs: [{ id: 'plan', label: 'Plan', active: true }],
onTabChange: function (id) {
tabs.show(id);
},
});
document.body.prepend(header);
</script>
Use solverforge-ui when you want to ship SolverForge-backed web interfaces
quickly without rebuilding common UI primitives or bundling your own asset
pipeline.
It is a strong fit for:
/sf/*, include the bundled
assets, and wire the verified primitives into an appMount the bundled assets and wire verified solverforge-ui primitives into an Axum app.
Core factories, return values, and helpers in the shipped solverforge-ui surface.
Build timeline-rail and split-pane Gantt views with the shipped solverforge-ui APIs.
Backend adapters, asset serving, cache behavior, and example route contracts for solverforge-ui.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.