71–80 of 267 posts
An infinite scroll would have more UI density. Or a rich text editor containing 200 pages of text.
More information, yes, not density. Same for pagination. Information density = amount of information you can gather at once within a space, before any interaction.
The point is that Svelte may have trouble processing many off-screen elements, and those would be good tests.
Earlier quoted context omitted.
> you run into performance problems at the same number of elements regardless of whether they're interactive. As you implemented for the some of these pages, the solution is to go to a canvas. That's surprising. I thought Svelte's whole selling point was ultra-targeted and efficient DOM updates as a result of the compilation step and not having vdom. Are simple large tables still a problem within that paradigm? Which…
> Svelte's whole selling point was ultra-targeted and efficient DOM updates as a result of the compilation step and not having vdom Going by performance ( https://krausest.github.io/js-framework-benchmark/ ), Svelte 4 is essentially vdom, Svelte 5 is ultra-efficient based on the direct-DOM approach pioneered by Solid. Svelte 5 is currently a release candidate, API stable but also not necessarily production ready. htt…
Svelte itself is a successor to Ractive.js which already existed in 2013 [2] with similar ideas, but before JS transpilers came into the picture.
[1] https://www.solidjs.com/guides/comparison#svelte
[2] first npm release: https://www.npmjs.com/package/ractive/v/0.2.0
I'd like to think projects like these are somehow signaling a return to well designed but information dense , space saving interfaces ... The amount of bloat, whitespace, extra spacing, "air" and other such waste - starting with (now Google-dead) "Material Design" has been egregious.- (One can dream ...)
1. Mobile needs to have somewhat spacious UIs to deal with touch targets needing to be finger sized. 2. Companies don't want to design two very different UIs and by-in-large users prefer their skills transfer across platforms. 3. Accessibility is easier if the design leaves room for bigger font sizes and doesn't require fine motor control. Watching my dad start to noticeably age I'm realizing that even spacious spaci…
True. Mobile (and the path from "responsive" to "mobile native" - ergo, pre conditioned by everything you well mention ...)
... has led us to a what I think is today's sorry state of things.-
I deal with a lot of data in tabular form, and I like to have as much of it in front of me at once as I can. The biggest influence on my report design has been, believe it or not, iTunes: no more padding than necessary, zebra striping, fast and easy sorting, and something like a column browser if possible. I've been using DataTables happily for years. One thing I've been experimenting with lately is sorting vs. showi…
Earlier quoted context omitted.
More information, yes, not density. Same for pagination. Information density = amount of information you can gather at once within a space, before any interaction.
It depends on definition (a page is still a page, even if not everything is visible). The point is that Svelte may have trouble processing many off-screen elements, and those would be good tests.
This is a great intro to the topic: https://matthewstrom.com/writing/ui-density/
Earlier quoted context omitted.
1. Mobile needs to have somewhat spacious UIs to deal with touch targets needing to be finger sized. 2. Companies don't want to design two very different UIs and by-in-large users prefer their skills transfer across platforms. 3. Accessibility is easier if the design leaves room for bigger font sizes and doesn't require fine motor control. Watching my dad start to noticeably age I'm realizing that even spacious spaci…
I see and understand your well placed and valid examination.- True. Mobile (and the path from "responsive" to "mobile native" - ergo, pre conditioned by everything you well mention ...) ... has led us to a what I think is today's sorry state of things.-
Earlier quoted context omitted.
It depends on definition (a page is still a page, even if not everything is visible). The point is that Svelte may have trouble processing many off-screen elements, and those would be good tests.
Information density is a well-established concept in UI design, this experiment is not (just) about performance. This is a great intro to the topic: https://matthewstrom.com/writing/ui-density/
I deal with a lot of data in tabular form, and I like to have as much of it in front of me at once as I can. The biggest influence on my report design has been, believe it or not, iTunes: no more padding than necessary, zebra striping, fast and easy sorting, and something like a column browser if possible. I've been using DataTables happily for years. One thing I've been experimenting with lately is sorting vs. showi…
DataTables is great. Been using it for 10+ on a single product. We keep looking for a newer and better replacement, but have yet to find it.
Love the cube view! Tangentially related - anyone know a linux tool which takes a bunch of points/lines/labels as input and generates a nice interactive 3d view of it? I've considered using .obj file viewers, but it doesn't quite hit the mark. Gnuplot is nicer but doesn't have interactive features as far as I can tell.
I love plotly for all my graphics needs (mainly 2D but supports 3D too)! Can export to a standalone interactive html file, can be used as a pandas plotting backend, can be easily extended with some client-side JS if you want to add more interactivity to the final result
Something I've been banging on about for a while is the following: Programmers and designers keep trying to rebuild instagram in every domain, pretty UIs, regular UIs, "simple" UIs.
This is great when every interaction might be an onboarding, but can be really limiting and stupid in an environment where people are actually paying attention.
A proxy I like to use for the above distinction is whether the users are paid more than the programmers