https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    open to suggestions (naming stuff is crappy)
  • b

    https://cdn.discordapp.com/attachments/565569107701923852/1109476708249260093/image.png▾

  • b
    Copy code
    xml
        <popup-panel width="100">
            <listview>
                <data>
                    <item text="Item 1" />
                    <item text="Item 2" />
                    <item text="Item 3" />
                    <item text="Item 4" />
                </data>
            </listview>
        </popup-panel>

        <list-popup width="100">
            <data>
                <item text="Item 1" />
                <item text="Item 2" />
                <item text="Item 3" />
                <item text="Item 4" />
            </data>
        </list-popup>

        <popup-panel width="150" panelSelectionEvent="menuselected">
            <menu>
                <menu-item text="Item 1" />
                <menu-item text="Item 2" />
                <menu-item text="Item 3" />
                <menu-separator />
                <menu text="Menu A">
                    <menu-item text="Item 1A" />
                    <menu-item text="Item 2A" />
                    <menu-item text="Item 3A" />
                </menu>
                <menu-separator />
                <menu-item text="Item 4" />
                <menu-item text="Item 5" />
                <menu-item text="Item 6" />
            </menu>
        </popup-panel>

        <number-popup width="100" />
  • b
    (the rationale, btw, is that dropdown is trying to be way too many things, and i frequently abuse it to fake other types of controls - like a MenuDropdown)
  • b
    menudropown eg (its super hacky and a total abuse of the actual component):
  • b

    https://cdn.discordapp.com/attachments/565569107701923852/1109479218737319977/image.png▾

  • a
    i'd say hard no to popup because that is a already assigned to a different expected behaviour
  • b
    is it?
  • a
    pop up implies a "window" or "alert" kind of thing
  • b
    true, thats what i keep going back and forth on
  • a
    what's wrong with, at least for now, dropdownpanel?
  • b
    "selector" is something i thought about, but not sure it make sense
  • b
    dropdownpanel is alright i guess... probably better than popup for sure
  • b
    i was trying to avoid "dropdown" altogether tbh
  • b
    what about like "MenuSelector", "ColourSelector", "NumberSelector", "ListItemSelector", etc?
  • a
    i'd say there's no need to reference it with components built on it - like 
    ColorSelectorPopup
    can just be 
    ColorSelector
    or 
    ColorPicker
  • b
    true, but the idea is also that you could build your own, with relative ease, so the naming of the core class(es) is important
  • a
    if i understand it right, DropdownPanel seems more like a "lower level" way to interact with things
  • b
    core one here i guess would be "ItemSelector"
  • b
    well, dropdownpanel would basically be a dropdown... the "panel" there would be a listview
  • b
    and the renderer would be a normal item renderer and the trigger would be the whole component
  • a
    right so "core" would have dropdownpanel but you would build a 
    ListPicker
    or 
    Dropdown
    (conventional names i think) on top of the DropDownPanel
  • b
    no, core would have like an "ItemSelector" (or ItemPicker)... currently called "PopupPanel", and other "pickers" would be based around that
  • a
    hmm, i think dropdown seems like the "best" then
  • b
    like: ListItemPicker, ColorSelector, MenuItemSelector, etc
  • b
    but what about like, for instance a "combo box" (ie, list view being the "panel", textfield being the "renderer" and a dropdown arrow icon / button being the "trigger")
  • b

    https://cdn.discordapp.com/attachments/565569107701923852/1109485001231310898/image.png▾

  • b
    kinda like that (but a textfield and not a number stepper)
  • b
    StringDropDown?
  • b
    EditableStringDropDown?
1...167816791680...1687Latest