Yup, hxWidgets is independent of haxeui anything. There are two layers:
-
wx.widgets.*
(ie,wx.widgets.Button
) - these are just externs for haxe (hxcpp) for wxWidgets and can be used as is - but working with externs, esp. c++ externs can be… … difficult. -
hx.widgets.*
(iehx.widgets.Button
) - these are nice haxe wrappers for the externs so you can just donew Button(...)
and be done with it (and manages all the pointers etc). They also make things a little more “haxey” in the sense you havemyButton.bitmap = ...
rather than the traditional wx way ofmyButton.setBitmap(...)
As for people using hxWidgets over haxeui-hxwidgets, i honestly have no idea. I do think there are some for sure - just no idea how many.
Main “problem” with just using hxWidgets is you are now locked into wxWidgets which is certainly the main goal of haxeui: no framework lock in… well, except haxeui ofc!