Details for the issue

Hoping to get a nice new feature/capability. Routinely when I am working on writing complex SQL queries, I use the 'Execute SQL' tab to refine them as I like being able to type and hit ctrl-enter to see the results. Even better, doing so with a specific selection only executes that code making it a joy to use.

However, many times I have to routinely go back to the 'Browse Data' tab to check on some things, and every time I do, not only do I hate being switched away from my code (making a lot of tabbing back and forth) but on every return to the 'Browse Data' tab, it's reset and I have to go looking for what I was after all over again.

Now one solution would be to somehow persist the state of the Browse Data tabs, but from other bugs here, I see the coding pattern has been a dump-and-reload model, making that a non-trivial task. BUT... if we could somehow float the SQL windows (and their results) into new windows, we could look at the data side-by-side with the SQL code. Actually, being able to float multiple windows would be the best so I can look at several result sets all at once.

For instance, this would come in handy when I'm trying to see the results of a temp table and the results of a join on that temp table. I'd like to select out the results, leave them on screen for reference, then execute other code against it.

As an alternate to floating windows, and for that matter, preferable to them, I'd actually love to see a truly tabbed interface, similar to how VS Code handles its tabs. You can open groups of tabs, then split them horizontally or vertically as you see fit. If you could then save these as workspaces, perhaps with your open SQL statements in a metadata file alongside the open database, that would be epic!!

But heck... I'd even settle for simple side-by-side tiling of what's already there. Point being, being able to see both your code, its results, and the Browse Data feature all at the same time is IMHO a sorely-needed feature.

Useful extra information

I'm opening this issue because:

• DB4S is crashing
• DB4S has a bug
• DB4S needs a feature
• DB4S has another problem

I'm using DB4S on:

• Windows
• Linux: ( distro: ___ )
• Mac OS
• Other: ___

I'm using DB4S version:

• 3.9.0
• 3.8.0
• Other: ___

I have also:

• Tried out the nightly version: https://github.com/sqlitebrowser/sqlitebrowser#windows
• Searched for an existing similar issue: https://github.com/sqlitebrowser/sqlitebrowser/issues?utf8=%E2%9C%93&q=is%3Aissue%20