https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • f
    On the downside, you will have less design liberties with wxwidgets than with composites.
  • p
    That's not a downside if the goal is to have a native looking app.
  • a
    yeah
  • a
    contextual
  • a
    also having limitations are useful to help things move along
  • f
    Yes and no, not all of wxwidgets is perfectly implemented in haxeui. For example, normally you could make some combobox with bitmap inside of them and a few complex things, but haxeui implements for now only the most common, and most useful widgets, which is enough for 90% tooling applications.
  • a
    fair, i guess those limitations also extend to components as well
  • c
    To give you an example of a potential unexpected limitation. In MacOs will the automatic expansion of snippets work? Will password fields be recognized by the Keychain as, well, password fields and offer auto complete? Will ctl+a/e jump to the start end of the line?
  • p
    > Will password fields be recognized by the Keychain as, well, password fields and offer auto complete? Depends on wether HaxeUI (and WxWidgets) have the concept of a "password field".
  • f
    (I'm not on mac) but Ctrl a/e will work I think
  • c
    I mean that the maintainers of the library have to write code to ensure that all the native behaviors are implemented (kind of duplicated) the same as in the native components
  • a
    on native targets (wxwidgets) the components are native, so they'll behave as expected on the OS, if not, there may need to be some kind of extern/implementation to be added
  • f
    I don't know if passwords fields is implemented in haxeui ( haven't need it). For autocompletion, it 's not in haxeui but it is in wxwidgets, and these kind of things are quite easy to implement
  • a
    so textarea shortcuts should all work as expected
  • a
    password fields are implemented
  • a
    they work as normal on the html target as any other site as an example
  • c
    And what is composite exactly? Some kind of canvas render?
  • c
    Sounds good
  • f
    exactly
  • a
    composite is a rendering backend, typically used for game dev but can also be utilised for ui application development
  • f
    In fact not exactly, depends on the backends.
  • p
    Composite basically means that it's not native widgets, but custom widgets implemented on top of eg OpenFL sprites.
  • c
    And can be combined? Or as soon as you add one composite component the app has to go full composite?
  • a
    depends on if you're using composite specific features
  • a
    all haxeui components aim to behave the same across all backends
  • a
    outside of that requires personal workarounds, conditional compilation kind of stuff
  • f
    Basically you can haxeui will know what to do. Imagine you have special type of button with a text an image and a dropdown inside of it. Wxwidgets won't show the dropdown.
  • a
    i'm not sure if an app can use native things + composite
  • a
    maybe javascript could pull that off
  • f
    I think html5 can use both at the same time
1...136013611362...1687Latest