Skip to content

Bridge 0.17.0

Latest

Choose a tag to compare

@github-actions github-actions released this 14 Oct 05:58
· 29 commits to main since this release

Bridge 0.17.0 adds users, roles, project management and the optional team hub with its browser dashboard (the first slice of requirements 4 to 7). It also makes checking elective, so Greek Room runs only when asked, and lets Bridge install its own Paratext connector. The workbench database moves to v9 and the workspace database to v5, both by forward migration. The semantic database stays at v16. No translationCore project file changes shape.

This is the build for the field-laptop measurements (#232) and the two-laptop LAN walk (#281).

Choose the checks a run includes; Greek Room on demand (#251, #252)

A Checks ▾ menu in the editor toolbar has six boxes: Translation Notes, Translation Words, Alignment, USFM and text, Language QA and Greek Room. The selection is saved per installation and defaults to all but Greek Room. Opening a chapter, the re-check after an edit, Run chapter and Run whole book all use it, and the engine now runs only the ticked checks. Greek Room (Wildebeest, the USFM structural checker and names spelling) no longer runs on chapter open, after an edit or on verse selection. Run it from the Review panel for the verse, or from the Checks menu for the verse, the chapter or the book; it runs last, with progress and Cancel. A run of some checks keeps the other checks' findings. A verse's ✓ means every selected check ran clean, and its title says what ran and "Greek Room not run". Collection QA has its own boxes, with Greek Room on by default.

Measured on the Tamil IRV Luke fixture, on a development machine:

Run 0.16.0 0.17.0
First chapter of a session 16.1 s 11.7 s
A later chapter 1.19 s 0.10 s
Re-check after an edit (median) 24 ms 2 ms

Users, roles and project management (#236, #237, #238, #239, #240, #182)

  • Users and roles: a startup name picker and Settings › Users. There are three roles, and one authorization rule runs before every engine method. Every write carries the chosen user.
  • Projects list: progress columns, last opened by, rename, archive and unarchive.
  • Assignments: assign a book or a chapter to a user. The dashboard has "My work", and assigned chapters carry a ● mark.
  • Progress: aligned verses and Language QA are counted on the totals.

The team hub and dashboard, first slice (#79, #80, #81)

  • The hub: an optional sync peer on the local network (--serve, a pip [server] extra). It uses join codes and device tokens, pushes and pulls review state, and keeps a conflict queue. The desktop never waits on it.
  • The dashboard: a browser page the hub serves, with team progress, users and assignments.
  • Not yet tested on two machines: that walk is #281.

Bridge installs its own Paratext connector (#282, Benz)

The installer offers to install the connector when Paratext 9 is present, and Settings › Connections has Install or Update Paratext connector. Both compile the connector on the user's PC and ask for one UAC prompt. Bridge → Paratext and Logos navigation works again (#110).

Also in this release (Benz)

  • Language QA: requirement 3's coverage target is met: 20 framework items Checked and 20 Not checked (#253–#270). Every finding is drawn behind the Settings slider, with Why in the menu (#250). A live pass updates the dashboard's clean count (#280).
  • Source text panel: a side panel shows the source text beside the translation (#67).
  • Cross-verse: the pass is shown from the job status, with a plain provider-timeout message (#243). Rows M50, M51 and M59 pass on the installed 0.16.0 (#159).
  • Engine: a never-opened sibling book is prepared on a worker (#210).

Responsiveness table

Not yet measured on the reference laptop (Intel Core i3-1115G4, 2 cores, 8 GB, 1366x768). It is measured on this build on 15 October and added here (#232).

Known

  • Not yet seen on the installed desktop: the Checks menu and Greek Room on demand (QA matrix M61, M62), users and roles, the hub and the dashboard (#281).
  • CI's Language QA latency gate failed once on 99aa9ab. verse.decide (languageQa) measured p95 530 ms over 10 samples against a 300 ms budget. The same gate passed on the five later runs.