https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    as long as you are willing to theme the various parts of the core haxeui, you are gravy, or write your own core parts, and theme them, also fine
  • b
    ... ... ... ... haxeui core is a module of it itself... ...
  • w
    * brain explodes
  • w
    dude stop
  • w
    I think Frying pan is saying that that ditinction comes with a history of knowledge that newcomers do not have
  • b
    wanna write a component in haxeui, sure, have at it... make a component, make it do anything and as long as the backend honours it, you'll be fine. A haxeui "button" is just a haxeui component that lives inside haxeui-core
  • e
    ok cool
  • e
    there is a list of components that "come with haxeui"
  • e
    what is available without creating a custom component
  • b
    with haxeui-core, yeah, they are all composites
  • b
    they have native counterparts
  • e
    sure, a "button" in haxeui might map to a native button or a FlxButton or a custom thing, but a button is a "base" component as far as anyone creating something using haxeui knows
  • b
    true enough, but from haxeuis perspective, its just a component
  • b
    its a box that has states
  • b
    haxeui doesnt "know" what a "slider" is... or what haxeui-core includes, but it means nothing to haxeui-core (especially as that can also be abstracted to other, non composite backends)
  • e
    ok but haxeui-core includes some definition for a slider somewhere, no?
  • b
    it has an abstraction, sure, one you can build on
  • b
    this is a slider in haxeui (dox excluded):
  • b
    Copy code
    @:composite(SliderBuilder)
class Slider extends InteractiveComponent implements IDirectionalComponent {
    private function new() {
        super();
        cascadeActive = true;
        actionRepeatInterval = 10;
    }
    @:clonable @:behaviour(MinBehaviour, 0)         public var min:Float;
    @:clonable @:behaviour(MaxBehaviour, 100)       public var max:Float;
    @:clonable @:behaviour(DefaultBehaviour, null)  public var precision:Null<Int>;
    @:clonable @:behaviour(StartBehaviour, null)    public var start:Null<Float>;
    @:clonable @:behaviour(EndBehaviour, 0)         public var end:Float;
    @:clonable @:behaviour(PosBehaviour)            public var pos:Float;
    @:clonable @:behaviour(CenterBehaviour, null)   public var center:Null<Float>;
    @:clonable @:behaviour(DefaultBehaviour, null)  public var step:Null<Float>;
    @:clonable @:behaviour(MinorTicks, null)        public var minorTicks:Null<Float>;
    @:clonable @:behaviour(MajorTicks, null)        public var majorTicks:Null<Float>;
    @:clonable @:value(pos)                         public var value:Dynamic;
    @:call(PosFromCoord)                            private function posFromCoord(coord:Point):Float;
}
  • e
    ok, those are all things you could list on a documentation page
  • b
    the implementation is kinda variable (and they dont always apply)
  • b
  • b
    are they not? Granted the docs are woefully out of date
  • e
    i was going based off this statement
  • e
    ¯\_(ツ)_/¯
  • b
    i think thats more about completion in vscode
  • b
    but there isnt any definitive schema for haxeui, and there cant be
  • b
    just "what it found in the classpath"
  • a
    I think what these guys are saying is that it's possible to create a schema with a manual procedure. And haxeui comes with components. Isn't it possible to just manually run the command and dump the schema in the repo so people can copy paste that?
  • b
    you can, right now, run a haxe command that will build an .xsd
1...127712781279...1687Latest