lukashornych
commented
4 months ago However, there is problem with tabs that are not associated with any connection, such as: certain error viewers, keyboard shortcut viewer and there may be more in the future. Where would be put these tabs? Would we create another virtual workspace only for these general tabs?
novoj
After some discussion how to properly display active evitaDB connection name in tab toolbars so that it is obvious even for server managements tabs where the user is, we come one with totally different approach. The original idea to just simply add the connection name at the beginning of a toolbar was kinda discarded as it could get quite longer in some case (like schema viewers).
Instead, we started play with idea that each evitaDB connection would have it's own "virtual" workspace with its own tabs. Also, the main sidebar that is currently used to switch between different tools like in VS Code for example, would newly serve as switcher for the connections themself leaving the connection explorer unclutters because there would be only data from the selected connection.
That way we don't have to label each tab with connection name (less clutter) and so the toolbars. Also, there would be clear distinction in workflow between multiple connections, like "production" and "test" for example.
Unfortunately, this would mean that we would have to extend the tabs model and split the listings by selected connection. Also, the side bar would allow only circular thumbnails, so we would have to get creative with displaying available connections. For example, generate letter shortcut (like for profile pictures) with random colors.