| Age | Commit message (Collapse) | Author |
|
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.
|
|
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 flpsed.org site is generated statically; keeping the deployable
bundle in the tree lets the site pipeline pick it up directly.
Regenerate with crates/wipfel/build-release.sh.
|