Files
searchi/docs/FLOATING-LAUNCHER.md
T

53 lines
3.1 KiB
Markdown
Raw Permalink Normal View History

# Floating search launcher
The desktop opens as a centered search bar rather than a conventional document
window. The empty launcher requests 720 × 110 logical pixels. Typing or opening
settings, filters, local-model details or folder controls expands it to
1080 × 700. Native sizing stays inside the current monitor's work area, including
its scale factor and taskbar. A small display receives a smaller window.
The window is frameless, above ordinary windows, and omitted from the taskbar.
Its header can be dragged; the dedicated hide button, Escape and the existing
tray/global shortcut retain the resident workflow. The rounded shell uses the
configured native glass/frosted material where supported and the existing
opaque/high-contrast fallback otherwise. No CSS blur is presented as native
desktop transparency. Brief content transitions respect reduced motion and do
not defer search requests.
Installed applications have a separate list above file matches and a simple
launch preview. Arrow keys move across applications and files while preserving
typing focus; Enter launches the selected application or opens the selected
file. Application identities are opaque backend identifiers, not pretend file
paths or invented passages. Filters keep application suggestions out of scoped
file searches. Application requests are local lexical lookups and do not wait
for semantic inference.
Input immediately invalidates the previous application selection. A launch
requires the current query and the settled request revision, so a late response
or an immediate Enter after editing cannot launch an older suggestion. File
search timing remains separately measured; the result summary includes visible
application counts, and application-only matches suppress the empty-file state.
Automatic local-drive indexing is enabled by default. Its settings checkbox can
disable future automatic work while retaining searchable indexed content;
additional folder controls live inside settings. Existing active work is not
claimed to be instantly cancelled by the checkbox. Model progress and retry
remain available through local-search setup details.
## Validation recorded so far
- Frontend TypeScript/Vite build passed on desktop version 0.1.8.
- All 62 existing frontend tests passed; Prettier checks passed.
- Final Windows desktop checks passed 56 tests (one optional actual-catalog
check ignored); strict all-target Clippy passed. Linux passed 56 desktop tests.
- The background opacity control spans 40–100%, previews while dragging, and
applies directly to both glass materials. Local 60% reading tints protect
input, labels and controls; result and preview panes remain opaque.
- Twelve CPU browser composition checks passed across both themes, both glass
materials and 40/90/100% opacity. This verifies actual built CSS alpha,
independently of native compositor validation.
These checks alone do not establish native pixels, dragging, tray interaction,
rounded compositor corners or application launching. Actual final-build UI
capture and keyboard interaction belong in
[the native validation report](NATIVE-FINAL-VALIDATION.md).