-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for narrow screens #14
Comments
I do not fully understand, can you explain your idea? |
It's clear now. Added in TODO. |
I have the same problem. |
Just an idea for realisation. Two column header convert to one column. And the query statement put on the next row. |
Horizontal scrolling would be good to have -- similar to what pspg provides for psql. |
@NikolayS I fully support implementing For instance, users could set individual column minimum and maximum lengths, ensuring that columns are displayed in their minimum width when not selected, for example, and are expanded to their maximum width when selected, and scrolling horizontally if their content exceeds the maximum width. Or, additionally, users could set individual row minimum and maximum heights (with obvious minimum height of 1) enabling them to set specific heights for rows (some may want to have all rows of minimum height of 3, for example, for any reason). This would allow for flexible wrapping or unwrapping of cell contents based on the width and also vertical scrolling when necessary. I see each cell itself as a little box capable of resizing, reflowing it's content (wrapping) and scrolling it in either direction. Such cell is then "bound" to the columns and rows matrix that maintains the "higher order" pane "barriers". You can imagine it as "global view" mode when you scroll etc. the whole columns and rows and they just behave pretty similarly how I am not sure if I explained it well and AFAIK nothing similar to it was implemented for TUI (yet). Although |
I propose to add support for narrow screens (1280x1024 for example) either by adaptive TUI, or by template option.
The text was updated successfully, but these errors were encountered: