This version has following major changes/additions.
1. The low-level platform interfaces are defined in
the common namespace, 'impl'. To support a platform,
these interfaces need to be implemented.
2. The library uses boost::variant to manage heterogenous
type collections and events. With 'variant' the code is much
more elegant. You'll see a very little use of switch statements
or inheritance chains.
3. Added a *preliminary* menu support (win32 only).
The menus are implemented as Data/Display/View (DDV) objects.
Structually, a menu item is no different from a window.
A menu manager combines menu DDV's into a hierarchical structure.
The library itself resides in header files in notus/notus.
The low-level support files are static libraries, one for each platform.
The executable files are in the build folder.
There is NotusGuide.pdf in the doc folder.
It has a lot of technical information about
the library. I hope it'll eventually became a developer's guide.
You can use .mak (GCC/minGW) or MSVC project files to build the samples.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A new Design Draft build 1.0.02 is available.
This version has following major changes/additions.
1. The low-level platform interfaces are defined in
the common namespace, 'impl'. To support a platform,
these interfaces need to be implemented.
2. The library uses boost::variant to manage heterogenous
type collections and events. With 'variant' the code is much
more elegant. You'll see a very little use of switch statements
or inheritance chains.
3. Added a *preliminary* menu support (win32 only).
The menus are implemented as Data/Display/View (DDV) objects.
Structually, a menu item is no different from a window.
A menu manager combines menu DDV's into a hierarchical structure.
The library itself resides in header files in notus/notus.
The low-level support files are static libraries, one for each platform.
The executable files are in the build folder.
There is NotusGuide.pdf in the doc folder.
It has a lot of technical information about
the library. I hope it'll eventually became a developer's guide.
You can use .mak (GCC/minGW) or MSVC project files to build the samples.