CatpileDocs
Language Reference

Multi-Script Projects

A single .cat file can define multiple CatWeb scripts using the script directive. This keeps code organized while producing multiple CatWeb scripts.

#
python
script "movement":
    on loaded:
        initBoard()

    fn initBoard():
        createTable("items")

script "utils":
    on loaded:
        log("Utilities loaded")

Each script block produces a separate entry in the compiled JSON output.

#

When used with the Catpile editor, scripts are placed under their parent UI elements in the VFS tree. The compiler merges compiled scripts back into the correct position using alias matching.

#

Each script block is compiled independently:

bash
cpile site.cat -o output.json

The output contains one array entry per script:

json
[
  {"class": "script", "alias": "movement", "content": [...], "globalid": "..."},
  {"class": "script", "alias": "utils", "content": [...], "globalid": "..."}
]
#

When importing and recompiling a CatWeb page, the editor:

  1. Decompiles the page to .cat files (one per script)
  2. Stores UI element data in the VFS
  3. On "Full Project" compile, sends all scripts to the API
  4. Merges compiled scripts back into the UI tree
  5. Returns complete page JSON with {favicon, webcontent, title, background}
#

Page properties (favicon, title, background, description, thumbnail_id) are preserved during import and re-included in compiled output.

json
{
  "favicon": "122781995056465",
  "title": "[W.I.P] Catpile Demo",
  "background": "#323232",
  "webcontent": [
    {"class": "script", "alias": "movement", "content": [...]},
    {"class": "Frame", "globalid": "myFrame", "size": "{0.5,0},{0.5,0}"}
  ]
}
#

The .catui file maps element paths to global IDs:

json
{
  "paths": {
    "Page.FileLoader": "5s",
    "Page.FileLoader.Load": "@<",
    "Page.FileLoader.FileInput": "2\""
  },
  "tree": [...],
  "ui": [...]
}

Generated by the decompiler. Used by the compiler to resolve page. references.