https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    Coconut has all this typed. Pretty neat.
  • b
    Until you wanna do something that's missing in the types. 😄
  • b
    should be typed in haxeui too... not the same way coconut works, for sure, but 
    <button bob="tim" />
    would turn into 
    var c = new Button(); c.bob = "tim";
    (which would fail compilation because there is no bob prop)
  • b
    which is the reason this operator overloading is a no go for me as it stops that and moves it to runtime
  • b
    Any thoughts on a code-hinting friendly xml scheme?
  • b
    xsd would be nice, but the issue there is a) most ides dont support it and b) it need to be some type of dynamic xsd
  • b
    :/
  • b
    There's lot of talk around inlined markup in Haxe, with no consensus so far.
  • b
    Would be fun if we eventually had some way to hook into autocompletion from inside macros.
  • b
    @silly-kangaroo-60312 I don't think accessor methods are comparable to dynamic access
  • s
    yeah, they do different things. agree. I just mentally lump them together when comparing haxe to other languages where a property is basically just a namespaced variable
  • b
    namespaced variable?
  • s
    well, if you think about objects as namespaces
  • b
    I don't really follow, properties aren't really any different from variables in that regard
  • b
    to me, a property is generally syntactic sugar for getter / setter methods
  • s
    the point is that in haxe, compared to other languages, just setting or getting a property can do a lot more and there is a chance of all kinds of side effects
  • b
    that's the case in every language with properties
  • s
    yeah, I was just saying in haxe it's much more common practice, so it's not really that surprising
  • b
    I don't know, I think it's pretty common practice in other languages with properties too, C# for instance... 😄
  • b
    I guess this discussion isn't really going anywhere
  • s
    yeah, this is pretty subjective.
  • b
    as for having side effects in accessors.. IMO that should be considered bad practice regardless of the language
  • b
    well, in getters I should say
  • b
    i also think that there is a world of difference between getters / setters doing "extra stuff" and dynamic properties on classes, ie "foo.bar" (where .bar doesnt exist) - they are totally different things
  • b
    yeah
  • b
    so im (slowly) peicing the haxeui.org website back together, and part of that is a new (and proper component explorer)
  • b
  • b
    ... ... ... PRs more than welcome! 😉 😄
  • b
    this is it in the context of the "new" (not really new at all - mainly scraped from waybackwhen machine) site:
  • b
    im not convinced... :/
1...899091...1687Latest