html is also super generic, haxeui xml is super specific

Specific to the ui use case you mean ?

well, i just mean that html describes generic "documents", haxeui (xml) instantiates a fixed set of ui components

True, html is broader in scope but you could specify a ui in it using a subset right ? And would web- components handle the component piece ? Not arguing for it for other reasons already noted but it seems possible

well, if you go down the web component type of route, then i would argue they are basically the same (at a high level point of view)

i think web components make html more like xml

but thats just superficial really, under the hood, any UI in html is still build out of a bunch of document fragments

I thought about that but xml files are docs in a similar sense. I think they operate at different levels of abstraction wrt to this particular problem

One more like a spec, another more like an impl

well, true enough

Ian, it draws curves with line and quads, with triangles with pixels. So drawing can create a hitTest objects. Gradient triangles allow shader style RGB fills using Barycentric coordinates you get the 0 to 1 distance from each corner as a ratio coordinate. UV triangles allow shader style image mapping, allowing rotation and arbitary scaling without too much distortion. So for instance you can rotate images without them always being too pixelated. Smoothed edges, basically you can times a barycentic ratio against alpha and limit it to stay below 1 to create a smooth edge down one side.

So with a many sided polygon you instead can get a fairly smooth gradient circle because the barycentric times-ed alpha smooth is on the outer edge.

then if you only take the lower part of all 3 ratios in this way then you can get a triangle with smoothed sides

or with just two sides

so for instance can be applied to a quad/line to have smooth edges

I have created a very basic XML mark up for the shapes

So Ian for instance this is a Quint ( Quad with inner corner ). https://nanjizal.github.io/pixelimage-samples/bin/canvas_quints.html as you can see different smooth can be applied

oh the pixel text example is a bit small at mo! https://nanjizal.github.io/pixelimage-samples/bin/canvas_text.html

but as you can see rotation is fine

arrows needs more work, still sorting out the sides that need smoothing when applied https://nanjizal.github.io/pixelimage-samples/bin/canvas_arrows.html

rounded rectangles https://nanjizal.github.io/pixelimage-samples/bin/canvas_rectangles.html still need to add a smooth option

this is with the xml specifying the pattern

yer probably need to sort out a few more of the demos...

some it is because the TriGML xml markup needs tweaking

The new testing repo is here.. https://nanjizal.github.io/pixelimage-samples/bin/canvas_rectangles.html nine slice is working

in fact most stuff is but maybe not all with the TriXML markup

so natively you can look though the and see most of the initial tests commented out

but will fix up the samples folder. https://github.com/nanjizal/pixelimage-samples arrows is probably one of the nicest to read. https://github.com/nanjizal/pixelimage-samples/blob/main/src/pixelimage_samples/pixelimage_canvas/Arrows.hx

What sort of stuff would be sensible. I can rework the conversion to a specific display texture and remove js specifics

maybe it needs more polish I guess I develop too many aspects at once