Baton Manual

Chapter 2

The screen

A phone shows one thing at a time, so Baton puts the request you are working on in front and everything else in a drawer. The request fills the top half, its response the bottom half, and the drawer slides in from the left with the workspace, the collections and the state of sync.

A request, sent, with its response under it. — 1: The drawer: workspaces, collections, status; 2: Reload, save, and the active environment; 3: Open requests, a tab each; 4: The request: method, URL, Send and its tabs; 5: The response, under the request
  1. The drawer: workspaces, collections, status
  2. Reload, save, and the active environment
  3. Open requests, a tab each
  4. The request: method, URL, Send and its tabs
  5. The response, under the request
Figure 2: A request, sent, with its response under it.

1 opens the drawer. 2 re-reads the request from its file, saves it, and shows the active environment. 3 is the requests you have open, one tab each. 4 is the request itself — method, URL, Send, and the tabs under them. 5 is the response panel, which also holds what was actually sent, the console, the history and saved examples.

2.1The drawer

The drawer, top to bottom. — 1: Switch or create a workspace; 2: Active environment; 3: New collection, or import; 4: Search, or run a command; 5: A collection — tap to fold
  1. Switch or create a workspace
  2. Active environment
  3. New collection, or import
  4. Search, or run a command
  5. A collection — tap to fold
Figure 3: The drawer, top to bottom.

The workspace name 1 opens the list of workspaces and the way to add one. The chip beside it 2 is the active environment: every {{variable}} in every request resolves against whichever one is selected here — the chip in the top bar only shows it. 3 adds a collection or imports one. 4 searches every request and runs commands. A collection header 5 folds and unfolds; tapping a request opens it and closes the drawer, and the ⋯ beside a collection or a request opens its menu.

2.2Search and commands

Search lists every request, and runs things too. — 1: Type part of a name; 2: Every request, with its collection
  1. Type part of a name
  2. Every request, with its collection
Figure 4: Search lists every request, and runs things too.

Typing into 1 narrows the list to requests whose name matches. 2 is every request with the collection it belongs to, including ones inside folded folders. Further down, the list offers to run a whole collection and to jump to the variables and secrets of the active environment.

2.3The status rows

Each state, with the action that changes it. — 1: Connect a repository; 2: Pair a worker; 3: License state — only in the build from the site
  1. Connect a repository
  2. Pair a worker
  3. License state — only in the build from the site
Figure 5: Each state, with the action that changes it.

The rows at the foot of the drawer are buttons. 1 opens git sync and 2 worker pairing. 3 is the license, and it is there only in the build from the site, which these screenshots come from: the apps from the App Store and Google Play have no license row, because the store handles the purchase (Section 15).