Rafael Schouten

I was trying to write it as a pure demonstration refactor with no changes to functionality, but I didn't test it so maybe it is actually different. I'm also fine...

Thanks. I've been looking into fixing layout issues for getting 60+ sliders on one page. These functions are kind of a problem, as they hard codes the css spacing you...

To solve this I could just move all of those styles over into style.css and replace them with clases?

I just realised that when everything came out unstyled! In terms of class names: `widget-row`, `widget-left`, `widget-center`, `widget-right`?

It would also be nice to have the widget type as a css class, so that classes on flex row would be `widget-row` and also `slider`? or further up on...

Also is there a helper function for including your own custom css?

Having additional css in a keyword would simplify that process. I also agree on the interact- prefix. I'm torn between getting the general case working and just getting this interface...

Some of this is superceded by https://github.com/yeesian/ArchGDAL.jl/pull/316 There the enum integers are used in the type directly. Its simple and works. But we could also swap them to real types,...

Yeah seems like something like that. So the question is really in what cases does GDAL actually return `wkbLinearRing` form `ogr_g_getgeometrytype`, if ever? Hard to make things type stable without...

Ok great. We can lock in `wkbLineString` as the type parameter. Edit: but I guess we still need to handle passing `wkbLinearRing` but getting back a `wkbLineString`. So a line...