Atlas / Skills / zhanghandong / Makepad 2.0 Migration

Makepad 2.0 MigrationSAFE

skills/zhanghandong/makepad-2-0-migration

Build App with Makepad and AI skills

Verdict
SAFE
Grade
B
Trust score
89 /100
Version
—
Hosts
1 documented
License
—
Stars
748
01

Overview

Build App with Makepad and AI skills

Read from source at commit 7cbc563d4f32OBSERVED · 2026-10-12
02

Host compatibility

What the documentation claims. We have not run a compatibility test.

HostStatusNotes
cursormentioned
03

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: makepad-2.0-migration
description: |
  CRITICAL: Use for migrating from Makepad 1.x to 2.0. Triggers on:
  makepad migration, live_design to script_mod, makepad upgrade, makepad 1.x,
  old syntax, new syntax, makepad breaking changes, makepad 迁移, 旧语法,
  LiveHook to ScriptHook, apply_over to script_apply_eval,
  Live to Script, live_design!, angle brackets to curly braces
---

# Makepad 1.x to 2.0 Migration Skill

> **Version:** makepad-widgets (dev branch) | **Last Updated:** 2026-03-03

## Overview

Makepad 2.0 is a **fundamental architecture shift** from compile-time static DSL to runtime scripting. Migration involves syntax changes, derive macro updates, lifecycle method renames, and new patterns for state management.

## Documentation

Refer to the local files for detailed documentation:
- `./references/migration-guide.md` - Complete migration reference with examples

---

## Quick Syntax Mapping Table

| Makepad 1.x | Makepad 2.0 | Notes |
|-------------|-------------|-------|
| `live_design! { ... }` | `script_mod! { ... }` | Core macro change |
| `<Widget> { ... }` | `Widget{ ... }` | No angle brackets |
| `Key = Value` | `Key: value` | Colon, not equals |
| `(THEME_COLOR)` | `theme.color_*` | Theme namespace |
| `live_body: { ... }` | `body +: { ... }` | Merge operator |
| `#[derive(Live)]` | `#[derive(Script)]` | Derive macro |
| `#[derive(LiveHook)]` | `#[derive(ScriptHook)]` | Lifecycle hooks |
| `#[derive(Widget)]` | `#[derive(Widget)]` | Unchanged |
| `before_apply()` | `on_before_apply()` | Method rename |
| `after_apply()` | `on_after_apply()` | Method rename |
| `apply_over!()` | `script_apply_eval!()` | Runtime updates |
| `DefaultNone` | `Default` | Enum default |
| `LiveRegister` | `WidgetRegister` | Widget registration |
| `live_register()` | `register_widget(vm)` | Registration method |
| `LiveId` | `LiveId` | Unchanged |

---

## Step-by-Step Migration

### Step 1: Replace Macro

```rust
// OLD
live_design! {
    import makepad_widgets::base::*;
    import makepad_widgets::theme_desktop_dark::*;

    App = {{App}} {
        ui: <Root> { ... }
    }
}

// NEW
script_mod! {
    use mod.prelude.widgets.*

    startup() do #(App::script_component(vm)){
        ui: Root{
            // ... UI definition
        }
    }
}
```

### Step 2: Update Derives

```rust
// OLD
#[derive(Live, LiveHook, Widget)]
pub struct MyWidget { ... }

// NEW
#[derive(Script, ScriptHook, Widget)]
pub struct MyWidget { ... }
```

### Step 3: Update App::run

```rust
// OLD
impl LiveRegister for App {
    fn live_register(cx: &mut Cx) {
        makepad_widgets::live_design(cx);
    }
}

// NEW
impl App {
    fn run(vm: &mut ScriptVm) -> Self {
        crate::makepad_widgets::script_mod(vm);
        App::from_script_mod(vm, self::script_mod)
    }
}
```

### Step 4: Rename Lifecycle Methods

