Skip to content
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

fix: layout and no editor view #94

Closed
wants to merge 1 commit into from
Closed

Conversation

Bikash9609
Copy link

UI to shrink when the no editor view is active. Currently, the DB layout forms downwards which should be from left to right. The proposed solution fixes it, tho not completely but to some extent.

@Bikash9609
Copy link
Author

@Ovyerus

@Bikash9609
Copy link
Author

Bikash9609 commented Apr 12, 2024

scrnli_12_04_2024_20-23-57.mp4

Upon refining the user interface, I've endeavored to enhance its intuitive nature, fostering a more seamless user experience. However, one crucial aspect stands out: the layout of the tables. It's imperative that these tables adopt a left-to-right orientation (->) to optimize user visibility and comprehension. By arranging the tables horizontally, users can effortlessly perceive the entirety of the content without resorting to excessive zooming, which often leads to diminished clarity and legibility.

To illustrate, consider the following scenario: the video preview shown could have been effortlessly crafted in the following manner:

image

However, the current layout falls short, resulting in a less than ideal presentation:

image

Consequently, when dealing with a substantial number of tables, ranging from 10 to 20, it becomes apparent that viewing all of them simultaneously is impractical. While it's inherently illogical to expect these tables to fit within a single viewport, a strategic adjustment in layout orientation is warranted. Rather than resorting to a downward push, a lateral shift to the right proves more advantageous.

By favoring a rightward alignment, the tables remain within the user's purview, facilitating a more comprehensive understanding of the dataset. This approach mitigates the need for excessive scrolling or zooming, streamlining the user experience and fostering greater accessibility to the underlying data.

Ovyerus added a commit that referenced this pull request Apr 13, 2024
Thanks to @Bikash9609 for bringing this to my attention.
@Ovyerus
Copy link
Owner

Ovyerus commented Apr 13, 2024

Thanks for bringing the direction option to my knowledge! I've made the commit ab228c4 with only that change as I'm not fond of the header change personally.

@Ovyerus Ovyerus closed this Apr 13, 2024
@Bikash9609
Copy link
Author

Np, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants