2 ms·

I don't really get why this is called Boost.UI. The list of example seem to just try and have one for every boost library, is that the goal? Or is the goal to g

I don't really get why this is called Boost.UI. The list of example seem to just try and have one for every boost library, is that the goal? Or is the goal to get this added to boost? As long as it's not an officially accepted library, I think using boost in the name and code is quite misleading. Even more misleading is that it claims to be all native, while underneath it simply uses wxWidgets. I'm sure it's a way to go, but don't hide your dependency and make it sound like you actually implemented cross-platform native UI elements.

kosenko 9y ago
It is non official Boost library like an other libraries: http://blincubator.com/alphabetically/ http://blincubator.com/alphabetically/ Mentioned examples demonstrates integration with other Boost libraries. Yes, goal is to be added to Boost. Boost.UI application eventually uses native widgets. Cross-platform elements can't be native by definition. Boost.UI is about interface, but not implementation. And I would like to omit stereotypes about wxWidgets.
- eXpl0it3r 9y ago
  > Mentioned examples demonstrates integration with other Boost libraries. What do you understand with "integration". Do they really integrate or do you just demonstrate how each library can be used and then somehow represented with a UI? Examples are great, but making each one specifically for some Boost library feels odd. Are you showing off Boost libraries or are you showing Boost.UI's functionalities? I don't think anyone will doubt that Boost libraries can be used with Boost.UI. > And I would like to omit stereotypes about wxWidgets. That's okay, but I still find it a bit misleading, when only at the build stage the compiler will tell you "oh btw this library requires you to have wxWidget headers". When I use a library, I want to know its dependencies upfront and not having to browse the source code or being told through a compiler error.
  - kosenko 9y ago
    For example Boost.Geometry and Boost.Polygon could be used with Boost.UI coordinates, Boost.Chrono (and std::chrono) in Boost.UI on_timeout() function, Boost.Date_Time library is used in date and time pickers etc. wxWidgets is mentioned in build instructions.

kosenko 9y ago

It is non official Boost library like an other libraries: http://blincubator.com/alphabetically/ http://blincubator.com/alphabetically/ Mentioned examples demonstrates integration with other Boost libraries. Yes, goal is to be added to Boost. Boost.UI application eventually uses native widgets. Cross-platform elements can't be native by definition. Boost.UI is about interface, but not implementation. And I would like to omit stereotypes about wxWidgets.

eXpl0it3r 9y ago
> Mentioned examples demonstrates integration with other Boost libraries. What do you understand with "integration". Do they really integrate or do you just demonstrate how each library can be used and then somehow represented with a UI? Examples are great, but making each one specifically for some Boost library feels odd. Are you showing off Boost libraries or are you showing Boost.UI's functionalities? I don't think anyone will doubt that Boost libraries can be used with Boost.UI. > And I would like to omit stereotypes about wxWidgets. That's okay, but I still find it a bit misleading, when only at the build stage the compiler will tell you "oh btw this library requires you to have wxWidget headers". When I use a library, I want to know its dependencies upfront and not having to browse the source code or being told through a compiler error.
- kosenko 9y ago
  For example Boost.Geometry and Boost.Polygon could be used with Boost.UI coordinates, Boost.Chrono (and std::chrono) in Boost.UI on_timeout() function, Boost.Date_Time library is used in date and time pickers etc. wxWidgets is mentioned in build instructions.