Haxe

Oh. Wonder what stretch does. Gonna check the openfl implementation, thank you !

Ah, stretch is the default behavior, isn't it ?

https://github.com/haxeui/haxeui-openfl/blob/43355ff611d63c1ff86db6ba7535d9277fd0e654/haxe/ui/backend/openfl/OpenFLStyleHelper.hx#L272-L291  
I'm not sure , I haven't used much background-image-repeat

Thank you anyway, I'm gonna use this code to rewrite mine !

<@385014891750096896> Let's say I added a way to repeat images in my local Heaps binding code (in *StyleHelper.xml*). I also added a way to repeat parts of a 9-sliced image instead of stretching 'em (in case the image has more than just flat colors).
Should I try to do a PR for you to check ? Should I open an issue with my code in it ? What is your preferred workflow ?

nice, sounds great, either or work for me - totally up to you

I created it locally, tested on my machine, then uploaded to the playground

(using the forum announcement, 1.2, examples

gotcha... ok, so the first thing with it, is params have changed... they used to be `{0}`, `{1}`, etc... now they are `[0]`, `[1]`

this is because `{` is used in parsing now since you can get quite complex:

```
colours.count=[1] {
    none: has no colours
    one: has one colour
    many: has [0] colours
} in {
    [2]=m: his
    [2]=f: her
    _: their
} palette
```

yeah, thats a regression for sure... looking at it now

I will start updating the params in my apps

yeah, apologies for that - i kinda didnt really think anyone was really use this system... if its any consolation the new system is loads and loads better 🙂

alright, thats all working now: http://haxeui.org/builder/?dffda537

All compiling and displaying good except for my csv, tsv parsers. I will try to rewrite and pr. Thanks Ian!

i think i removed support for .po... was there ever support for csv?

In my framework yes. I had a Key Value class, extending LocaleParser, with simple childs setting up the separators, CR and comments differences

interesting... whats "your framework" out of curiosity? So you implemented a custom local parser for .csv and registered it? (Like: `LocaleParser.register("csv", CSVLocaleParser)`)? Sounds interesting, is there a use case for having that in core?

Csv or tsv are common as simple interchange data and most CAT tools handle them seamlessly.

so, btw, you are right about scaling... non int numbers seem to cause chaos - im pretty sure this is just the heaps backend, but ill check the others:

Scale 1.5: