file preview, which never worked here and had to be built rather than fixed

on /files the viewer is NOT part of the file browser. `useFileViewerPanels` lives on
the SCREEN and swaps the whole workspace layout when `?view=` appears, opening a
viewer panel beside the browser. a plugin renders its own defaultLayout and has no
such hook — so double-clicking a file in this panel set `?view=` and nothing on earth
read it.

which means it never worked here. it LOOKED like it did for one deploy, because
`urlPath` was navigating to /files, where that screen did the work — so the bug I
introduced and then removed is the only reason anybody saw a preview.

the panel reads `?view=` itself now and renders FileViewerView, which the platform
exports for exactly this. OVER the browser rather than beside it: this panel is one
column of a two-column screen, and splitting it again would give a preview the width
of a phone.

closing clears `view` and `viewRoot` and leaves `media` alone, so you land back in
the folder you were in rather than at the top.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

pastilhas

2026-08-29 09:19:11 +01:00

co-authored by

Claude Opus 5

parent 21935cbc27

commit 1d820fc9d4

2 changed files with 38 additions and 2 deletions

									
										manifest.ts
									
		+1
		-1
	
												View File
												
				@@ -35,7 +35,7 @@ import type { PluginManifest } from '@@/plugins/manifest';

				 */

				export const manifest: PluginManifest = {

				  publisher: 'officerdev',

				  version: '2026.08.29.24',

				  version: '2026.08.29.25',

				  platform: '>=1.0.0',

				  label: 'Fofos',