Yeah, the Winter is coming) (or Q- What does it mean), and we need to be prepared. This will be a post blog I'm thinking about. The reason is that a new major version of the c++ standard is a great opportunity for all of us to improve our programming experience, but it is also a lot of work as library maintainer and tester. Nana already has experience with this: the c++03 version was maint
The Goal and the goals of nana. : I just added this nana blog. Jinhao added this text some months ago on the wiki, with the intention of getting people helping to improve it. But I afraid it have not a good visibility there. I hope it will help people understand a few things, and that it will be improved. (you can just improve the wiki, and I will port it back)
The really important part is the API (the design of the global structure, main classes and functions)
So, maybe, there should be some discussion about this?
The first thing that hits me when I look at nana's API design is the large numbers of things that serve almost the same purpose but are not quite identical. This really clutters up the design and makes nana hard
Hi, I am using gcc-7.3.0 (provided with qt-5.13.1). When i try use nana-1.7.2 then there is a lot of linking problems with filesystem, either when i use nana or std filesystem. All of them are related with filebox and filesystem units.
1 - first approach - default build
cmake -G "MSYS Makefiles" -DCMAKE_INSTALL_PREFIX=/d/work/libextern/windows_mingw_x86_gcc_7.3.0/nana-1-7-2 ../nana
I'm working on a new project and I would like to create a customizable layout where the user can show/hide, arrange, move, resize, etc ... several panels. As reference example think to the MS Visual Studio editor.
I've worked a little with the DOCK field and it seems to be a good start but not yet complete.
Is there someone who use the DOCK field? If yes, what are your impr
I find that many people use MinGW on Windows, but some redistros don't support standard library and COM well, and the configurations for MinGW and nana are complicated, therefore people often encounter the compiling/linkage errors.
So, I decided to create a simple IDE which would contain a MinGW and compiled nana. Also will provide a package management that can easy to update MinGW and nana,
Hello, first of all thanks for your great work! :-)
For the listbox there are two models. Typically, if you have complicated data and you want to avoid data duplication and senseless back and forward conversions, you'd pick the shared_model. The problem is that this model still forces you to do unnecessary conversions. If you pick a shared_model and want to handle the container yoursel