You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
First, Jupyter Dashboard is an excellent initiative and excellent results.
Share my experience on Grid Layout for Dashboard (QlikView, Tableau, ... other BI I used before).
Grid Layout is a complicated issue, many layouts, many combinaisons,..., all leading to re-factoring in the code, insertion of hacks to handle all the special cases.....
If one take experience from Web Design of website where they have the most experience, for example,
Wordpress. Best layouts are the pre-designed Grid layout.
Why Pre-designed layout template is better ?
Users dont have much idea of design, they just want to put things together in various/"exotic" ways, leading to big issues to handle on backend/programming side.... (a lot of work to handle all user cases).
Few (designer/specialist) people can think better for most of the people.
Pre-designed layout can be optimized for rendering,..., backend.... at end, less bugs, less conflict to handle, less individual request to handle...
In real case, we jus want to have Graphs, Tables and Texts put together in a readable way.
Given the space on one screen, only few "tested" design work better.
Having less but works without bug is more valuable than having more flexiblity and handling/hacking all the bugs.
Hope my comments would be of interest, fruiful for Jupyter Dahsboard progress.
Thanks for all the hardwork doing this.
The text was updated successfully, but these errors were encountered:
@arita37 Thanks for your comments. I don't think the extension in this repo will change to solely support pre-defined templates. That's not to say, however, that future dashboard efforts around Jupyter (e.g., in Jupyter Lab) shouldn't consider them. http://rmarkdown.rstudio.com/flexdashboard/ is one example of an interesting project that follows the approach you suggest.
First, Jupyter Dashboard is an excellent initiative and excellent results.
Share my experience on Grid Layout for Dashboard (QlikView, Tableau, ... other BI I used before).
Grid Layout is a complicated issue, many layouts, many combinaisons,..., all leading to re-factoring in the code, insertion of hacks to handle all the special cases.....
If one take experience from Web Design of website where they have the most experience, for example,
Wordpress. Best layouts are the pre-designed Grid layout.
Why Pre-designed layout template is better ?
Users dont have much idea of design, they just want to put things together in various/"exotic" ways, leading to big issues to handle on backend/programming side.... (a lot of work to handle all user cases).
Few (designer/specialist) people can think better for most of the people.
Pre-designed layout can be optimized for rendering,..., backend.... at end, less bugs, less conflict to handle, less individual request to handle...
In real case, we jus want to have Graphs, Tables and Texts put together in a readable way.
Given the space on one screen, only few "tested" design work better.
Having less but works without bug is more valuable than having more flexiblity and handling/hacking all the bugs.
Hope my comments would be of interest, fruiful for Jupyter Dahsboard progress.
Thanks for all the hardwork doing this.
The text was updated successfully, but these errors were encountered: