{flaws ? {focus === i ? u.long : u.short}
+Chenglong Wang, Yuwei Xiao, Kecheng Lu, Yunhai Wang, Alper Sarikaya, Michel Galley, Chris Quirk, Jianfeng Gao
Deep Learning Group, Microsoft Research
microsoft.github.io/flint-chart
Flint is a visualization language for AI agents to reliably create polished data visualizations. The agent writes a short, simple spec, and Flint's compiler takes care of the rest.
@@ -268,15 +319,10 @@ export const SLIDES: SlideDef[] = [ }, // ======================================================== Act 1 - { - id: 'act1', kind: 'section', render: () => (<> -We'll build one chart with a declarative grammar, Vega-Lite, step by step.
- >), - }, { id: 'ideal', render: () => (<> -Ideally, a chart is a few lines that are easy to change.
Task: "Make a heatmap of net new users by game and month for our report page, in The Economist style, and let me click a game to highlight it next to our table."
@@ -302,30 +348,26 @@ export const SLIDES: SlideDef[] = [ rows={LONG_ROWS.map((r) => [r.game, r.region, r.period.replace('-', ''), r.newUsers])} />Rows: 60 months × 24 games × 4 regions = 5,760.
- A click filters the table and a picker selects a game. These {GLUE_LINES} lines talk in signal names and internal stores, not in terms of the data.
+{GLUE_LINES} lines, all in signal names.
>), }, { @@ -391,16 +433,10 @@ export const SLIDES: SlideDef[] = [ >), }, - // ======================================================== Act 2 - { - id: 'act2', kind: 'section', render: () => (<> -Today we would hand this to an agent. It can do it, but then we notice five problems.
- >), - }, + // Act 1, continued: handing it to an agent { id: 'five-problems', render: () => (<> -Low-level configuration ties together what the data means, how the chart looks, and how it behaves. Every change ripples into the others.
-"The logic depends on coordinates, pixels, and SVG paths, all tangled together. So the agent reasons, writes, debugs, and goes around again, and still hands you something fragile."
-You and your agent work with the high-level specs, without losing control. The compiler takes care of data parsing, layout, events, design tokens, and the dependencies between them.
A few lines on the raw data, with the same look. Click a game to try it.
Semantic types and a layout engine take care of what the data means.
+ id: 'sec-a', render: () => (<> +
+ Semantic types decide data processing, axes, and colors, so the compiler can infer the low-level configuration reliably, without heuristics.
+
- The Flint spec, on the raw rows.
- What the compiler wrote in Vega-Lite because of the three types.
| {family} | {types} |
|---|
Agents are really good at this. Saying that a column is a month, a profit, or a country is just reading the data, and it is far easier than writing parsing, scale, and format code.
Each item is a spring that wants its own room, and the canvas is a stiffer spring that resists growing. The plot settles where the two balance, never past the most it may stretch.
Each library structures its parameters differently. The same chart spec compiles to all of them.
A formal specification of style, written once for every chart.
+ id: 'sec-b', render: () => (<> +
- The "economist" definition, from the theme library.
Semantic events and update operators describe how a chart behaves.
+ id: 'sec-c', render: () => (<> +Drag to turn the globe; the country facing you is the focus.
+Scroll to zoom the months, and the bars, axis, and labels are laid out again.
+In a chat, in your app, and beyond the presets.
+ id: 'act4', render: () => (<> +Describe the chart and how it should behave. The agent writes the interaction spec next to the chart spec, and the chart appears in the conversation, ready to hover and read.
-Visualize U.S. egg and bread prices since 2015, and let me hover to read both at any month.
-Here it is. Hover along the timeline to read both prices.
-"Show goals by team, and when I click a team, list its scorers in the panel beside it."
@@ -641,9 +681,27 @@ export const SLIDES: SlideDef[] = [Pick a row in the table, and the chart follows; select points in the chart, and the table follows.
+Hover a sentence in the text, and the chart shows what it is about.
+"Let readers draw where they think coal's share of U.S. electricity went, then reveal the real line."
@@ -657,18 +715,9 @@ export const SLIDES: SlideDef[] = [ >), }, { - id: 'story', render: () => (<> -Hover a sentence in the text, and the chart shows what it is about.
-"Create a theme inspired by a Disneyland day out: candy colors, rounded shapes, and a playful font."
-
+ "Here is our brand guide: navy and teal, slate for supporting series, Georgia for headlines, and quiet grids. Write a Flint theme so every chart in our reports matches."
+
Drag to turn the globe; the country facing you is the focus.
-Scroll to zoom the months, and the bars, axis, and labels are laid out again.
+Open source, MIT license. flint-chart on npm and PyPI, and the flint-chart-mcp server for your agent, at github.com/microsoft/flint-chart.
Add the Flint MCP server to GitHub Copilot or your own agent with npx -y flint-chart-mcp, and ask for styled, interactive charts, reports, and dashboards right in the chat.
Add the Flint MCP server to GitHub Copilot or your own agent with npx -y flint-chart-mcp, and ask for charts and dashboards right in the chat.
Build Flint into your product with npm install flint-chart. Give your agent the Flint skills, and its charts will talk to your tables, widgets, and app state.
Let's work on new themes together. Your team's style guide can become a Flint theme that every chart, on every library, follows.
+Let's work on new themes together. Your team's style guide can become a Flint theme that every chart follows.
We want to collaborate! Ping me and I'm happy to demonstrate Flint to your team, and to work together on the next generation of interactive artifacts.
diff --git a/site/src/talk/talk.css b/site/src/talk/talk.css index 8c6b5cbe..4b74233d 100644 --- a/site/src/talk/talk.css +++ b/site/src/talk/talk.css @@ -42,7 +42,6 @@ .talk-slide strong { color: var(--ink); font-weight: 650; } .talk-slide code { font: 500 0.86em/1.3 ui-monospace, 'SF Mono', Menlo, Consolas, monospace; color: var(--ink); background: var(--panel); padding: 0.06em 0.3em; border-radius: 6px; } .talk-lead { font-size: 34px !important; line-height: 1.4; color: var(--ink) !important; } -.talk-quote { font-size: 32px; line-height: 1.45; color: var(--ink); font-style: italic; } .c-meaning { color: var(--meaning); } .c-look { color: var(--look); } .c-behavior { color: var(--behavior); } @@ -110,10 +109,6 @@ .talk-slide.is-title h1 { font-size: 80px; max-width: 1300px; margin-bottom: 16px; } .talk-slide.is-section h1 { font-size: 76px; } .talk-slide.is-statement h1 { font-size: 64px; max-width: 1300px; } -.talk-bar { width: 120px; height: 10px; border-radius: 5px; margin-bottom: 32px; flex: none; } -.talk-bar.meaning { background: var(--meaning); } -.talk-bar.look { background: var(--look); } -.talk-bar.behavior { background: var(--behavior); } /* A chat, as an agent client shows it. */ .talk-chat { flex: 1 1 auto; min-height: 0; display: flex; flex-direction: column; gap: 16px; background: var(--panel); border-radius: 16px; padding: 22px; } @@ -164,14 +159,16 @@ .talk-dashboard .idash-heading h1 { font-size: 44px; line-height: 1.1; max-width: none; } /* Call to action: one card per audience, each with its section color on top. */ -.talk-cta-wrap { flex: 1 1 auto; min-height: 0; display: flex; flex-direction: column; justify-content: center; gap: 32px; } +.talk-cta-wrap { flex: 1 1 auto; min-height: 0; display: flex; flex-direction: column; justify-content: center; gap: 22px; } +/* The three use cases, as the act 4 sketch draws them, above the card for each. */ +.talk-cta-sketch { flex: 1 1 200px; min-height: 140px; max-height: 240px; position: relative; } .talk-cta-wrap > .talk-cta { flex: none; align-items: stretch; gap: 28px; } -.talk-slide .talk-collab { margin: 0; font-size: 30px; line-height: 1.45; padding: 22px 28px; } -.talk-cta-card { background: var(--panel); border-radius: 12px; border-top: 6px solid #2f6db5; padding: 22px 26px; } +.talk-slide .talk-collab { margin: 0; font-size: 27px; line-height: 1.4; padding: 16px 26px; } +.talk-cta-card { background: var(--panel); border-radius: 12px; border-top: 6px solid #2f6db5; padding: 18px 24px; } .talk-cta-card.look { border-top-color: #e8954a; } .talk-cta-card.behavior { border-top-color: #d9534f; } .talk-cta-card h3 { margin: 0 0 14px; } -.talk-cta-card p { font-size: 26px; line-height: 1.45; margin: 0; } +.talk-cta-card p { font-size: 23px; line-height: 1.4; margin: 0; } /* A side-by-side demo stacked for a narrow slot: the chart on top, the table below it. */ .talk-slide .talk-stacked-demo .ig-continent-cohort .it-workspace { grid-template-columns: minmax(0, 1fr); } @@ -196,3 +193,38 @@ box-shadow: 0 8px 22px rgba(0, 40, 90, 0.12); overflow: hidden; } .talk-themes-card:hover { z-index: 20 !important; } + +/* Labels under the use-case sketch: one column per panel, in the deck's own type. */ +.talk-usecases { flex: none; display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 40px; padding: 0 3%; } +.talk-usecases h3 { margin: 0 0 6px; text-align: center; } +.talk-usecases p { margin: 0; font-size: 24px; line-height: 1.4; text-align: center; } +.talk-usecases .on h3 { color: #c0392b; } +.talk-usecases .off { opacity: 0.4; } + +/* The first slide of each act: its title leads with a mark, in place of a separate divider slide. */ +.talk-slide h2.is-act::before { + content: ''; display: inline-block; width: 0.42em; height: 0.42em; margin: 0 0.5em 0 0.06em; + background: #0067b8; border-radius: 3px; transform: rotate(45deg); vertical-align: 0.14em; +} + +/* A callout that floats over the slide like a sticky note, out of the layout's flow. */ +.talk-slide .talk-callout { + position: absolute; top: 46px; right: 64px; z-index: 5; max-width: 420px; margin: 0; + padding: 18px 22px; border-radius: 10px; background: #fff7d6; border: 1.5px solid #e8c766; + color: var(--ink); font-size: 27px; line-height: 1.35; font-weight: 550; + box-shadow: 0 12px 28px rgba(60, 45, 0, 0.18); transform: rotate(1.6deg); +} + +/* The problems circled on a chart, numbered to match its red badges. */ +.talk-flaws { flex: none; display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 40px; margin: 8px 0 0; padding: 0; list-style: none; } +.talk-flaws li { display: flex; align-items: flex-start; gap: 12px; margin: 0; font-size: 26px; line-height: 1.35; color: var(--ink); } +.talk-flaws span { flex: none; width: 34px; height: 34px; border-radius: 50%; background: #e4572e; color: #fff; font-weight: 700; font-size: 20px; display: grid; place-items: center; } + +/* A sketch with text laid over it: the frame keeps the sketch's aspect, so text and lines stay aligned. */ +.talk-frame { position: absolute; inset: 0; margin: auto; max-width: 100%; max-height: 100%; container-type: size; } +.talk-frame .talk-sketch { position: absolute; inset: 0; } +.talk-leaf { position: absolute; transform: translateY(-50%); white-space: nowrap; font-size: 2.9cqw; color: var(--ink); line-height: 1.2; } +.talk-leaf.mono { font: 500 1.9cqw/1.2 ui-monospace, 'SF Mono', Menlo, Consolas, monospace; } +.talk-leaf.muted { color: var(--ink-3); } +.talk-leaf.good { color: #3d7a27; } +.talk-slide .talk-callout.talk-callout-inline { position: relative; top: auto; right: auto; flex: none; max-width: none; margin: 0 8px 8px; transform: rotate(-1deg); }