-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
[core] Make DashboardLayout navigation responsive #3750
[core] Make DashboardLayout navigation responsive #3750
Conversation
There are some problems in the docs:
|
Added some fixes/improvements and addressed review feedback:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! About initialNavigationOpen
, I would expect the name of the prop to match more closely with the behaviour of opening the mobile navigation by default.
Perhaps mobileNavigationOpen
"propDescriptions": { | ||
"children": { "description": "The content of the dashboard." }, | ||
"initialNavigationOpen": { | ||
"description": "Whether the mobile navigation drawer should start open." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be external API? Why would users need this?
Besides, can't we, for demo purposes just force the large screen behavior. Maybe change the breakpoints or something. But in a hidden way, users shouldn't copy+paste our hacks accidentally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be internal API if possible, just not sure what the best way to do that is? Will try to find a solution. (edit: I guess we can just mark it as internal but it's still secretly usable?)
Also wasn't sure if it's better to have the mobile or the desktop version on the docs, so I guess we can try to use the desktop one there or change the breakpoints.
This comment was marked as outdated.
This comment was marked as outdated.
Addressed latest review feedback:
|
Solutions to the recent problems that have been raised:
|
This one should be good for a review, the themes in the demos are cleaner now! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's go!
Hello, very good! Can you make the code available? |
Hi, the features in this PR are already live in the latest version of |
Hi...How can I customize the layout with the toolpad/core? Make the vertical bars in the collected style as in the photo? |
So you want to have 2 columns on the left-side? I've created an issue in #4299, hopefully this feature will help! |
The toolpad doesn't make customizing more dynamic, right? So I can leave it aside and use old components, discarding the toolpad core. I want to create a double drawer... |
Depending on how specific the layout you want to create is, it might be difficult to adjust Toolpad Core to look exactly like it at the moment... |
I urgently need to make this layout this way, separated by drawers like Instagram and responsive: |
Will try to make it so you can override the header and drawer with your own custom components, and release it in v0.9.0 of I've also created an issue for supporting layouts with two navigation sidebars #4304 but I think it might not be our biggest priority for now. |
Thanks! I'm building my screens with the @mui/core components! |
Closes #3585
Make navigation menu open and close with a menu toggle in left side of the header in breakpoints under
md
.Also centered logo + title in mobile screens.
DashboardLayout docs: https://deploy-preview-3750--mui-toolpad-docs.netlify.app/toolpad/core/react-dashboard-layout
Screen.Recording.2024-07-19.at.14.33.41.mov