Add jump-to-page pagination and Find Next/Previous navigation in search results

[entsalze]

Is your feature request related to a problem? Please describe.

• The list currently uses infinite scroll to load data. There is no pagination, no previous/next page buttons, and no way to jump directly to a specific page by entering a page number. When the dataset is large, the only option is to keep scrolling down, which is inefficient.
• The search function only displays all matching results at once as a list, with no way to easily view the context around each match. There is no "Find Next / Find Previous" navigation to step through matches one by one and see them in context, like in a typical editor's Ctrl+F. Users have to manually scan the result list instead.

Describe the solution you'd like

• Pagination:
  • Add a pagination bar (e.g., in the bottom right corner) with previous/next page buttons.
  • Add a page number input field where users can type a number and press Enter or click a confirm button to jump directly to that page.
  • Validate input bounds (not less than 1, not greater than total page count), with a warning or auto-correction when out of range.
• Search Find Next/Previous:
  • Add "Previous/Next" buttons next to the search box (or keyboard shortcuts such as Enter / Shift+Enter).
  • Clicking should automatically navigate to and highlight the current match.
  • Display a counter such as "X of Y" so users can step through all search results in order.

[Barush]

Hi @entsalze,
and thank you for such a thoughtful and detailed write-up, it's clear you've put real care into describing both the problem and a proposed solution.

I'd like to be honest and transparent about how we see each part:

Pagination
This is something we've deliberately decided against. Infinite scroll is a core part of how our translation view is designed to work, and it's the direction we want to keep for Tolgee. So while I completely understand the appeal of a classic pagination bar with page jumps, it's not a change we're planning to make.

Find Next / Previous in search
Here I think there may be a small difference in how our search is meant to work versus what you're expecting. Our search isn't a "find and step through matches" tool like Ctrl+F in an editor, it's more of a filter. It narrows the list down to matching keys rather than letting you iterate one-by-one through occurrences.

Context around each match
Similarly, "context" in Tolgee means something specific: it's information attached to a key itself (its description, screenshots, related metadata), not the surrounding keys based on their position in the list. So the surrounding-rows context you're describing isn't something the current model represents.

The good news! 🎉 We're soon releasing a new interface called Tolgee Apps, which will let you build your own custom views on top of Tolgee. This could be a great fit for exactly the kind of workflow you're after, since you'd be able to shape the browsing and navigation experience to your needs.

And most importantly, I'd genuinely love to understand your workflow better. Sometimes the solution already exists in a form we haven't thought to point out, or there's an underlying need we can address in a different way. Could you tell me a bit more about what you're ultimately trying to accomplish? What does your day-to-day look like when you're scrolling and searching, and what would make it faster for you?

Thanks again for taking the time, feedback like this genuinely helps us.