Earlier quoted context omitted.
I’m talking about the whitespace within a row. There’s no reason to make a row in the table 3x taller than the text on the row. If you think 8 rows is all your users need that’s fine, but why waste all that space?
Well there is a point to be made that if you don't stack rows without any spacing the user might actually be able to look left and right at different columns without losing sight which line they were even looking at. Can be partially solved by having alternating colour rows (and frankly it should've been a thing here), but ultimately this is far easier to read then your average excel sheet, at least to me. And frankl…
Tabler: Free and open source dashboard HTML/CSS framework
71–80 of 94 posts
Re: Tabler: Free and open source dashboard HTML/CSS framework
#72Earlier quoted context omitted.
From what I understand, it should also work ok with more semantic html elements. But it would be nice to see maybe a little of that in the examples.
Basically even if it's not built in, adding a reset stylesheet underneath it would make it work with semantic tags just like with divs, so no worries about that. then again, you'd probably not have to care about semantic structure in dashboards anyways, as it's unlikely SEO is a concern. Might be worth considering for accessibility though.
Re: Tabler: Free and open source dashboard HTML/CSS framework
#73Earlier quoted context omitted.
There are designers that appreciate the distinction between the way you design a desktop application vs a consumer website / mobile app. A lot of the design literature and discussion seems to be focused on the latter these days. A lot of things that desktop applications did are missing in most web apps; high information density, resizable panels, panel layouts (side by side etc...), keyboard shortcuts, embedded CLI's…
Designers optimize for the common customer, which does _not_ want keyboard shortcuts or embedded CLI's etc.
Re: Tabler: Free and open source dashboard HTML/CSS framework
#74I hate this modern design trend of wasting as much of my screen real estate as possible. It's ugly and it wastes my time, which is rude. Every one of these tables is literally 300% taller than it needs to be. Get rid of all the pointless padding and spaces. You can pack 3x the information on screen. This looks "modern" but it doesn't look good and it certainly isn't useful . Every time I bring this up in UX review de…
Re: Tabler: Free and open source dashboard HTML/CSS framework
#75I hate this modern design trend of wasting as much of my screen real estate as possible. It's ugly and it wastes my time, which is rude. Every one of these tables is literally 300% taller than it needs to be. Get rid of all the pointless padding and spaces. You can pack 3x the information on screen. This looks "modern" but it doesn't look good and it certainly isn't useful . Every time I bring this up in UX review de…
It's a dashboard. The point of a dashboard is to present the most important information in an aesthetically pleasing way, not to cram as much informational density per pixel as possible. This is why your UX review designers look at you like you're from the moon - you're not understanding the user need.
Re: Tabler: Free and open source dashboard HTML/CSS framework
#76I hate this modern design trend of wasting as much of my screen real estate as possible. It's ugly and it wastes my time, which is rude. Every one of these tables is literally 300% taller than it needs to be. Get rid of all the pointless padding and spaces. You can pack 3x the information on screen. This looks "modern" but it doesn't look good and it certainly isn't useful . Every time I bring this up in UX review de…
It's a dashboard. The point of a dashboard is to present the most important information in an aesthetically pleasing way, not to cram as much informational density per pixel as possible. This is why your UX review designers look at you like you're from the moon - you're not understanding the user need.
Re: Tabler: Free and open source dashboard HTML/CSS framework
#77Earlier quoted context omitted.
There are designers that appreciate the distinction between the way you design a desktop application vs a consumer website / mobile app. A lot of the design literature and discussion seems to be focused on the latter these days. A lot of things that desktop applications did are missing in most web apps; high information density, resizable panels, panel layouts (side by side etc...), keyboard shortcuts, embedded CLI's…
Designers optimize for the common customer, which does _not_ want keyboard shortcuts or embedded CLI's etc.
Re: Tabler: Free and open source dashboard HTML/CSS framework
#78I have been using Apache Superset on top of sqlite for my personal use, and am fairly happy with it. Any advantages/disadvantages of Tabler compared to Superset?
Tabler is just a (semi)framework for building the UI layer of that software. It doesn't provide any actual execution of logic.
Re: Tabler: Free and open source dashboard HTML/CSS framework
#79Why pack so many different things into a single project? If I want to build a dashboard with multiple widgets on the screen, my first step would be to look for a layout tool. Which allows me to handle how the screen is divided into multiple areas and offers an interative interface so I can open, move, resize and close those areas. I would not want a bundle that combines the layout tool with charts and forms and whatn…
Use what you want from whatever framework you want, but there's a lot of efficiency in one framework providing the vast majority as it's known to work well together and reduces complexity and decision making.
Re: Tabler: Free and open source dashboard HTML/CSS framework
#80I love Tabler and have used it for a few projects with great success. The title of the OP is not really accurate though. It's not so much a framework but a bunch of customization on top of Bootstrap and some pre-built templates for stuff _like_ dashboards, galleries, forms, etc. The site is more like a kitchen sink demo and documentation site for stuff you can pick apart and use in your own application.
> Any change in /src directory will build the application and refresh the page.
Do you start from the demo page and start ripping off components that you don't need? Or do you pick specific parts from the template and build it from scratch from bottom up?
Even though templates seem to be an easy way to build stuff, I never understood the approach building from templates.