https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • p
    or maybe branch current?
  • b
    yeah, ill probably need to branch, since there will likely be bug fixes in main... makes it a pain to maintain, since i can see 2.0 being months and months and months
  • b
    another option would be to do "one final release" and then git becomes 2.0... and branch the old version in case it needs fixes
  • b
    yeah, the more i think about it, the more i think thats the better path here
  • p
    ya, never sure which direction is best. It just means my main things will stick on the branch and play will be main git
  • b
    well, it also means for all the people on git main (which is most i think) the upgrade process will be gradual
  • p
    true, they will just see bugs appear and adjust
  • b
    rather than just "boom"... 2.0 is now master... enjoy the 17 million errors
  • p
    yep, agreed, I guess I prefer that approach. If stable is needed use 1..x branch'
  • b
    yeah
  • b
    so, to get another voice wrt to the "picker" stuff... does that make sense to you?
  • b
    "DropDown" (for example) would become "ListItemPicker" (effectively - i may alias it to avoid confusion / breaking things, but thats not the point atm)
  • h
    been watching this sail by - interesting and I see your point. The thing I suppose I would ask is - is there anything that you have that doesn't fit the Picker but which would become a picker - you have a bunch of dropdown like thingies which do drop sideways, drop up etc which this will solve by focussing on a different aspect of the behaviour. Is there any case you can think of where the same sort of discord will arise with Picker ?
  • b
    ComboBox type thing...
  • b
    ie, a listview "panel" with a "textfield" renderer
  • b
    EditableStringPicker?
  • b
    or as NotBilly said, just alias to "ComboBox"
  • h
    in some sense is this about trying to disconnect the pop behaviour - some container element appearing - from the how exactly it comes to appear ? Here I'm wondering if Picker captures the essence of the distinction you are trying to draw out
  • h
    Naming is a beast afterall
  • b
    > disconnect the pop behaviour thats certainly true... it could be a "dropdown panel"... it could be a "panel in a dialog", it could be a "sidebar that appears from the bottom"...
  • b
    i feel like "picker" gives the best "intention", ie, "what are you going to do"... "im going to pick a date" (or a number, or a string from a list, etc)... how are you going to do that "well, it depends"
  • a
    ComboPicker instead of ComboBox
  • b
    also works... though ive always hated the "Combo" in ComboBox anyway
  • a
    could move it to OptionPicker
  • b
    that (to me) would be an option-stepper renderer with a listview panel
  • b
    (like number-picker)
  • b
    but yeah, i still think "picker" is the best word here since its a verb and conveys an action, an intention (certainly better than "popup" which conveys a "result")
  • p
    I agree with picker. I dont have preconceived perception of what it is doing besides allowing something to be chosen
  • b
    yeah... it feels like it does what you would expect... though, what about an editable one? ListItemPickerThatCanAlsoBeEditedIfYouWant? 😄
  • h
    I certainly don't have an alternative in mind - but another question - is picker used in this sense in UI frameworks ? Is someone going to know what it means and be able to find what they want easily ? When I think of a picker I think of color pickers of various kinds mostly. I don't necessarily think I would expect to find a dropdown menu component under pickers
1...168216831684...1687Latest