#moon-pptx

#Features

• Read and write .pptx packages end-to-end — themes, masters, layouts, slides, notes, comments — without ever materialising XML by hand.
• Builder API for creating decks from scratch: text boxes, shapes, pictures, tables, and charts via Presentation::new() →add_slide_mut → with_shape → save.
• All 16 standard chart families from a typed ChartData, plus read/write support for the Microsoft 2016 extended chartEx families (waterfall, treemap, sunburst, histogram, boxWhisker, funnel, paretoLine, regionMap, clusteredColumn) — parsed losslessly and attachable to a slide, though building one still means supplying the <cx:chartSpace> XML yourself.
• Type-safe units — Emu, Pt, Inch, Cm, Angle, Percentage, RgbColor, ThemeColor are distinct types; the compiler stops you from mixing them.
• Immutable builders — slide.with_shape(s) returns a new value; _mut variants exist where editing existing decks is the natural shape.
• Lossless round-trip — unknown OOXML extensions are preserved verbatim on read → write, so files survive parsers that don't know every Microsoft extension element.
• Pure MoonBit — depends only on hustcer/fzip for ZIP/DEFLATE. No FFI, works on Native / Wasm-GC / JS / Wasm.

#Install

moon add t-ujiie-g/moon-pptx

#Quickstart

#Build a one-slide deck from scratch

let prs = @presentation.Presentation::new()

// Append a slide using the built-in Blank layout at index 0.
let _ = prs.add_slide_mut(0)

// Drop a title text box onto the new slide.
let s = prs.slides()[0]
let tb = @slide.AutoShape::textbox(
  id=2, name="Title",
  x=@units.Emu(457_200L),     // ½" margin
  y=@units.Emu(2_438_400L),   // ≈ 2.7" from the top
  cx=@units.Emu(8_229_600L),  // slide width − 2× margin
  cy=@units.Emu(914_400L),    // 1"
  "Hello, MoonBit",
)
prs.update_slide_mut(0, s.with_shape(@slide.AutoShape(tb)))

// `save()` returns PPTX bytes — write them with whatever I/O your
// backend supports.
let bytes : FixedArray[Byte] = prs.save()

#Tables

let yellow = @units.RgbColor::parse_hex("FFFF00")
let header_props = @slide.TableCellProperties::default()
  .with_fill(@oxml.Fill::SolidFill(@oxml.Color::srgb(yellow)))
  .with_anchor(@slide.Anchor::AnchorCenter)
let header = @slide.TableCell::merged_origin("Header", grid_span=2)
let header = { ..header, properties: Some(header_props) }

let row0 = @slide.TableRow::of_cells(
  [header, @slide.TableCell::h_merge_covered()],
  height=@units.Emu(457_200L),
)
let row1 = @slide.TableRow::of_cells(
  [
    @slide.TableCell::of_text("A2"),
    @slide.TableCell::of_text("B2"),
  ],
  height=@units.Emu(457_200L),
)
let t = @slide.Table::of_rows(
  [row0, row1],
  col_widths=[@units.Emu(2_286_000L), @units.Emu(2_286_000L)],
)
let gf = @slide.GraphicFrame::of_table(
  id=10, name="Summary",
  x=@units.Emu(914_400L), y=@units.Emu(914_400L),
  cx=@units.Emu(4_572_000L), cy=@units.Emu(914_400L),
  t,
)
prs.update_slide_mut(0, prs.slides()[0].with_shape(@slide.GraphicFrame(gf)))

#Charts

let data = @chart.ChartData::new()
  .with_category("Q1")
  .with_category("Q2")
  .with_category("Q3")
  .with_category("Q4")
  .with_series("Revenue", [100.0, 200.0, 300.0, 250.0])
  .with_series("Cost",    [60.0,  110.0, 180.0, 140.0])

// Pick a family: bar / line / pie / area / radar / doughnut / …
let chart = @chart.Chart::of_bar(data)
// or:  @chart.Chart::of_line(data, grouping=Stacked)
// or:  @chart.Chart::of_pie(data)
// or:  @chart.Chart::of_doughnut(data, hole_size=60)

prs.add_chart_mut(
  0, chart,
  x=@units.Emu(914_400L), y=@units.Emu(1_828_800L),
  cx=@units.Emu(4_572_000L), cy=@units.Emu(3_429_000L),
)

let scatter = @chart.Chart::of_scatter(
  @chart.ScatterData::new()
    .with_series("trend", [1.0, 2.0, 3.0], [10.0, 25.0, 32.0]),
)

let bubble = @chart.Chart::of_bubble(
  @chart.BubbleData::new().with_series(
    "growth",
    [1.0, 2.0, 3.0],
    [100.0, 200.0, 150.0],
    [10.0, 20.0, 30.0],
  ),
)

#Sub-packages

#Examples

• examples/README.md — cookbook of focused recipes (title slides, widescreen sizing, hyperlinks, speaker notes, picture cropping, tables with custom borders, charts from data, a complete pitch deck end-to-end).
• examples/sample-deck/ — a standalone MoonBit module that depends on moon-pptx exactly the way a downstream consumer would. It builds a 26-slide demonstration deck exercising every typed feature. Run it via moon -C examples/sample-deck run main --target native | tail -1 | xxd -r -p > out/sample.pptx.

#Comparison with python-pptx and PptxGenJS

#At a glance

#Where moon-pptx goes further

1. Chart coverage — 16 families build from a typed ChartData, and python-pptx's XL_CHART_TYPE lists surface / stock / of-pie with no plot implementation behind them. On top of that, the Microsoft 2016 chartEx set (waterfall, treemap, sunburst, funnel, boxWhisker, paretoLine, regionMap, histogram, clusteredColumn) parses losslessly and can be written into a deck with the OPC plumbing handled — neither competitor touches those at all. A typed builder for them is still open (ROADMAP.md G11): today you hand add_chart_ex_mut a ChartEx you parsed or assembled yourself.
2. Lossless preservation — every model node carries extension : Array[XmlElement], so third-party files round-trip with zero data loss even through features moon-pptx doesn't model.
3. Type-safe units — confusing Emu with Pt fails to compile. Integer/float dimensions elsewhere invite silent unit-mix bugs.
4. Exhaustive ADT matching — a new shape / fill / stroke / chart option the writer hasn't handled is a compile error, not a silently dropped element.
5. Multi-backend from one source — server (Native), browser (Wasm-GC), Node (JS). Neither competitor spans this.
6. SmartArt creation — all eight families emit a full five-part DiagramML graphic; the nesting families ship recursive hierRoot/hierChild layout definitions, so PowerPoint lays out the whole tree with connectors. python-pptx can only identify SmartArt; PptxGenJS cannot touch it.
7. Compile-time placeholder schema — LayoutSlide[L] makes accessing a placeholder the layout doesn't have a compile error.
8. Immutable + _mut duality — pure transforms when you want them, in-place edits when you don't.

#Where the others go further

#Feature matrix

#Compatibility

#License