0 Fork 0

mirror of https://github.com/vicliu624/trail-mate.git synced 2026-11-11 14:47:39 +00:00

Files

T

Trail Mate Dev 6e613e382e Add CM0 Linux support and share device services across platforms

Compose the CM0 fullscreen application and standard Debian package, align the
Cardputer Zero shell, and share protocol, configuration, audio and storage
services with embedded targets through existing platform seams.

Add the paginated on-device TMAP creator using Center's published producer,
private workspace recovery and direct keyboard shortcuts. Preserve unfinished
management work behind its existing opt-in capability.

Include native, ARM and shared-core regression fixtures, integration records,
packaging helpers and dependency/license updates. Keep local build trees,
device credentials, produced packages and validation logs outside version control.

Validation before integration: ESP stack hygiene, Reticulum scope guard, staged
whitespace checks and GitNexus scope audit. Prior device/build evidence and
remaining hardware/package boundaries are recorded in the acceptance documents.

2026-10-29 10:29:29 +08:00

8.2 KiB

Raw Blame History

On-device TMAP creation

CM0 and Cardputer Zero expose Extensions → Make TMAP directly in the bottom action bar, without opening Menu. It also opens directly with T while on Extensions; the button displays T Make TMAP and H Help lists the shortcut. Text editors keep literal T input. The shared LVGL wizard uses seven pages: local PBF source, WGS84 bounds, layers/zoom, map identity, output/revision/budget, review, and progress/result. Touch text editing and keyboard focus navigation use the existing shared UI contracts. Read-only text panels can be scrolled with arrow keys. Closing the page leaves a job running; Cancel stops it. Reopening the entry shows the current job, and a completed job offers New map.

Sources and outputs

Put a local .osm.pbf file in map-sources beneath the application's configured storage root. The source page displays that actual directory. Refresh scans in the background and updates the list when finished. maps/sources and an explicit TRAIL_MATE_TMAP_SOURCE_ROOT override are also supported. The wizard does not download regional PBF extracts or infer a boundary from a country name. Enter explicit bounds and split areas crossing the antimeridian.

OSM, terrain and satellite layers use Center's existing PBF rendering and raster sources. Terrain and satellite may fetch source data over the system network. Their source cache belongs to the private job workspace and is deleted with it after success, failure or cancellation. POI, search and independent labels are retained in the authoritative OSM package, including when only another raster layer is requested. The current wizard produces Center's display/search TMAP profile; the separate experimental navigation/region-production CLI and contour production are not new wizard modes.

Completed files use the existing maps/tmap/osm, terrain and satellite layout. Referenced font resources are installed before their maps. The normal map catalog's existing directory/file watcher discovers newly published maps. Existing map filenames are refused; select another name instead of silently replacing a map. Keep a package key stable for updates to the same region and choose its revision explicitly.

For the default CM0 desktop session, the source directory is /home/pi/.local/share/trailmate/map-sources. The page's displayed path is authoritative if XDG or application storage overrides are configured. For example, copy area.osm.pbf there, open Extensions → Make TMAP and select Refresh. Bounds are WGS84 decimal degrees: West/South/East/North, with negative numbers for western longitudes and southern latitudes. For a small example, enter 102.70, 25.00, 102.71, 25.01 respectively, provided the PBF covers it. Start with OSM and zoom 13–14. Give the map a name, a simple package key such as test-area, filename test-area.tmap, revision 1 and an appropriate output limit. Review the estimate and start creation. After success, return to Map → Map Layer and choose the produced base layer, move to the covered region and use a zoom in the produced range. No manual output copy or separate import is required.

Only the original PBF and final map resources need to remain after a normal job. Final output includes the .tmap files and any referenced resources under trailmate/packs/fonts; deleting those fonts can break map labels. Plans, temporary indexes, raster downloads and staging output belong to the private workspace and are removed after success, failure or cancellation. Center's geometry and font-summary JSON reports are not installed as map payloads. The app installation/runtime, its regular settings and unrelated map caches are separate from creator intermediates.

