Juraj Kirchheim

I don't think there's much I can do about it. All I can really find out about the parameter is whether it is optional or not: http://api.haxe.org/haxe/macro/Type.html#TFun However, if you...

ouch

Ah yes. I ran into this once. Will look into it. For the time being I suggest using `@:forward(!textInteractionMode)` instead of listing all fields ;)

Well now you know you can and I know it's not enough :D

Ok, the problem comes from an underlying layer. In some sense the whole way in which @:require is handled is rather problematic. I would have liked to just generate the...

> Also, why use html strings if there is a way to not? Because inline markup is an experimental feature that may be drastically changed or even removed from Haxe....

Soo, the error was this: https://github.com/HaxeFoundation/haxe/issues/9379 I've made the three render functions in `ListGroup` optional. As a side note: if you give a body to an `@:attribute function`, it can...

I'd like to propose that npm might be a better place than haxelib to distribute haxe code that is npm specific. Maybe it's just a crazy idea. I haven't thought...

Yep, that's nice. Personally, I think it's ok if the facade is at the same level as the package. [Short names are good](http://stackoverflow.com/a/891589/111466) ;)

> * the "safe cast", which is `cast(expr,T)` > * at compilation : will ensure that the type of `expr` is a subtype of `T` so the cast is valid...