Search everything: Bible text, settings and app functions from one field #138

New issue

Open

opened 2026-10-30 15:46:59 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-10-30 15:46:59 +00:00

Collaborator

Owner's idea (#95, comment 2676): one search field that finds everything, the way IntelliJ's Search Everywhere does:

Text: the Bible text, which needs F-feature text search.
Settings: "font size" jumps to that setting.
App functions: "go to", "modules", "switch Bible", and so on.

This fits the minimalist direction: the main screens keep few actions, the rest sits one or two levels down, and search reaches it all.

To be scoped after the #95 design pass, which gives search its place on the main screen. Questions to settle then:

Which index for the text (#?, the search feature), and its memory and disk cost against docs/07.
How settings and actions are registered so they can be searched, including translated names (the po files).

The priority is a guess (Could); relabel as you see fit.

Owner's idea (#95, comment 2676): one search field that finds everything, the way IntelliJ's Search Everywhere does: - **Text:** the Bible text, which needs F-feature text search. - **Settings:** "font size" jumps to that setting. - **App functions:** "go to", "modules", "switch Bible", and so on. This fits the minimalist direction: the main screens keep few actions, the rest sits one or two levels down, and search reaches it all. To be scoped after the #95 design pass, which gives search its place on the main screen. Questions to settle then: - Which index for the text (#?, the search feature), and its memory and disk cost against docs/07. - How settings and actions are registered so they can be searched, including translated names (the po files). The priority is a guess (Could); relabel as you see fit.

claude-bot added the

priority

Could

label

2026-10-30 15:46:59 +00:00

claude-bot referenced this issue

2026-10-30 17:49:53 +00:00

A proper design, a final name and a rebrand (after the v0.1 Shoulds) #95

claude-bot referenced this issue

2026-10-30 18:11:44 +00:00

A proper design, a final name and a rebrand (after the v0.1 Shoulds) #95

claude-bot referenced this issue