gramlot.

Course · Lesson 14 of 20

Load a Source fragment

Use remote content when the server should build part of the interface.

Reading · Practice2 sectionsPrerequisites: Call an endpoint
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

Request structure, not just a scalar

A remote declaration asks a @source method to build a fragment. The returned Source becomes the content of the target element. This differs from an endpoint returning a number into Data.

Reactive parameters can request another fragment when the selection changes. Read the target, method and parameters together: they explain which part of the page is replaced and why.

Understand the request boundary

Authored children can appear until the first remote fragment arrives. _if controls readiness; a false condition makes no request and does not automatically erase existing content. Removing the target cancels its request.

Cached remote compares the method and serialized parameters with the relevant in-flight or last-mounted request. It is not a permanent cache of every record previously visited. A return to an earlier record may require another request.

Your turn

Try it yourself

  1. Open Remote and change the selection that drives its details pane.
  2. Identify the target branch in Source and compare the new fragment.
  3. Open Cached remote and follow its documented repeated-parameter experiment.

Check your understanding

If you only need a returned total, should the server build a whole Source fragment?

Show the answer and expected result

Usually a dataRpc returning a value expresses that task directly. Use remote for interface structure supplied by the server. Keep its replacement boundary small and understand the lifetime of the content it replaces.

Working examples and reference