gramlot.

Course · Lesson 19 of 20

Deliver the JavaScript edition offline

Open a complete export from disk and test what still needs a connection.

Reading · Practice2 sectionsPrerequisites: Read the JavaScript edition
Course contents
Orientation
  1. 01 Install Gramlot and create Hello world
  2. 02 Connect text and colour to Data
  3. 03 Explore Data and Source with the inspector
  4. 04 Use relative and symbolic paths, then dataFormula
  5. 05 Call the server with dataRpc and .remote
Start a project
  1. 01 Create your first project
  2. 02 Read and compose Source
  3. 03 Initialize structured Data
  4. 04 Connect fields and values
Build a form
  1. 05 Accept values, preserve drafts
  2. 06 Declare a calculation
  3. 07 Run an action at the right time
  4. 08 Name behavior and understand lifecycle
Compose an interface
  1. 09 Arrange an application with containers
  2. 10 Style the page you own
  3. 11 Publish messages and ask before acting
  4. 12 Format values without changing Data
Connect services
  1. 13 Call an endpoint
  2. 14 Load a Source fragment
  3. 15 Load Data when it is read
  4. 16 Save, restore and send Data deliberately
Deliver your work
  1. 17 Organize pages and choose a host
  2. 18 Read the JavaScript edition
  3. 19 Deliver the JavaScript edition offline
  4. 20 Explain and change a complete form

The Worker supplies the Page

The serverless edition packages JavaScript Pages and their runtime. A Worker executes Page-side behavior; the window renders the interface and runs Logic. Users opening an already built export need a browser, not a Python or Node.js application server.

Download the maintained gallery ZIP from the serverless page, extract the entire folder and open index.html. Keep its supporting assets with it. Exporting your own project is a separate build step described by the JavaScript server repository.

Test the real offline boundary

After extracting, disconnect the network and open a simple example. Follow its Data updates. Then identify any features that would call external services, load remote resources or require authenticated business data.

An external endpoint remains external. Offline execution does not automatically queue submissions or reconcile later changes. The delivery workflow from lesson 16 is still an application responsibility.

Your turn

Try it yourself

  1. Download the gallery ZIP and extract all files.
  2. Disconnect networking, open index.html from the extracted folder and try a bound input.
  3. Reconnect and list which parts of your proposed application would need an external service.

Check your understanding

What does a successful offline binding test prove?

Show the answer and expected result

It shows that the packaged page and its local runtime can handle that interaction without a server connection. It does not prove persistence, synchronization, external-service access or that a Python Page can run in the Worker.

Working examples and reference