| Age | Commit message (Collapse) | Author |
|
The 35mm film frame is 36 mm wide, so a lens with 35mm-equivalent
focal length f projects with focal length f*w/36 in pixels. The
original C++ code divided by 35, making the EXIF-derived initial
scale ~2.9% too large (and the fitted focal readout ~2.9% low).
- EXIF init and the focal slider/readout in both apps now use /36
- the gipfel JPEG comment KEEPS its historical scale*35/w encoding
(focal_from_comment flag), so annotated JPEGs written by any older
gipfel version still reproduce the identical view, and files saved
by this version remain readable by them
- new regression test focal_scale_exif_vs_comment; golden tests
untouched (they pin the comment path)
|
|
All colors moved into CSS custom properties on :root (dark default)
with a prefers-color-scheme: light override block. The two canvas-
drawn surfaces follow too: the viewport now clears transparent so the
CSS canvas background shows through, and the compass strip reads its
colors from the same variables via a new bridge::css_var helper.
theme-color metas (dark + light variants) tint mobile browser chrome
to match.
|
|
Appearing between Display and Track it pushed the whole Track block
down on every hover. As the last item before the bottom-pinned info
texts the flexible spacer absorbs it — nothing jumps anymore.
|
|
The 'web gipfel photogrammetry' tag under the title now links to
flpsed.org/gipfel.html (grey like plain text, accent blue on hover);
the separate 'More information…' row is gone. Hover readout uses the
desktop phrasing: 'Name · 2849 m · distance 12.34 km'.
|
|
hover distance
- control panel starts open on all screen sizes (so the image picker is
reachable on phones); it auto-collapses on narrow screens once an
image is loaded
- 'Fit to window' and the whole Track section only appear when an image
is loaded
- Track section moved directly below Display, above the pinned info
texts (which now carry the margin-top: auto)
- hover readout shows the distance to the peak in km, matching the
desktop format 'name · height m · dist km'
|
|
One text field accepting '47.676,13.32042' (optionally ',alt' as a
third component; commas, semicolons or spaces as separators) — the
format gallery apps show, so the coordinates can simply be copied and
pasted. This replaces the PWA/share-target detour for getting a
viewpoint onto mobile: EXIF GPS may be redacted by the OS, but the
gallery displays the true coordinates for manual transfer.
|
|
This reverts commit 2df51e89039b9b160aafb52b700e874411eb0555.
|
|
- manifest.webmanifest: standalone, dark theme, mountain icons
(regular + maskable)
- sw.js: network-first with cache fallback -> full offline after first
visit (wasm + hill DB included); versioned cache, stale caches pruned
- share_target: images shared to the installed app are POSTed to
__share; the SW stashes the bytes at __shared and redirects with
?shared=1; the app picks them up on startup and cleans the URL
- index.html: manifest link, theme-color, icons, SW registration
- build/serve scripts ship the new files; dist refreshed
Note: sharing does not bypass AOSP GPS redaction when the share source
passes a MediaStore URI (the browser is still the reader) — the
.nomedia/rename trick remains the way to get GPS EXIF into a browser.
|
|
Thin wrapper so wipfel can read original photo bytes: browsers cannot
declare ACCESS_MEDIA_LOCATION, so the OS always redacts GPS EXIF from
images they read. Our own app declares and requests it (plus
READ_MEDIA_IMAGES) and gets the intact files.
- WebView served from a loopback AssetServer (fetch/WASM need a real
HTTP origin; file:// is blocked)
- file picker wired through WebChromeClient (accepts any file type)
- zero androidx dependencies, plain Activity, minSdk 29
- build.sh: wasm release site -> assets -> assembleDebug (~3MB APK)
- loader: fall back to plain gipfel.dat (aapt gunzips .gz assets)
|
|
MediaProvider only redacts GPS EXIF in files it indexes as images.
A copy renamed to a non-image extension (or under a .nomedia folder)
reaches the browser untouched — an all-files picker makes that route
usable on GrapheneOS/AOSP where browsers cannot hold
ACCESS_MEDIA_LOCATION.
|
|
A UseStateHandle cloned into a callback derefs to its render-time
snapshot (documented Yew behaviour). Pinch emitted zoom and pan as two
separate read-modify-writes per event: both read the same stale
snapshot, so the pan write reverted the zoom write on every event and
the scale never moved. Wheel zoom survived because it emits alone with
a render between events.
Fix: keep the authoritative ViewState in a use_mut_ref mirror with an
apply_view helper (read live, mutate, write mirror + use_state), and
fold pinch zoom+pan into a single combined update. Removes all the
pinch diagnostic probes (debug callback, event counters, build stamp).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The overlay was suppressed whenever the panel was open — but Firefox
on Android defaults to desktop-site mode, which reports a 980px
viewport and thus keeps the panel open on phones. The overlay now
always shows (it doubles as the pinch-diagnostic readout), and the
initial status carries a build stamp so a stale cached page is
recognizable at a glance.
|
|
serve-here.sh only refreshed style.css and the wasm bundle, so the
viewport meta change that frees the pinch gesture for the app never
reached the served page. Copy the loader page as well, and surface
the status line as a small overlay over the canvas when the control
panel is collapsed (mobile) — this is also where the pinch pointer
diagnostics become visible on phones.
|
|
Second data point needed for the mobile pinch issue: the status line
now shows pointer activity (pointerdown id/pts, pointercancel id/pts,
pinch distance) so it is visible on the phone whether the second
pointer arrives at all or whether the browser cancels pointers when
pinching. Also: only capture the primary pointer (capturing every
finger confuses some mobile browsers), and pointercancel now removes
just that pointer instead of clearing the table — a browser that
'cancels' finger one as finger two lands no longer makes pinch
impossible to form.
|
|
Firefox on Android may consume two-finger pinch for page zooming
despite touch-action: none on the canvas. Disable page zooming via
the viewport meta (maximum-scale=1, user-scalable=no) so the gesture
reaches the app as pointer events; the app provides its own zoom.
Also join touch pointers seen only via pointermove into the pointer
table, so a swallowed second pointerdown cannot break pinch.
|
|
- two-finger pinch on the viewport canvas: pointer table tracks all
active pointers; pinch emits zoom anchored at the finger midpoint
plus pan by the midpoint delta; a second finger cancels an in-flight
pan/marker drag, the remaining finger resumes panning, and pinch
gestures never fire a click
- 100dvh (with 100vh fallback) for the app shell: on mobile browsers
100vh includes the area behind the dynamic URL bar, which pushed
the compass strip below the visible fold
- file input accepts image/* so Android pickers offer all photos and
transcode exotic formats (HEIC) to decodable ones
|
|
The ResizeObserver only re-fit the image; with user_moved set (after
any manual pan/zoom) it did nothing, so the canvas backing store kept
its old dimensions and the browser stretched the stale bitmap —
visible distortion on sidebar collapse and window resize. The
observer now always bumps the redraw tick (backing store resyncs in
the draw effect, compass included) and re-fits additionally when the
view has not been moved by hand.
|
|
|
|
|
|
'Load GPX Track…' and the Track width slider now live in their own
Track section below everything else, held at the bottom of the
sidebar via margin-top: auto.
|
|
- port of the desktop bump() lens-FOV clamp: max_view_angle is the
angle at which the (distorted) projection reaches the image edge;
peaks beyond it cannot be inside the photo even when the fitted
distortion folds their projection back into the image. Recomputed
each render (idempotent, only rebuilds visibility on change) — this
is what let impossible peaks show up at high visibility settings
- 'Load GPX Track…' moved from the top into the Display section next
to the Track width slider (optional, advanced)
- collapsible control panel: collapse button in the sidebar corner,
floating hamburger button over the canvas when hidden; starts
collapsed on viewports narrower than 900px
|
|
- core: track::load_gpx_from_bytes (path wrapper delegates to it;
same hardening: size cap, no entity expansion, direct-child <ele>)
- sidebar: 'Load GPX Track…' button + hidden .gpx file input; the
track swaps in via remove_hills(FLAG_TRACK_POINT) + add_hills, so
marker hill indices never shift (track hills always live at the end
of the hill list)
- rendering: desktop parity — consecutive visible points joined with
round-cap strokes, width = scale*track_width/(dist_m*10) clamped
to [1,1000] image px, red (blue when hidden by terrain); a Track
width slider (50-1000 m, default 200) appears in Display once a
track is loaded
- track points and duplicates are excluded from guide dots, hover and
click hit-testing (they are scenery, not markable peaks)
|
|
The desktop lays out labels in alpha-descending order (the C
pointer-array sort), which on screen means right to left — so the
leftmost peak of a collision cluster ends up on top of the stack.
The web port sorted by screen x ascending, inverting every stack and
making labels look assigned to the wrong peaks. Sort descending; the
break-early scan in layout_label_y stays valid because it only relies
on monotonic x, and labels extend rightward just like in C.
Verified against the desktop rendering of the same panorama photo and
a right-to-left replay of the layout in the label simulator.
|
|
The C++ original draws a cross + vertical + horizontal leader for
every labeled peak, not just marked ones. Without them, collision-
pushed peak labels float unattached and it is impossible to tell
which dot they belong to (verified by replaying layout_label_y on a
synthetic ridge scene). Peak leaders use the muted pale green of the
label text; marker leaders stay yellow with the small cross.
|
|
Display > 'Show peak labels' toggle (off by default): every visible
peak gets its name drawn next to its guide dot, like the desktop
version. Labels join one combined collision-avoidance layout pass with
the marker labels (same layout_label_y), so marker labels keep
priority and nothing overlaps. Unmarked labels are tinted pale green;
hidden peaks and already-marked peaks get no duplicate label.
Candidates now carry name + marked flag (DotView), markers carry the
hill index (MarkerView::hill) for the dedup.
|
|
The fit at load time (and the 120 ms nudge) could still run before the
canvas had a valid layout size, leaving the first image invisible until
'Fit to window' was pressed. A ResizeObserver attached when the first
bitmap arrives fires once with the element's real size immediately
after observing, then on every later resize; it re-fits automatically
unless the user has panned or zoomed by hand since the last load
(user_moved flag, reset on each image load). Window resizes now
re-fit the image as well instead of only redrawing it.
|
|
'gipfel web' is taken by an existing related project. The browser app
is now wipfel — web based gipfel photogrammetry for mountain images:
crate gipfel-web -> wipfel, updated titles, docs, plan and dev script.
The shared engine crate stays gipfel-core.
|