Interrupted jobs are recovered automatically on service startup. Producer work and publication staging both live beneath the configured storage root's private trailmate/.tmap-jobs/job-XXXXXX directories. The namespace has a checked ownership record and a process lease. Recovery only removes job directories in that marked namespace, traverses relative to directory descriptors without following symlinks, and never scans input PBF or final map directories for deletion. It preserves unknown siblings and refuses unmarked nonempty namespaces. A small .owner control file remains; it is not a retained rendering cache.

The producer inherits the lease. If the app dies while its producer is still alive, a newly started service waits and retries recovery every two seconds until that process releases the lease. After power restoration the lease is released by the OS and abandoned work is recovered on startup. Files already published as final maps/fonts remain intact; recovery does not roll back published outputs. Legacy unmarked cache folders or generic .creating files from older versions are not blindly deleted because their ownership cannot be proved. This version no longer creates generic staging files beside final maps.

Estimates count uncompressed RGB565 tiles and conservative working space. Indexes, font resources, geometry complexity and actual source processing affect final size and duration; deduplication can reduce pixels. The producer enforces output and free-space budgets again before processing. A failed/cancelled job discards its private workspace and rolls back only files created by that job.

Ownership and reuse

The application does not fork the TMAP writer, OSM importer, renderer or search index format. LinuxTmapCreation invokes the existing Center TmapTool in a separate process, using a captured PBF descriptor, a private JSON plan, copied progress and fixed build/verify commands. Center Core owns production and format verification; the existing independent TMAP SDK remains the device reader.

The portable tmap_creation::Service seam contains plans/status only. Composition registers the Linux worker for CM0's tmap_creation=true profile and Cardputer's startup. Unsupported ESP32/nRF targets have no registered producer, hidden entry and no producer thread/runtime dependency. Other Linux compositions must opt in. All filesystem scans, rendering, copying and child-process control run off the UI thread. One job owns its state, and storage publication uses descriptor-rooted I/O, an exclusive storage lease and no-replace publication.

Producer packaging

Publish the existing Center project for the target; do not copy its source into the firmware repository:

./tools/publish_tmap_producer.ps1 -CenterRoot ../trail-mate-center `
  -OutputDirectory ./build/tmap-producer/linux-arm -Runtime linux-arm

Use linux-arm for CM0, linux-arm64 for the Cardputer package builder, and linux-x64 for native integration tests. The self-contained output includes its runtime, Skia assets, Center license and a producer/hash manifest. CMake's TRAIL_MATE_TMAP_PRODUCER_DIR installs it under /usr/lib/trailmate/tmap-producer and checks its architecture. CM0 and Cardputer package metadata include their distribution's ICU dependency when bundling this producer. No .NET SDK or Center checkout is required on the device. An explicit TRAIL_MATE_TMAP_PRODUCER executable override is available for development.

The Debian Lintian overrides are restricted to SkiaSharp's bundled raster codecs and the published SQLite native asset's debug symbols. These upstream runtime binaries are preserved so their hashes continue to match the producer manifest.

The Cardputer build_cardputer_zero_deb.sh helper also accepts TRAIL_MATE_TMAP_PRODUCER_DIR and transfers the published bundle to its existing ARM64 Docker builder. A developer build without a bundle reports an unavailable producer; it cannot claim a working production creator.

Validation

Native contract cases cover invalid plans, budget refusal, single-job ownership, producer failure, cancellation, workspace cleanup and preservation of an existing destination. A small real OSM PBF is processed by the published Center producer; the resulting map is independently discovered/read by the application's TMAP SDK and its POI is found through the normal map-search runtime. Both 1232×568 and 320×170 wizard tests cover every step, form preservation, background continuation, cancellation and unsupported-service behavior. Release/device results are recorded in the CM0 acceptance audit after those checks run.

8.2 KiB Raw Blame History Unescape Escape