```rust
// OLD
impl LiveHook for MyWidget {
    fn before_apply(&mut self, cx: &mut Cx, ...) { ... }
    fn after_apply(&mut self, cx: &mut Cx, ...) { ... }
}

// NEW
impl ScriptHook for MyWidget {
    fn on_before_apply(&mut self, cx: &mut Cx, ...) { ... }
    fn on_after_apply(&mut self, cx: &mut Cx, ...) { ... }
}
```

### Step 5: Update DSL Syntax

```
// OLD - angle brackets, equals signs
<View> {
    width: Fill, height: Fill
    show_bg: true
    draw_bg: { color: (THEME_BG) }

    title = <Label> {
        text: "Hello"
        draw_text: { color: #fff }
    }
}

// NEW - curly braces, colons, theme namespace
View{
    width: Fill height: Fill
    show_bg: true
    draw_bg.color: theme.color_bg_app

    title := Label{
        text: "Hello"
        draw_text.color: #fff
    }
}
```

### Step 6: Replace apply_over with script_eval

```rust
// OLD
self.label(id!(title)).apply_over(cx, live! {
    text: "New text"
});

// NEW
script_eval!(cx, {
    ui.title.set_text("New text")
});
// OR
script_apply_eval!(cx, self.ui, {
    title.text: "New text"
});
```

---

## Key Breaking Changes

1. **No commas** between properties (whitespace-delimited)
2. **No semicolons** anywhere in Splash
3. **No angle brackets** for widget types
4. **Theme constants** use `theme.*` prefix, not `(THEME_*)` syntax
5. **Named children** use `:=` operator, not `=`
6. **Merge operator** is `+:` not `:` for extending parent properties
7. **`height: Fit`** is MANDATORY on containers (default is 0px, not auto)
8. **Registration** happens in `App::run`, not `live_register`
9. **Field attribute** `#[source]` links to script object (required on some widgets)
10. **Old `old/` directory** contains archived 1.x code for reference

---

## Common Migration Mistakes

| Mistake | Symptom | Fix |
|---------|---------|-----|
| Still using `live_design!` | Compile error | Replace with `script_mod!` |
| Using `<Widget>` syntax | Parse error | Use `Widget{}` |
| Using `Key = Value` | Property not applied | Use `Key: value` |
| Using `(THEME_COLOR)` | Unknown token | Use `theme.color_*` |
| Missing `height: Fit` | Container invisible (0px) | Add `height: Fit` |
| Using `Live` derive | Compile error | Use `Script` |
| Using `before_apply` | Method not found | Use `on_before_apply` |
| Using commas between props | Parse error | Remove commas |

---

## Best Practices for Migration

1. **Start with examples** - Study `examples/counter` and `examples/todo` for 2.0 patterns
2. **Migrate one widget at a time** - Don't try to convert everything at once
3. **Check the old/ directory** - Compare old vs new widget implementations
4. **Test `height: Fit`** - Most invisible UI is caused by missing height
5. **Use theme variables** - Replace all hardcoded theme colors with `theme.*`
6. **Add `new_batch: true`** - Any View with `show_bg` and text children needs it
04

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeNA
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (1)

LOWInventory / provenance · inv.no_license · CWE-1104
Why it matters. no LICENSE file and no repo licence
Fix. add a licence

Gates applied: no_behavioural_pass, no_license.

Audited 2026-10-12 · audit v0.4.1 · source sha 7cbc563d4f32full audit observations/trust-audit/skill/zhanghandong__makepad-2.0-migration.json · Report an issue / request a re-scan
05

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-127cbc563d4f32SAFEB89first audit
06

Questions

What does the Makepad 2.0 Migration skill do?

Build App with Makepad and AI skills

Is Makepad 2.0 Migration safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can Makepad 2.0 Migration access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

Which assistants does Makepad 2.0 Migration work with?

Its documentation mentions cursor. That is what the text claims, not a compatibility test we ran.

How current is this page?

The grade is for one exact copy of the source (7cbc563d4f32), read on 2026-10-12. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement