skinning

I have always been a fan of skinning, even since the days of Litestep and other PC OS skinning systems.

This is an issue of unskilled devs using ancient UI design approach, usually not even bothering with skinning it.

It's hard to not just be 'skinning' and come up with interesting ways of display UI elements and data.

Hell, most of our projects were just skinning Wordpress and charging clients up the ass for it.

As long as there's a coherent logical approach, you can have skinning, performance and a maintenance friendly site without ever touching frameworks.

If we're stuck skinning the cat in a stupid way for a while will that drive you nuts?

There are actually better apps than Maya for modelling / UVing, but for animation / rigging / skinning / techanim it's the benchmark.

You want to use GPU-based skinning or similar techniques for best performance.

It just has been brought to the forefront of our issues now because there are no longer evil tyrants skinning people alive (outside of North Korea).

Things like using dictionary learning for skinning models is overkill.

Vertex skinning [1] (code at [2]) is a classic example.

Essentially you'd then be skinning LinkedIn profiles and I think that would make it a whole lot easier for people to get started.

"Skinning" and code re-use can be achieved in different ways using CSS.

ImGui looks decent but is "designed and optimised to create debug tools." If you're building a game that doesn't look like a debug tool, you'll want to do some kind of skinning or at least make the UI fit into the aesthetic.

A counter-counter argument is that implementing a language that is semantically distant from assembly language, over top of assembly language, counts as "from scratch", whereas skinning a language over with an interpreter (which doesn't even scan tokens, collect garbage or perform any I/O) doesn't count as "from scratch".

Skinning for a native look the way Qt does may be the way to go.

Skinning hasn't been done on the CPU for about a decade now.