officer
bf27793b44
They were floating buttons over the top-right of the iframe, which was wrong twice: they sit on top of Gitea's own controls, and an overlay on an application that fills its whole panel is invisible until you already know it is there. Reported as "I have no access to settings when the iframe is loaded", which is exactly right. The header is the platform's own furniture — always present, never competing with the content underneath — and it is where photos and jellyfin put theirs. It also names where you are, so /gitea/connection reads as "Gitea — connection" rather than looking like the frame failed to load.
23 lines
908 B
TypeScript
23 lines
908 B
TypeScript
import type { AppRegistryMeta } from 'officerdev';
|
|
import { GitBranch } from 'lucide-react';
|
|
import { GiteaFrame } from './GiteaFrame';
|
|
import { GiteaViewHeader } from './GiteaViewHeader';
|
|
|
|
// ONE panel, where the old screen had seventeen files behind two.
|
|
//
|
|
// There is no nav panel because Gitea has its own, inside the frame. A second navigation beside it would
|
|
// be two things claiming to say where you are, and the one that could not actually move you.
|
|
export const appRegistryMetas: AppRegistryMeta[] = [
|
|
{
|
|
key: 'gitea-frame',
|
|
name: 'Gitea',
|
|
icon: GitBranch,
|
|
component: GiteaFrame,
|
|
// The settings live in the HEADER, not floating over the frame: an overlay on an application that
|
|
// fills its own panel sits on top of that application's controls, and is invisible until you already
|
|
// know it is there.
|
|
header: GiteaViewHeader,
|
|
availableOnPanel: false,
|
|
},
|
|
];
|