https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • h

    handsome-television-62908

    11/18/2019, 9:27 AM
    since property seems like a "meta" thing, why not do something like . . .
    <meta type="property" name="..." bind=".." />
    This is totally just another way to write what you say; but, I think, it may make a lot of sense if you plan on extending meta-features without reserving so many property names
  • b

    bright-gpu-74537

    11/18/2019, 9:27 AM
    yeah, thats a great idea
  • b

    bright-gpu-74537

    11/18/2019, 9:28 AM
    nice and seperated... and, one of things i wasnt happy about "" was what if you wanted a custom component called "property", which is more than feasable
  • h

    handsome-television-62908

    11/18/2019, 9:29 AM
    I was thinking the same thing
  • b

    bright-gpu-74537

    11/18/2019, 9:29 AM
    👍
  • b

    bright-gpu-74537

    11/18/2019, 9:29 AM
    great minds think alike, but fools seldom differ...
  • b

    bright-gpu-74537

    11/18/2019, 9:29 AM
    😄
  • h

    handsome-television-62908

    11/18/2019, 9:30 AM
    I've not heard of the second part of that phrase but now I'll have that in mind hahaha
  • b

    bright-gpu-74537

    11/18/2019, 9:30 AM
    hahaha, yeah
  • h

    handsome-television-62908

    11/18/2019, 9:37 AM
    So here's something . . . right now I'm trying to do a make-shift component similar to google calendar's timeline thing. I'm really doing the quickest path, probably most inefficient too, of mocking it and my idea seems really dumb. But, what do you think of mocking this by layering 1: a table for the base timeline 2: floating elements (the blue blocks) inside of an absolute element.
  • h

    handsome-television-62908

    11/18/2019, 9:38 AM
    I haven't seen what the grid can do entirely but I don't imagine it supports the ability to replicate this too easily
  • b

    bright-gpu-74537

    11/18/2019, 9:39 AM
    grid wont allow you to overlap things
  • h

    handsome-television-62908

    11/18/2019, 9:40 AM
    Gotcha. And I guess it's really just a limitation of what could be shown through xml, since this is better handled through imperative code
  • b

    bright-gpu-74537

    11/18/2019, 9:40 AM
    im not even sure table will do what you want it to... is that screen shot above haxeui? Or just a mock up in a prototyping app?
  • h

    handsome-television-62908

    11/18/2019, 9:40 AM
    that's google calendar, I'm trying to mock that view
  • b

    bright-gpu-74537

    11/18/2019, 9:41 AM
    i think a scrollview with an absolute for its contents, and then position everything where you want it manually
  • b

    bright-gpu-74537

    11/18/2019, 9:41 AM
    ofc, that could be wrapped into a custom component with util functions for doing that "smartly" ie, "addItem(new Date())"
  • h

    handsome-television-62908

    11/18/2019, 9:42 AM
    Definitely the direction I was headed in; I hope I can get this view done in about 2 hours or less haha
  • b

    bright-gpu-74537

    11/18/2019, 9:42 AM
    just a fake mockup of it? or a working component?
  • h

    handsome-television-62908

    11/18/2019, 9:43 AM
    kind of both, I know the fake mockup will take me a considerable amount of time since I'm so unfamiliar with haxeui still
  • h

    handsome-television-62908

    11/18/2019, 9:43 AM
    but I'm doing my best haha
  • b

    bright-gpu-74537

    11/18/2019, 9:54 AM
    its all completely fake ofc, but that type of thing?
  • b

    bright-gpu-74537

    11/18/2019, 9:54 AM
    Copy code
    xml
    <vbox style="padding: 5px;">
        <style>
        .item {
            border: 1px solid #888888;
            background-color: #CCCCFF;
            border-radius: 5px;
            padding: 5px;
            filter: drop-shadow(1, 45, #000000, 0.15, 1, 1, 1, 3, false);
        }
        </style>
        <scrollview width="500" height="500" contentWidth="100%">
            <hbox width="100%">
                <vbox width="100" style="spacing: 30px;">
                    <label text="09:00" />
                    <label text="10:00" />
                    <label text="11:00" />
                    <label text="12:00" />
                    <label text="13:00" />
                    <label text="14:00" />
                    <label text="15:00" />
                    <label text="16:00" />
                    <label text="17:00" />
                    <label text="18:00" />
                    <label text="19:00" />
                    <label text="20:00" />
                    <label text="21:00" />
                </vbox>
                <absolute width="100%">
                    <box styleName="item" width="100%" height="40">
                        <label text="Item 1" />
                    </box>    
                    <box left="0" top="50" styleName="item" width="300" height="250">
                        <label text="Item 2" />
                    </box>    
                    <box left="60" top="20" styleName="item" width="270" height="140">
                        <label text="Item 3" />
                    </box>    
                </absolute>
            </hbox>    
        </scrollview>
    </vbox>
  • h

    handsome-television-62908

    11/18/2019, 9:56 AM
    Oh wow yeah, man that's very very similar
  • h

    handsome-television-62908

    11/18/2019, 9:57 AM
    and I don't imagine it would be hard to wrap the labels into boxes that extend 100% width . . . so that's pretty damn good haha
  • h

    handsome-television-62908

    11/18/2019, 9:57 AM
    Dude thank you so much! That's a great start
  • b

    bright-gpu-74537

    11/18/2019, 9:57 AM
    yeah, and get the custom component to expose so functions to inteliigently place "boxes" in the absolute based on times
  • b

    bright-gpu-74537

    11/18/2019, 9:57 AM
    no worries 🙂
  • h

    handsome-television-62908

    11/18/2019, 10:02 AM
    I will definitely be moving on to that as soon as I can haha - you saved me a lot of time though, I really appreciate it
  • b

    bright-gpu-74537

    11/18/2019, 10:03 AM
    i would even be tempted to make the component understand datasources too ;) Its probably waaaay out of scope though for now, and more for the "final", real component
1...141142143...1687Latest