Migration to new Rust-based engine (#401)

* wasm first steps * parsing start * parsing continued * progress * progress * progress * progress * progress * progress * progress * progress * fixes * reorganize * change type * fix * progress * refactoring * progress * progress * progress * keep style info * progress * progress * remove (copy) in name * progress * merge methods into 1 * splice * progress * progress * progress * cleaning * progress * progress * progress * visibility * progress * progress * progress * progress * progress * fixes * progress * fix markers * fix * progress * progress * progress * progress * progress * progress * small fix * use engine info * fix popups * small fix * progress * progress * progress * clean tool * handle self closing elements * reduce data exchanges across boundary * copy on wasm side to avoid any data corruption * speed fix * routing * refactoring * reverse * reverse * crop * split * merge * progress * time tool * fix bounds for waypoints * reduce * fix reactivity * handle corrupt time data * export * progress * remove gpx js package * remove todo * update readme * cleaning * progress * fix link fields * remove unused fields * refactoring and tests * import and export of routes, ref #192 * per-chunk categories storage * cross-tab sync * outdated state * refactoring * reorder methods * refactoring * fix * improve flow * renaming * progress * progress * fix * progress * per file history * keep original flag * use history variant * fix * progress * file explorer * progress * fix * sticky folders * improved sticky folders * fix sortable * fix sortable * fix * fix tab size * no file delete on desktop * fix routing on other file * fix sorting * remember language * open links in browser * commit missing changes * avoid selecting on resize * clarify filename * explorer actions * fix folder styling * drop anywhere in folder * cleaning * fixes * remove focus-ring * full screen * small fix * consistent highlight color * improved preview * performance improvements * sparser data transfers * sparser data transfers * show popup once data is loaded * fix routing control size * fix * sparse desktop build * remove custom ign styles * use new endpoint for openhikingmap * strip native menu * reorder context menu items * route full support * route - track conversion * create route file action * route export, filter out anchors at high zoom level * clarify name handling * move hide & center to view * routes continued * update docs * fix power format, closes #378 * lint fixes * fix display of additional data with gaps, closes #361 * fix linting issues * fix import modules * fix multidrag * change base to resolve * fix type errors * fix layer typings * fix last type error * each keys * improve typings * deploy to cloudflare --------- Co-authored-by: vcoppe <vcoppe@hexaly.com>
2026-11-01 20:19:39 +00:00 · 2026-10-31 18:08:22 +01:00
1 parent 6a0d434371
commit 8fe7d8d64d
@@ -16,7 +16,7 @@ This tool allows you to extract [tracks (or segments)](../gpx) from files (or tr
    <Extract class="text-foreground p-3 border rounded-md shadow-lg" />
 </div>

-Applying the tool to a file containing multiple tracks will create a new file for each of the tracks it contains.
+Applying the tool to a file containing multiple [tracks or routes](../gpx) will create a new file for each of the tracks and routes it contains.
 Similarly, applying the tool to a track containing multiple segments will create (in the same file) a new track for each of the segments it contains.

 <DocsNote>
@@ -10,11 +10,11 @@ title: Merge

 # <Group size="24" class="inline-block" style="margin-bottom: 5px" /> { title }

-To use this tool, you need to [select](../files-and-stats) multiple files, [tracks, or segments](../gpx).
+To use this tool, you need to [select](../files-and-stats) multiple files, [tracks, segments or routes](../gpx).

 - If your goal is to create a single continuous trace from your selection, use the **Connect the traces** option and validate.
- The second option can be used to create or manage files with multiple [tracks or segments](../gpx).
-Merging files (or tracks) will result in a single file (or track) containing all tracks (or segments) from the selection.
+- The second option can be used to create or manage files with multiple [tracks, segments or routes](../gpx).
+Merging files (or tracks) will result in a single file (or track) containing all tracks and routes (or segments) from the selection.

 <DocsNote>

@@ -27,6 +27,6 @@ To split the selected trace into two parts, click on one of the split markers di
 To split at a specific point of your choice, hover over the trace on the map.
 Scissors will appear at the cursor position, showing that you can split the trace at that point.

-You can choose to split the trace into two GPX files, or to keep the split parts in the same file as [tracks or segments](../gpx).
+You can choose to split the trace into two GPX files, or to keep the split parts in the same file as [tracks, segments or routes](../gpx).

 <DocsImage src="tools/split" alt="Hovering over the selected trace turns your cursor into scissors." />