Urgent.News

What's breaking now, across thousands of outlets.

Tech

I Built a Kawaii Native GUI with Nim and SDL3

Native GUI demos often look like settings panels, administrative dashboards, or collections of standard controls. Those examples are useful, but they leave another question unanswered: can the same native UI foundation express a playful, consumer-facing visual language? Clay Board Style System v0.5.0 includes a new Kawaii Companion demo built to explore that question. It renders a complete…

The article discusses a new Kawaii Companion demo built using the Native GUI framework CBSS (Clay Board Style System) and SDL3. The demo showcases a playful, consumer-facing visual language through soft color palette, mixed Japanese and English text, cards, progress indicators, and a stylized character drawn directly through retained Canvas commands.

The author emphasizes that this demo is not just a test of CBSS's ability to draw rounded rectangles, but rather a demonstration of its capacity to compose a coherent visual system that stands apart from conventional native GUI demos. The article highlights the usage of retained Box nodes, typed CBSS Style declarations, style resolution, layout, text, and paint, all of which are processed through the SDL3 backend to create a native desktop window.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Field Notes: Watching the Cascade Resolve, Start to Finish

Thursday's piece described the order the browser resolves conflicting CSS in: origin and importance first, then layer order, then specificity, then source order, with inheritance underneath all of it.

  • User-origin !important declarations take precedence over author-origin !important declarations
  • Layer order determines winner after removing !important declarations
  • Source order decides when same layer and specificity

Notas de campo: la resolución de la cascada, de principio a fin

El artículo del jueves describió el orden en que el navegador resuelve los conflictos de CSS: primero origen e importancia, luego el orden de las capas, después la especificidad y, por último, el…

  • Origin and importance stage determines color: green wins due to user-origin !important
  • Layer order resolves remaining rules before specificity: unlayered red wins over layered blue
  • Source order decides between identical declarations: navy blue wins due to later appearance

More from Saturday 22 August →