Haxe

oh i forgot to add docs to the class itself

ok i made the pr, it only contains docs for NumberStepper

ill doc more and more classes, im just kinda testing this style of docs now

will probably submit groups of classes later tho

"classic" number steppers should look more correct now btw

also, e few things aabout TextField:
1. does maxChar applied to text set via code
2. does restrictedChars behave like normal, regex set?

i mean that `0-9` turns into `~/[0-9]/`, and `^0-9` turns into `~/[^0-9]/`

1. not sure, i would have expected it to, if it doesnt it sounds like a bug
2. also not sure, i didnt write the restrictedChars stuff, so not 100% what it uses, i _think_ its modeled after openfl /flashs api

i assume it uses regex, but dont actually know that to be the case

ill just fix that later if its wrong i guess

and about html text, does it support all HTML tags or just a subset?

defo a subset, and its not all backends either

+ why is `icon` a string? doe it accept a path?

yeah, i would just pretend like its all backends... backend specific docs can come as and when

icon is actually a variant... it can be a file path, a resourceid, web address (http/s) or backend specific image data

before i just thought its a wrapper for file paths

nope, its a wrapper for different types, well abstract for different types

```haxe
enum VariantType {
    VT_Int(s:Int);
    VT_Float(s:Float);
    VT_String(s:String);
    VT_Bool(s:Bool);
    VT_Array(s:Array<Dynamic>);
    VT_DataSource(s:DataSource<Dynamic>);
    VT_Component(s:Component);
    VT_Date(s:Date);
    VT_ImageData(s:ImageData);
}
```

button::icon / image::resource being good examples of it being able to accept different types automatically