gramlot.

Course · Lesson 18 of 20

Read the JavaScript edition

Transfer your understanding of Source and Data to a Page authored for Node.js or Bun.

Reading · Practice2 sectionsPrerequisites: Organize pages and choose a host
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

Keep the model; check the syntax

A JavaScript Page still builds Source, refers to Data paths and names browser Logic. Use the JavaScript gallery to compare the same example with its Python counterpart. Server-side JavaScript Page methods and browser Logic still run in separate contexts.

The current published JavaScript data declarations use object arguments. Do not assume that Python’s positional dataFormula signature is implemented in JavaScript. Compare the actual maintained source instead of inventing a compatibility wrapper.

Start from the maintained scaffold

Use the JavaScript server’s setup guide for Node.js or Bun. It owns the current package commands, scaffold and startup instructions. The website’s Python download is not a JavaScript project.

First reproduce the same simple binding. Once the Data path and trigger are understood, compare a formula and a named Logic method. The language change should not obscure the server/browser boundary.

Your turn

Try it yourself

  1. Open b04 in both hosted galleries and compare the field’s binding.
  2. Compare c01 in both languages and locate the result path and reactive arguments.
  3. Follow the JavaScript setup guide if you want to run that edition locally; keep it in a separate project.

Check your understanding

Can the fact that both files use JavaScript tell you whether a method runs on the server?

Show the answer and expected result

No. Page code belongs to the server or Worker, while Logic runs in the browser. Check the module’s role and the host. The same language does not imply shared object state or a single execution context.

Working examples and reference