bpaf VS rbfx

If you want to make smart decisions depending on widths of the cells - you have to consume the whole iterator to see what is the widest cell out there, it could be the last one for example. During that iteration you'll want either to store the values somehow or store preformatted bits in a string - something like this https://github.com/pacak/bpaf/blob/master/src/buffer.rs

bpaf does it here, giving access to primitives like "dump names of this parser" or "dump help for this subparser": https://github.com/pacak/bpaf/blob/semantic/src/docugen.rs

https://github.com/pacak/bpaf/blob/master/src/from_os_str.rs - a concrete example

https://github.com/pacak/bpaf/issues/50 - I would appreciate some feedback from a new user on naming conventions used - there or here is fine.

Most of the code change is here: https://github.com/pacak/bpaf/pull/57 https://github.com/pacak/bpaf/pull/60

Something like this, handles example from the ticket at least (sans hex digits) https://github.com/pacak/bpaf/blob/master/examples/sensors.rs

see https://github.com/pacak/bpaf/blob/rc-0.5.5/examples/custom_usage.rs

good engines for C++ that meet your requirements https://github.com/u3d-community/U3D https://github.com/rbfx/rbfx i highly recommend taking a look at rbfx, U3D doesn't have all the fancy features that rbfx has but deep down they are the same engine almost. They are forks of Urho3D, a mature engine that has existed from the year of 2011/2010.

Urho3D is dead. There is the U3D project which is essentially a maintenance fork made after the original project was taken over by a crazy Russian nationalist. There is also rbfx which is a progression fork that is working to make improvements such as to the PBR rendering pipeline, making it work with C# if desired, as well as rebuilding and improving the editor. The original Urho3D is soon to be even more dead than currently, since the discourse forum is set for archival and deactivation at 4:00 AM tomorrow morning.

Go to: https://github.com/rbfx/rbfx, they have a discord but IIRC it's basically just a CMake build so you flip the flags to say "WebGL" or "Emscripten" or w/e and CMake will basically tell you everything that's wrong.

If anyone is looking for a Unity alternative, the guys at rbfx are doing a great job revamping the old Urho3D codebase: https://github.com/rbfx/rbfx

It has good C# scripting support, a nice editor and modern rendering pipeline.

You could try Urho3D or its newer fork rbfx.

I use an engine called rbfx which is a fork of the Urho3D engine. A lot of it is just the fact that I've been using it for over a decade, so I am comfortable with it. I'm a programmer, not really comfortable with integrated editor engines such as Unity or Godot, and the easy C++ extensibility of the engine appeals to me. Plus it's decently powerful, and well supported on a lot of platforms (I build for Windows, WebGL, and very occasionally RPi for the most part) and is open source to satisfy that stubbornly libertarian side of my character.