Hello! Ich hab da mal was für euch #mechanicalkeyboard Nerds und Nerdettes gebaut. Naja zumindest komme ich damit ganz gut klar.
Das KYB3R_KEYS Layout.
Ein Keyboardlayout mit Fokus auf Vim, Terminal und TilingWM Nutzung. Es hat viel Mate und Hirnschmalz gekostet. Habt Spaß beim testen 😘
Already gave a glimpse of this yesterday[1]. This example uses the new StackedLayout generator to create random multi-column base layouts and allocate cells of varying sizes (column/row spans). Depending on size, each cell also has a probability to produce nested child layouts in its place (up to 4 levels). The example also shows how the layout gen can be queried to determine & allocate any remaining empty space(s) at the bottom of each nesting level (since it's highly likely that there's such)... The result is a completely space-filling grid layout (which the new thi.ng website will likely be based on too, obviously with some of the more sane/usable/responsive configurations...)
This is a pain in the butt to read (before: hard-wrapped, after: unbroken). Yes, this applies to #Markdown files especially. Burn me at the stake if you want, but Markdown embedded in source files is not an exception.
As usual, deep in the blurry spectrum between outright and intended utility (aka layout algorithm), dataviz (tree depth) and art. I love them all, and as so often, the extrema are just a tiny param change away from each other! Pushing toward art territory often a great way to uncover issues and debug an algorithm. E.g. I had originally issues with propagating size changes of nested cells back up to their parent/ancestors (solved now)...
(Ps. also a teaser for next #HowToThing... probably out tomorrow)
Today we just wanted to share an internal clip that showcases what’s coming next, Grid Layout!
It’s still in a very early stage, we need to go through a lot of polishing, testing, user testing, more polishing… but it’s a nice little gorgeous clip to watch!
It is only implemented in Firefox (behind a flag) and #Safari 17 (Technical Preview) at the moment, though (one more reason to ditch Chr**e and Ed*e if you ask me).
Come to the Anarchist #DIY#publishing meet-up 10th of April where we gather around our book-info store!
We want to:
⭐ Generate a space where we can find reflection materials and editions (#books, #fanzine, #magazines, #pamphlets) that are an extension of the ideas and struggles in which we believe and participate.
⭐ Organize #workshops that actively encourage the do-it-yourself #layout, #printing and #binding.
A great guide by @fonts, which has really helped me understand those #flexbox properties better.
It just solved a "hack" I've used previously in one of my flex containers, where the container shouldn't grow when content in it changed (hack: use position: absolute and another element within with position: relative).
> The #CSS#AnchorPositioning#API is a game-changer in #web#development because it lets you natively position elements relative to other elements, known as anchors. This API simplifies complex #layout requirements for many interface features like menus and submenus, tooltips, selects, labels, cards, settings dialogs, and many more.
I use a different layout to type, but I'd like to be able to have my physical layout reflect what I'm actually typing. The problem is that moving the F and J keys to where they should be means the home row would be missing the tactile bumps, and I use those to recenter my hands when I'm not looking. I'd like to add keycaps for...
What are the keys with tactile bumps called?
I use a different layout to type, but I'd like to be able to have my physical layout reflect what I'm actually typing. The problem is that moving the F and J keys to where they should be means the home row would be missing the tactile bumps, and I use those to recenter my hands when I'm not looking. I'd like to add keycaps for...