ui: token-driven component library on Mantine
Adds src/components/ui: buttons, messages, labels, progress, status, tables,
form controls, panels, cards, statistics, modals, tooltips, tabs, and icons.
Everything resolves its colors through theme tokens, so no component branches
on the current theme, and Semantic UI keeps rendering the app meanwhile.
Mantine is bridged rather than restyled: its own CSS variables are pointed at
our tokens. Four details were not obvious, and each caused a visible defect
in night mode before being fixed:
- Structural colors must go in the resolver's light/dark blocks. Mantine
emits its values under [data-mantine-color-scheme], which outranks the
:root block that `variables` becomes, so its grays were winning.
- The dark and gray palettes are mapped shade by shade to tokens. Mantine
reads them directly for table borders, zebra stripes and input chrome;
they can be neither flattened nor left alone.
- Mantine writes --button-* as inline styles, which no stylesheet can
outrank, so the dashed danger treatment sets real properties instead.
- Switch colors are written onto inner elements, so they need scoped CSS
rather than a variable on the root. Adds a --knob token for control
handles, because Mantine's default thumb follows theme.white, which is
near-black in the dark-based themes.
An audit of every painted pixel in the /theme-sample gallery now finds no
non-red channel in night mode.
Icons come from @tabler/icons-react with the 102 Semantic names the app uses
mapped to components; they stroke with currentColor, so they follow the theme
without any rule of their own. Toasts keep the react-semantic-toasts-2
signature so those call sites migrate by changing an import.
TypeScript 5 is required: Mantine's declarations use `const` type parameters,
which 4.9 cannot parse (Mantine 7 is the same, so downgrading is no escape).
That needs two npm overrides to keep clean installs working, both verified
against a Docker build: react-scripts declares peerOptional typescript ^3||^4,
and fork-ts-checker 6.5.2 assigns typescript.performance.mark, which TS 5
made getter-only - crashing the dev server's type checker on every rebuild.
semantic-baseline.test.js ratchets the removal: it fails if a file not already
listed imports Semantic UI. An ESLint rule would have printed 75 warnings per
rebuild, and CI unsets CI= for its build step, so it would guard nothing there.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:22:03 -06:00
|
|
|
import React, {useContext, useState} from 'react';
|
|
|
|
|
import {ThemeContext} from '../contexts/contexts';
|
|
|
|
|
import {
|
|
|
|
|
Button,
|
|
|
|
|
Card,
|
|
|
|
|
CardGroup,
|
|
|
|
|
Confirm,
|
|
|
|
|
Icon,
|
|
|
|
|
IconButton,
|
|
|
|
|
Label,
|
|
|
|
|
Loader,
|
|
|
|
|
Message,
|
|
|
|
|
Panel,
|
|
|
|
|
Placeholder,
|
|
|
|
|
Progress,
|
|
|
|
|
Select,
|
|
|
|
|
Statistic,
|
|
|
|
|
StatisticGroup,
|
|
|
|
|
Status,
|
|
|
|
|
Table,
|
|
|
|
|
TextInput,
|
|
|
|
|
Textarea,
|
|
|
|
|
Checkbox,
|
ui: theme picker in Settings, and ship the component gallery
The gallery at /theme-sample is now a normal route rather than a development
one, and Settings links to it, so a user can see what a theme actually looks
like before committing to it. Every new component belongs in the gallery: it is
how the design gets reviewed, and how a component that only looks wrong in one
of the four themes gets caught.
Settings gains a Theme section with the new ThemePicker, which explains what
each theme is for - notably that night mode filters videos, documents and maps
to red as well, not just the interface.
Theme names and picker options move to themes/names.ts so the component library
can read them without importing components/Theme.tsx, which still pulls in
Semantic UI. Theme.tsx re-exports them, so existing call sites are unchanged.
The navigation bar's compact picker now reads the same list, so the two cannot
drift apart.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:38:04 -06:00
|
|
|
ThemePicker,
|
ui: token-driven component library on Mantine
Adds src/components/ui: buttons, messages, labels, progress, status, tables,
form controls, panels, cards, statistics, modals, tooltips, tabs, and icons.
Everything resolves its colors through theme tokens, so no component branches
on the current theme, and Semantic UI keeps rendering the app meanwhile.
Mantine is bridged rather than restyled: its own CSS variables are pointed at
our tokens. Four details were not obvious, and each caused a visible defect
in night mode before being fixed:
- Structural colors must go in the resolver's light/dark blocks. Mantine
emits its values under [data-mantine-color-scheme], which outranks the
:root block that `variables` becomes, so its grays were winning.
- The dark and gray palettes are mapped shade by shade to tokens. Mantine
reads them directly for table borders, zebra stripes and input chrome;
they can be neither flattened nor left alone.
- Mantine writes --button-* as inline styles, which no stylesheet can
outrank, so the dashed danger treatment sets real properties instead.
- Switch colors are written onto inner elements, so they need scoped CSS
rather than a variable on the root. Adds a --knob token for control
handles, because Mantine's default thumb follows theme.white, which is
near-black in the dark-based themes.
An audit of every painted pixel in the /theme-sample gallery now finds no
non-red channel in night mode.
Icons come from @tabler/icons-react with the 102 Semantic names the app uses
mapped to components; they stroke with currentColor, so they follow the theme
without any rule of their own. Toasts keep the react-semantic-toasts-2
signature so those call sites migrate by changing an import.
TypeScript 5 is required: Mantine's declarations use `const` type parameters,
which 4.9 cannot parse (Mantine 7 is the same, so downgrading is no escape).
That needs two npm overrides to keep clean installs working, both verified
against a Docker build: react-scripts declares peerOptional typescript ^3||^4,
and fork-ts-checker 6.5.2 assigns typescript.performance.mark, which TS 5
made getter-only - crashing the dev server's type checker on every rebuild.
semantic-baseline.test.js ratchets the removal: it fails if a file not already
listed imports Semantic UI. An ESLint rule would have printed 75 warnings per
rebuild, and CI unsets CI= for its build step, so it would guard nothing there.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:22:03 -06:00
|
|
|
Toggle,
|
|
|
|
|
Tooltip,
|
|
|
|
|
toast,
|
|
|
|
|
} from './ui';
|
|
|
|
|
import {semanticColorNames} from '../themes/mantine';
|
|
|
|
|
|
|
|
|
|
/*
|
ui: theme picker in Settings, and ship the component gallery
The gallery at /theme-sample is now a normal route rather than a development
one, and Settings links to it, so a user can see what a theme actually looks
like before committing to it. Every new component belongs in the gallery: it is
how the design gets reviewed, and how a component that only looks wrong in one
of the four themes gets caught.
Settings gains a Theme section with the new ThemePicker, which explains what
each theme is for - notably that night mode filters videos, documents and maps
to red as well, not just the interface.
Theme names and picker options move to themes/names.ts so the component library
can read them without importing components/Theme.tsx, which still pulls in
Semantic UI. Theme.tsx re-exports them, so existing call sites are unchanged.
The navigation bar's compact picker now reads the same list, so the two cannot
drift apart.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:38:04 -06:00
|
|
|
* A gallery of every component in the library, in the current theme.
|
ui: token-driven component library on Mantine
Adds src/components/ui: buttons, messages, labels, progress, status, tables,
form controls, panels, cards, statistics, modals, tooltips, tabs, and icons.
Everything resolves its colors through theme tokens, so no component branches
on the current theme, and Semantic UI keeps rendering the app meanwhile.
Mantine is bridged rather than restyled: its own CSS variables are pointed at
our tokens. Four details were not obvious, and each caused a visible defect
in night mode before being fixed:
- Structural colors must go in the resolver's light/dark blocks. Mantine
emits its values under [data-mantine-color-scheme], which outranks the
:root block that `variables` becomes, so its grays were winning.
- The dark and gray palettes are mapped shade by shade to tokens. Mantine
reads them directly for table borders, zebra stripes and input chrome;
they can be neither flattened nor left alone.
- Mantine writes --button-* as inline styles, which no stylesheet can
outrank, so the dashed danger treatment sets real properties instead.
- Switch colors are written onto inner elements, so they need scoped CSS
rather than a variable on the root. Adds a --knob token for control
handles, because Mantine's default thumb follows theme.white, which is
near-black in the dark-based themes.
An audit of every painted pixel in the /theme-sample gallery now finds no
non-red channel in night mode.
Icons come from @tabler/icons-react with the 102 Semantic names the app uses
mapped to components; they stroke with currentColor, so they follow the theme
without any rule of their own. Toasts keep the react-semantic-toasts-2
signature so those call sites migrate by changing an import.
TypeScript 5 is required: Mantine's declarations use `const` type parameters,
which 4.9 cannot parse (Mantine 7 is the same, so downgrading is no escape).
That needs two npm overrides to keep clean installs working, both verified
against a Docker build: react-scripts declares peerOptional typescript ^3||^4,
and fork-ts-checker 6.5.2 assigns typescript.performance.mark, which TS 5
made getter-only - crashing the dev server's type checker on every rebuild.
semantic-baseline.test.js ratchets the removal: it fails if a file not already
listed imports Semantic UI. An ESLint rule would have printed 75 warnings per
rebuild, and CI unsets CI= for its build step, so it would guard nothing there.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:22:03 -06:00
|
|
|
*
|
ui: theme picker in Settings, and ship the component gallery
The gallery at /theme-sample is now a normal route rather than a development
one, and Settings links to it, so a user can see what a theme actually looks
like before committing to it. Every new component belongs in the gallery: it is
how the design gets reviewed, and how a component that only looks wrong in one
of the four themes gets caught.
Settings gains a Theme section with the new ThemePicker, which explains what
each theme is for - notably that night mode filters videos, documents and maps
to red as well, not just the interface.
Theme names and picker options move to themes/names.ts so the component library
can read them without importing components/Theme.tsx, which still pulls in
Semantic UI. Theme.tsx re-exports them, so existing call sites are unchanged.
The navigation bar's compact picker now reads the same list, so the two cannot
drift apart.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:38:04 -06:00
|
|
|
* Reachable at /theme-sample and linked from Settings, so a user can see a theme
|
|
|
|
|
* before committing to it.
|
|
|
|
|
*
|
|
|
|
|
* EVERY new component belongs here. It is how we review the design and how we
|
|
|
|
|
* catch a component that only looks wrong in one of the four themes — which has
|
|
|
|
|
* already happened more than once.
|
ui: token-driven component library on Mantine
Adds src/components/ui: buttons, messages, labels, progress, status, tables,
form controls, panels, cards, statistics, modals, tooltips, tabs, and icons.
Everything resolves its colors through theme tokens, so no component branches
on the current theme, and Semantic UI keeps rendering the app meanwhile.
Mantine is bridged rather than restyled: its own CSS variables are pointed at
our tokens. Four details were not obvious, and each caused a visible defect
in night mode before being fixed:
- Structural colors must go in the resolver's light/dark blocks. Mantine
emits its values under [data-mantine-color-scheme], which outranks the
:root block that `variables` becomes, so its grays were winning.
- The dark and gray palettes are mapped shade by shade to tokens. Mantine
reads them directly for table borders, zebra stripes and input chrome;
they can be neither flattened nor left alone.
- Mantine writes --button-* as inline styles, which no stylesheet can
outrank, so the dashed danger treatment sets real properties instead.
- Switch colors are written onto inner elements, so they need scoped CSS
rather than a variable on the root. Adds a --knob token for control
handles, because Mantine's default thumb follows theme.white, which is
near-black in the dark-based themes.
An audit of every painted pixel in the /theme-sample gallery now finds no
non-red channel in night mode.
Icons come from @tabler/icons-react with the 102 Semantic names the app uses
mapped to components; they stroke with currentColor, so they follow the theme
without any rule of their own. Toasts keep the react-semantic-toasts-2
signature so those call sites migrate by changing an import.
TypeScript 5 is required: Mantine's declarations use `const` type parameters,
which 4.9 cannot parse (Mantine 7 is the same, so downgrading is no escape).
That needs two npm overrides to keep clean installs working, both verified
against a Docker build: react-scripts declares peerOptional typescript ^3||^4,
and fork-ts-checker 6.5.2 assigns typescript.performance.mark, which TS 5
made getter-only - crashing the dev server's type checker on every rebuild.
semantic-baseline.test.js ratchets the removal: it fails if a file not already
listed imports Semantic UI. An ESLint rule would have printed 75 warnings per
rebuild, and CI unsets CI= for its build step, so it would guard nothing there.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:22:03 -06:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
const Section = ({label, children}) => <section style={{marginBottom: 34}}>
|
|
|
|
|
<p style={{
|
|
|
|
|
fontSize: 11, fontWeight: 600, letterSpacing: '0.12em', textTransform: 'uppercase',
|
|
|
|
|
color: 'var(--muted)', margin: '0 0 10px',
|
|
|
|
|
}}>{label}</p>
|
|
|
|
|
{children}
|
|
|
|
|
</section>;
|
|
|
|
|
|
|
|
|
|
const Row = ({children}) => <div style={{display: 'flex', gap: 10, flexWrap: 'wrap', alignItems: 'center'}}>
|
|
|
|
|
{children}
|
|
|
|
|
</div>;
|
|
|
|
|
|
|
|
|
|
export function ThemeSamplePage() {
|
|
|
|
|
const {theme, setTheme} = useContext(ThemeContext);
|
|
|
|
|
const [confirmOpen, setConfirmOpen] = useState(false);
|
|
|
|
|
const [comments, setComments] = useState(true);
|
|
|
|
|
const [hotspot, setHotspot] = useState(true);
|
|
|
|
|
|
|
|
|
|
return <div style={{maxWidth: 1060, margin: '0 auto', padding: '20px 16px 60px', color: 'var(--text)'}}>
|
|
|
|
|
<h1 style={{fontSize: 21, fontWeight: 600, margin: '8px 0 4px'}}>Component gallery</h1>
|
|
|
|
|
<p style={{color: 'var(--muted)', fontSize: 13, marginTop: 0}}>
|
ui: theme picker in Settings, and ship the component gallery
The gallery at /theme-sample is now a normal route rather than a development
one, and Settings links to it, so a user can see what a theme actually looks
like before committing to it. Every new component belongs in the gallery: it is
how the design gets reviewed, and how a component that only looks wrong in one
of the four themes gets caught.
Settings gains a Theme section with the new ThemePicker, which explains what
each theme is for - notably that night mode filters videos, documents and maps
to red as well, not just the interface.
Theme names and picker options move to themes/names.ts so the component library
can read them without importing components/Theme.tsx, which still pulls in
Semantic UI. Theme.tsx re-exports them, so existing call sites are unchanged.
The navigation bar's compact picker now reads the same list, so the two cannot
drift apart.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:38:04 -06:00
|
|
|
Every component in the WROLPi interface library, rendered in the <strong>{theme}</strong> theme.
|
ui: token-driven component library on Mantine
Adds src/components/ui: buttons, messages, labels, progress, status, tables,
form controls, panels, cards, statistics, modals, tooltips, tabs, and icons.
Everything resolves its colors through theme tokens, so no component branches
on the current theme, and Semantic UI keeps rendering the app meanwhile.
Mantine is bridged rather than restyled: its own CSS variables are pointed at
our tokens. Four details were not obvious, and each caused a visible defect
in night mode before being fixed:
- Structural colors must go in the resolver's light/dark blocks. Mantine
emits its values under [data-mantine-color-scheme], which outranks the
:root block that `variables` becomes, so its grays were winning.
- The dark and gray palettes are mapped shade by shade to tokens. Mantine
reads them directly for table borders, zebra stripes and input chrome;
they can be neither flattened nor left alone.
- Mantine writes --button-* as inline styles, which no stylesheet can
outrank, so the dashed danger treatment sets real properties instead.
- Switch colors are written onto inner elements, so they need scoped CSS
rather than a variable on the root. Adds a --knob token for control
handles, because Mantine's default thumb follows theme.white, which is
near-black in the dark-based themes.
An audit of every painted pixel in the /theme-sample gallery now finds no
non-red channel in night mode.
Icons come from @tabler/icons-react with the 102 Semantic names the app uses
mapped to components; they stroke with currentColor, so they follow the theme
without any rule of their own. Toasts keep the react-semantic-toasts-2
signature so those call sites migrate by changing an import.
TypeScript 5 is required: Mantine's declarations use `const` type parameters,
which 4.9 cannot parse (Mantine 7 is the same, so downgrading is no escape).
That needs two npm overrides to keep clean installs working, both verified
against a Docker build: react-scripts declares peerOptional typescript ^3||^4,
and fork-ts-checker 6.5.2 assigns typescript.performance.mark, which TS 5
made getter-only - crashing the dev server's type checker on every rebuild.
semantic-baseline.test.js ratchets the removal: it fails if a file not already
listed imports Semantic UI. An ESLint rule would have printed 75 warnings per
rebuild, and CI unsets CI= for its build step, so it would guard nothing there.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:22:03 -06:00
|
|
|
Switch themes here or from the navigation bar.
|
|
|
|
|
</p>
|
|
|
|
|
|
ui: theme picker in Settings, and ship the component gallery
The gallery at /theme-sample is now a normal route rather than a development
one, and Settings links to it, so a user can see what a theme actually looks
like before committing to it. Every new component belongs in the gallery: it is
how the design gets reviewed, and how a component that only looks wrong in one
of the four themes gets caught.
Settings gains a Theme section with the new ThemePicker, which explains what
each theme is for - notably that night mode filters videos, documents and maps
to red as well, not just the interface.
Theme names and picker options move to themes/names.ts so the component library
can read them without importing components/Theme.tsx, which still pulls in
Semantic UI. Theme.tsx re-exports them, so existing call sites are unchanged.
The navigation bar's compact picker now reads the same list, so the two cannot
drift apart.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:38:04 -06:00
|
|
|
<Section label='Theme picker'>
|
|
|
|
|
<Panel>
|
|
|
|
|
<ThemePicker/>
|
|
|
|
|
<p style={{fontSize: 12, color: 'var(--muted)', marginBottom: 0, marginTop: 12}}>
|
|
|
|
|
The same picker the Settings page uses. The navigation bar has a compact
|
|
|
|
|
version; both read the same list of themes.
|
|
|
|
|
</p>
|
|
|
|
|
</Panel>
|
ui: token-driven component library on Mantine
Adds src/components/ui: buttons, messages, labels, progress, status, tables,
form controls, panels, cards, statistics, modals, tooltips, tabs, and icons.
Everything resolves its colors through theme tokens, so no component branches
on the current theme, and Semantic UI keeps rendering the app meanwhile.
Mantine is bridged rather than restyled: its own CSS variables are pointed at
our tokens. Four details were not obvious, and each caused a visible defect
in night mode before being fixed:
- Structural colors must go in the resolver's light/dark blocks. Mantine
emits its values under [data-mantine-color-scheme], which outranks the
:root block that `variables` becomes, so its grays were winning.
- The dark and gray palettes are mapped shade by shade to tokens. Mantine
reads them directly for table borders, zebra stripes and input chrome;
they can be neither flattened nor left alone.
- Mantine writes --button-* as inline styles, which no stylesheet can
outrank, so the dashed danger treatment sets real properties instead.
- Switch colors are written onto inner elements, so they need scoped CSS
rather than a variable on the root. Adds a --knob token for control
handles, because Mantine's default thumb follows theme.white, which is
near-black in the dark-based themes.
An audit of every painted pixel in the /theme-sample gallery now finds no
non-red channel in night mode.
Icons come from @tabler/icons-react with the 102 Semantic names the app uses
mapped to components; they stroke with currentColor, so they follow the theme
without any rule of their own. Toasts keep the react-semantic-toasts-2
signature so those call sites migrate by changing an import.
TypeScript 5 is required: Mantine's declarations use `const` type parameters,
which 4.9 cannot parse (Mantine 7 is the same, so downgrading is no escape).
That needs two npm overrides to keep clean installs working, both verified
against a Docker build: react-scripts declares peerOptional typescript ^3||^4,
and fork-ts-checker 6.5.2 assigns typescript.performance.mark, which TS 5
made getter-only - crashing the dev server's type checker on every rebuild.
semantic-baseline.test.js ratchets the removal: it fails if a file not already
listed imports Semantic UI. An ESLint rule would have printed 75 warnings per
rebuild, and CI unsets CI= for its build step, so it would guard nothing there.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-29 19:22:03 -06:00
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Section label='Statistics'>
|
|
|
|
|
<StatisticGroup>
|
|
|
|
|
<Statistic value='1,432' label='Videos'/>
|
|
|
|
|
<Statistic value='896' label='Archives'/>
|
|
|
|
|
<Statistic value='12,904' label='Files'/>
|
|
|
|
|
<Statistic value='87.4 GiB' label='Free space'/>
|
|
|
|
|
<Statistic value='14' label='Zim files'/>
|
|
|
|
|
</StatisticGroup>
|
|
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Section label='Buttons'>
|
|
|
|
|
<Panel>
|
|
|
|
|
<Row>
|
|
|
|
|
<Button role='primary' icon='download'>Download</Button>
|
|
|
|
|
<Button role='save' icon='save'>Save</Button>
|
|
|
|
|
<Button role='retry' icon='refresh'>Retry</Button>
|
|
|
|
|
<Button role='danger' icon='trash' onClick={() => setConfirmOpen(true)}>Delete</Button>
|
|
|
|
|
<Button role='cancel' icon='x'>Cancel</Button>
|
|
|
|
|
<Button role='primary' loading>Working</Button>
|
|
|
|
|
<Button role='primary' disabled>Disabled</Button>
|
|
|
|
|
</Row>
|
|
|
|
|
<div style={{marginTop: 12}}>
|
|
|
|
|
<Row>
|
|
|
|
|
<IconButton icon='settings' label='Settings'/>
|
|
|
|
|
<IconButton icon='search' label='Search'/>
|
|
|
|
|
<IconButton icon='trash' role='danger' label='Delete'
|
|
|
|
|
onClick={() => setConfirmOpen(true)}/>
|
|
|
|
|
<Tooltip label='Tooltips replace Semantic popups'>
|
|
|
|
|
<Button role='cancel'>Hover me</Button>
|
|
|
|
|
</Tooltip>
|
|
|
|
|
<Button role='cancel' onClick={() => toast({
|
|
|
|
|
type: 'success', title: 'Saved', description: 'Channel settings written.',
|
|
|
|
|
})}>Show a toast</Button>
|
|
|
|
|
</Row>
|
|
|
|
|
</div>
|
|
|
|
|
<p style={{fontSize: 12, color: 'var(--muted)', marginBottom: 0}}>
|
|
|
|
|
In night mode Delete drops its fill for a dashed red outline; dashed means
|
|
|
|
|
destructive or failed, and nothing else uses it.
|
|
|
|
|
</p>
|
|
|
|
|
</Panel>
|
|
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Section label='Messages'>
|
|
|
|
|
<div style={{display: 'flex', flexDirection: 'column', gap: 10}}>
|
|
|
|
|
<Message kind='info' title='Refresh started'>
|
|
|
|
|
Indexing the media directory. This can take several minutes.
|
|
|
|
|
</Message>
|
|
|
|
|
<Message kind='success' title='Config saved'>
|
|
|
|
|
Channel settings were written to config/channels.yaml.
|
|
|
|
|
</Message>
|
|
|
|
|
<Message kind='warning' title='Daily download limit reached'>
|
|
|
|
|
Downloads will resume tomorrow at 00:00.
|
|
|
|
|
</Message>
|
|
|
|
|
<Message kind='error' title='Download failed'>
|
|
|
|
|
HTTP 403 from the remote server after 3 attempts. Retry, or check the URL.
|
|
|
|
|
</Message>
|
|
|
|
|
</div>
|
|
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Section label='Downloads table'>
|
|
|
|
|
<Table>
|
|
|
|
|
<Table.Header>
|
|
|
|
|
<Table.Row>
|
|
|
|
|
<Table.HeaderCell>URL</Table.HeaderCell>
|
|
|
|
|
<Table.HeaderCell>Downloader</Table.HeaderCell>
|
|
|
|
|
<Table.HeaderCell style={{width: 150}}>Progress</Table.HeaderCell>
|
|
|
|
|
<Table.HeaderCell>Status</Table.HeaderCell>
|
|
|
|
|
<Table.HeaderCell>Size</Table.HeaderCell>
|
|
|
|
|
<Table.HeaderCell>Actions</Table.HeaderCell>
|
|
|
|
|
</Table.Row>
|
|
|
|
|
</Table.Header>
|
|
|
|
|
<Table.Body>
|
|
|
|
|
<Table.Row>
|
|
|
|
|
<Table.Cell>youtube.com/watch?v=hT6Rkfahyg</Table.Cell>
|
|
|
|
|
<Table.Cell>video</Table.Cell>
|
|
|
|
|
<Table.Cell><Progress percent={100}/></Table.Cell>
|
|
|
|
|
<Table.Cell><Status kind='complete'>complete</Status></Table.Cell>
|
|
|
|
|
<Table.Cell numeric>312 MiB</Table.Cell>
|
|
|
|
|
<Table.Cell><Button role='cancel' size='xs'>Details</Button></Table.Cell>
|
|
|
|
|
</Table.Row>
|
|
|
|
|
<Table.Row>
|
|
|
|
|
<Table.Cell>youtube.com/watch?v=Zk91nq2rrE</Table.Cell>
|
|
|
|
|
<Table.Cell>video</Table.Cell>
|
|
|
|
|
<Table.Cell><Progress percent={62}/></Table.Cell>
|
|
|
|
|
<Table.Cell><Status kind='active'>downloading</Status></Table.Cell>
|
|
|
|
|
<Table.Cell numeric>198 MiB</Table.Cell>
|
|
|
|
|
<Table.Cell><Button role='cancel' size='xs'>Stop</Button></Table.Cell>
|
|
|
|
|
</Table.Row>
|
|
|
|
|
<Table.Row failed>
|
|
|
|
|
<Table.Cell>example.org/prepping/water-storage.html</Table.Cell>
|
|
|
|
|
<Table.Cell>archive</Table.Cell>
|
|
|
|
|
<Table.Cell><Progress percent={0} showPercent={false}/></Table.Cell>
|
|
|
|
|
<Table.Cell><Status kind='failed'>failed</Status></Table.Cell>
|
|
|
|
|
<Table.Cell numeric>—</Table.Cell>
|
|
|
|
|
<Table.Cell>
|
|
|
|
|
<Row>
|
|
|
|
|
<Button role='retry' size='xs' icon='refresh'>Retry</Button>
|
|
|
|
|
<Button role='danger' size='xs' icon='trash'
|
|
|
|
|
onClick={() => setConfirmOpen(true)}>Delete</Button>
|
|
|
|
|
</Row>
|
|
|
|
|
</Table.Cell>
|
|
|
|
|
</Table.Row>
|
|
|
|
|
<Table.Row>
|
|
|
|
|
<Table.Cell>wikipedia_en_all_maxi_2026-06.zim</Table.Cell>
|
|
|
|
|
<Table.Cell>zim</Table.Cell>
|
|
|
|
|
<Table.Cell><Progress percent={0}/></Table.Cell>
|
|
|
|
|
<Table.Cell><Status kind='pending'>pending</Status></Table.Cell>
|
|
|
|
|
<Table.Cell numeric>104 GiB</Table.Cell>
|
|
|
|
|
<Table.Cell><Button role='cancel' size='xs'>Cancel</Button></Table.Cell>
|
|
|
|
|
</Table.Row>
|
|
|
|
|
</Table.Body>
|
|
|
|
|
</Table>
|
|
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Section label='Form controls'>
|
|
|
|
|
<Panel>
|
|
|
|
|
<div style={{display: 'grid', gridTemplateColumns: '2fr 1fr 1fr', gap: 12}}>
|
|
|
|
|
<TextInput label='URLs' defaultValue='https://www.youtube.com/watch?v=hT6Rkfahyg'
|
|
|
|
|
description='One URL per line.'/>
|
|
|
|
|
<Select label='Downloader' defaultValue='Videos'
|
|
|
|
|
data={['Videos', 'Archive', 'File', 'Scrape']}/>
|
|
|
|
|
<TextInput label='Destination' defaultValue='videos/'/>
|
|
|
|
|
</div>
|
|
|
|
|
<div style={{marginTop: 12}}>
|
|
|
|
|
<Textarea label='Notes' placeholder='Notes about this download…' minRows={2}/>
|
|
|
|
|
</div>
|
|
|
|
|
<div style={{marginTop: 14, display: 'flex', flexDirection: 'column', gap: 10}}>
|
|
|
|
|
<Checkbox label='Download comments' checked={comments}
|
|
|
|
|
onChange={e => setComments(e.currentTarget.checked)}/>
|
|
|
|
|
<Toggle label='Hotspot' description='Broadcast the WROLPi WiFi network.'
|
|
|
|
|
checked={hotspot} onChange={e => setHotspot(e.currentTarget.checked)}/>
|
|
|
|
|
<Toggle label='WROL Mode' description='Read-only: disables downloads.'/>
|
|
|
|
|
<Toggle label='Bluetooth' description='No adapter detected.' disabled/>
|
|
|
|
|
</div>
|
|
|
|
|
</Panel>
|
|
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Section label='Labels'>
|
|
|
|
|
<Panel>
|
|
|
|
|
<Row>
|
|
|
|
|
{semanticColorNames.map(color => <Label key={color} color={color}>{color}</Label>)}
|
|
|
|
|
<Label color='black'>black</Label>
|
|
|
|
|
<Label color='white'>white</Label>
|
|
|
|
|
<Label color='blue' icon='tag'>tagged</Label>
|
|
|
|
|
</Row>
|
|
|
|
|
</Panel>
|
|
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Section label='Icons'>
|
|
|
|
|
<Panel>
|
|
|
|
|
<Row>
|
|
|
|
|
{['film', 'archive', 'file text', 'map outline', 'book', 'settings', 'search',
|
|
|
|
|
'download', 'trash', 'warning sign'].map(name => <Icon key={name} name={name} size='large'/>)}
|
|
|
|
|
</Row>
|
|
|
|
|
<div style={{marginTop: 14}}>
|
|
|
|
|
<Row>
|
|
|
|
|
<Loader/>
|
|
|
|
|
<Icon name='circle notch' loading/>
|
|
|
|
|
<span style={{fontSize: 12, color: 'var(--muted)'}}>
|
|
|
|
|
Icons inherit currentColor, so they follow every theme.
|
|
|
|
|
</span>
|
|
|
|
|
</Row>
|
|
|
|
|
</div>
|
|
|
|
|
</Panel>
|
|
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Section label='Cards'>
|
|
|
|
|
<CardGroup>
|
|
|
|
|
{[
|
|
|
|
|
['How To Sharpen An Axe The Right Way', 'Wranglerstar · 2024-11-03'],
|
|
|
|
|
['Pressure Canning Basics', 'RoseRed Homestead · 2025-02-17'],
|
|
|
|
|
['Solar Panel Wiring: Series vs Parallel', 'DIY Solar Power · 2025-08-21'],
|
|
|
|
|
['Ham Radio General License, Part 1', 'Ham Radio Crash Course · 2024-05-09'],
|
|
|
|
|
].map(([title, meta]) => <Card
|
|
|
|
|
key={title}
|
|
|
|
|
title={title}
|
|
|
|
|
meta={meta}
|
|
|
|
|
media={<div style={{
|
|
|
|
|
aspectRatio: '16/9', background: 'var(--head)', display: 'flex',
|
|
|
|
|
alignItems: 'center', justifyContent: 'center', color: 'var(--muted)',
|
|
|
|
|
}}><Icon name='film' size={34}/></div>}
|
|
|
|
|
/>)}
|
|
|
|
|
</CardGroup>
|
|
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Section label='Loading placeholders'>
|
|
|
|
|
<Panel><Placeholder lines={4}/></Panel>
|
|
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Section label='Danger zone'>
|
|
|
|
|
<Panel danger>
|
|
|
|
|
<h2 style={{color: 'var(--red)', fontSize: 14, margin: '0 0 4px'}}>Danger zone</h2>
|
|
|
|
|
<p style={{color: 'var(--muted)', fontSize: 13, margin: '0 0 12px'}}>
|
|
|
|
|
These actions are destructive and cannot be undone.
|
|
|
|
|
</p>
|
|
|
|
|
<Row>
|
|
|
|
|
<Button role='danger' icon='trash' onClick={() => setConfirmOpen(true)}>
|
|
|
|
|
Delete channel
|
|
|
|
|
</Button>
|
|
|
|
|
<Button role='danger' icon='trash' onClick={() => setConfirmOpen(true)}>
|
|
|
|
|
Wipe download history
|
|
|
|
|
</Button>
|
|
|
|
|
</Row>
|
|
|
|
|
</Panel>
|
|
|
|
|
</Section>
|
|
|
|
|
|
|
|
|
|
<Confirm
|
|
|
|
|
open={confirmOpen}
|
|
|
|
|
destructive
|
|
|
|
|
title='Delete channel?'
|
|
|
|
|
confirmLabel='Delete'
|
|
|
|
|
onConfirm={() => setConfirmOpen(false)}
|
|
|
|
|
onCancel={() => setConfirmOpen(false)}
|
|
|
|
|
>
|
|
|
|
|
<p style={{marginTop: 0}}>
|
|
|
|
|
The channel <strong>Wranglerstar</strong> and its download rules will be removed.
|
|
|
|
|
</p>
|
|
|
|
|
<p style={{color: 'var(--muted)', marginBottom: 0}}>
|
|
|
|
|
videos/Wranglerstar/ (312 files) will not be deleted.
|
|
|
|
|
</p>
|
|
|
|
|
</Confirm>
|
|
|
|
|
</div>
|
|
|
|
|
}
|