https://linen.dev logo
Powered by
# haxe-ui
  • h
    not quite sure how to record my deps yet. Starting to think manual git clone at a commit, haxelib dev is going to be the way to get anything reproducible
  • b
    lix might be your friend here, i dont use it personally, but i think it will do what you are after
  • h
    I've heard of it but not looked into it - might be time - thanx
  • p
    Or just 
    git submodule add <url> lib/<name>
    Who needs package managers when you have git?
  • b
    ☝️
  • h
    I'll have to look that up. What does that do ?
  • p
  • h
    How does that manage version dep ?
  • p
    A submodule points to a specific commit of a library. And since it's tracked inside the git repo for your project there's no risk of an external update breaking anything.
  • h
    I assumed it must but I couldn't see where you specified that commit. I'll read it through later more closely.
  • h
    That said then why haxelib at all ?
  • h
    Although it means haxe lib dev is then tied to github unless the submodule thing can interoperable with other vcs
  • b
    and this point i basically only use 
    haxelib dev
    and 
    haxelib git
  • h
    🪦 haxelib version deps I guess. Been feeling like that for little while now. I'll have a look at how that model works
  • s
    drop_files event can be applied only to Screen.instance.frame?
  • b
    i wouldnt have thought so, on haxeui-hxwidgets, each component exposes a native (wx) window... i think its call "window"... so "myComponent.window" will give you the native hxWidgets widow
  • b
    so im assuming you could just use that window instead of the top level wx frame
  • b
    this works fine:
  • s
    that is, buttons and text fields with labels also have their own window?
  • b
    Copy code
    haxe
@:build(haxe.ui.ComponentBuilder.build("assets/main-view.xml"))
class MainView extends Box {
    public function new() {
        super();
    }
    
    private override function onReady() {
        super.ready();
        setupDrop(dropTarget1, theLabel1);
        setupDrop(dropTarget2, theLabel2);
        setupDrop(dropTarget3, theLabel3);
        setupDrop(dropTarget4, theLabel4);
    }
    
    private function setupDrop(target:Component, label:Label) {
        target.window.dragAcceptFiles(true);
        target.window.bind(hx.widgets.EventType.DROP_FILES, function(e:hx.widgets.Event) {
            var dfe = e.convertTo(DropFilesEvent);
            trace("on dropped - " + dfe.numberOfFiles);
            label.text = dfe.files.join("\n");
        });
    }
}
  • s
    thanks!
  • b
    Copy code
    xml
<box style="padding: 5px;" width="800" height="600">
    <grid width="100%" height="100%">
        <box id="dropTarget1" width="50%" height="50%" style="background-color: #FFCCCC">
            <label text="Drop Some Files" id="theLabel1" verticalAlign="center" horizontalAlign="center" style="text-align:center" />
        </box>
        <box id="dropTarget2" width="50%" height="50%" style="background-color: #CCFFCC">
            <label text="Drop Some Files" id="theLabel2" verticalAlign="center" horizontalAlign="center" style="text-align:center" />
        </box>
        <box id="dropTarget3" width="50%" height="50%" style="background-color: #CCCCFF">
            <label text="Drop Some Files" id="theLabel3" verticalAlign="center" horizontalAlign="center" style="text-align:center" />
        </box>
        <box id="dropTarget4" width="50%" height="50%" style="background-color: #FFFFCC">
            <label text="Drop Some Files" id="theLabel4" verticalAlign="center" horizontalAlign="center" style="text-align:center" />
        </box>
    </grid>
</box>
  • b
    also, btw, you asked about a dialog to open a directory, right? Well, haxeui doesnt have it, but hxWidgets does, and since you are using hxWidgets for the file drop, you could also just use it for the dir dialog
  • b
    kinda yeah, in reality, on haxeui-hxwidgets a "component" is kinda a wrapper around a native component window (provided by wx/hx widgets)
  • b
    and properties and functions are "behaviours" that are replaced from the core ones to ones that make sense for wxwidgets
  • b
    so "button.text" (in core) is a "behaviour", the default behaviour is a composite behaviour that looks for the haxeui-core label (inside the button, or creates it if it doesnt exist) and sets its text. Obviously, for native components this doesnt make sense (since there is no "haxeui label" inside a native button component), so haxeui-hxwidgets replaces this behaviour with one that does make sense
  • p
    Another reason not use dependencies from haxelib: Haxelib still uses md5 to store passwords. So haxelib packages could be compromised at any moment.
  • b
    thats just shitty. why didnt haxelib switch to a better encryption yet?
  • p
    No one has sent a PR :) This issue has been open since 2016: https://github.com/HaxeFoundation/haxelib/issues/314
  • b
    so the problem is password reset?
1...114411451146...1687Latest