spw.quest

Pivot a line

Change one slot, keep the rest, and see the line before you go. Forms, side by side shows what each slot does.

The line

builder{tune.serialize}(living-component)

a line you wrote

  • new
subject
builder
body
tune.serialize
scope
living-component

An operator in front

  1. ~
  2. ?
  3. !
  4. *
  5. .
  6. ^
  7. #
  8. @
  9. &
  10. =
  11. %
  12. $
Add to what it holds

Back to builder[living-component]{tune.serialize}

Families it belongs to

Other lines about builder

31 lines one change away

Drop a slot to read what the line says without it.

near: a line sharing a slot uses it · common: common on the shelf

charge the charge in front

  1. boon builder{tune.serialize}(living-component)

    add boon

    • add
    lands
    Not on the shelf yet.
    why
    a valence word rides the word

subject the word

  1. folio{tune.serialize}(living-component)

    swap to folio

    • swap
    • common
    lands
    Not on the shelf yet.
  2. theory{tune.serialize}(living-component)

    swap to theory

    • swap
    • common
    lands
    Not on the shelf yet.
  3. principle{tune.serialize}(living-component)

    swap to principle

    • swap
    • common
    lands
    Not on the shelf yet.
  4. practice{tune.serialize}(living-component)

    swap to practice

    • swap
    • common
    lands
    Not on the shelf yet.
  5. ?builder{tune.serialize}(living-component)

    ? wonder in front

    • mark
    lands
    Not on the shelf yet.
  6. ~builder{tune.serialize}(living-component)

    ~ potential in front

    • mark
    lands
    Not on the shelf yet.
  7. ^builder{tune.serialize}(living-component)

    ^ ascension in front

    • mark
    lands
    Not on the shelf yet.
  8. &builder{tune.serialize}(living-component)

    & subject in front

    • mark
    lands
    Not on the shelf yet.
  9. $builder{tune.serialize}(living-component)

    $ substrate in front

    • mark
    lands
    Not on the shelf yet.

mode the lens

  1. builder[character-card]{tune.serialize}(living-component)

    add character-card

    • add
    • near
    lands
    Not on the shelf yet.
  2. builder[living-component]{tune.serialize}(living-component)

    add living-component

    • add
    • near
    lands
    Not on the shelf yet.
  3. builder[profile]{tune.serialize}(living-component)

    add profile

    • add
    • near
    lands
    Not on the shelf yet.
  4. builder[prompt-packet]{tune.serialize}(living-component)

    add prompt-packet

    • add
    • near
    lands
    Not on the shelf yet.

body what it holds

  1. builder{slot.identity}(living-component)

    swap to slot.identity

    • swap
    • near
    lands
    Not on the shelf yet.
  2. builder{context.surface}(living-component)

    swap to context.surface

    • swap
    • near
    lands
    Not on the shelf yet.
  3. builder{material.image}(living-component)

    swap to material.image

    • swap
    • near
    lands
    Not on the shelf yet.
  4. builder{keep.share}(living-component)

    swap to keep.share

    • swap
    • near
    lands
    Not on the shelf yet.
  5. builder(living-component)

    drop what it holds

    • drop
    lands
    Not on the shelf yet.
  6. builder(living-component)<tune.serialize>

    turn its walls to < >

    • walls
    lands
    Not on the shelf yet.
    why
    what it holds becomes where it goes
  7. builder[tune.serialize](living-component)

    turn its walls to [ ]

    • walls
    lands
    Not on the shelf yet.
    why
    what it holds becomes the lens
  8. builder{tune,serialize}(living-component)

    hold the parts together

    • turn
    lands
    Not on the shelf yet.
    why
    commas keep parts apart and present at once
  9. builder{tune;serialize}(living-component)

    hold the parts in order

    • turn
    lands
    Not on the shelf yet.
    why
    semicolons put the parts in a sequence
  10. builder{tune ~> serialize}(living-component)

    make the parts a path

    • turn
    lands
    Not on the shelf yet.
    why
    ~> carries each part on to the next without collapsing them

scope the scene

  1. builder{tune.serialize}(year)

    swap to year

    • swap
    • common
    lands
    Not on the shelf yet.
  2. builder{tune.serialize}(runtime)

    swap to runtime

    • swap
    • common
    lands
    Not on the shelf yet.
  3. builder{tune.serialize}

    drop the scene

    • drop
    lands
    Not on the shelf yet.
  4. builder{tune.serialize}<living-component>

    turn its walls to < >

    • walls
    lands
    Not on the shelf yet.
    why
    the scene becomes where it goes
  5. builder[living-component]{tune.serialize}

    turn its walls to [ ]

    • walls
    lands
    On the shelf: spwashi.com/design/components/#specimen-builder-rail.
    why
    the scene becomes the lens

projection where it goes

  1. builder{tune.serialize}(living-component)<receipt>

    add receipt

    • add
    • common
    lands
    Not on the shelf yet.
  2. builder{tune.serialize}(living-component)<china>

    add china

    • add
    • common
    lands
    Not on the shelf yet.

Constructs · Specimens · Take one line apart · Learn it a mark at a time