It is more than practical to have the boost gui abstraction cover the most common concepts. This not only makes it small and easy to
true. but...
implement, but also allows me to write directly to WxWidgets where it makes sense.
The only problem I see IMO is abstracting events (+ the event arguments). That said, I do plan to abstract away the win32 layer, but this will most likely happen in the distant future - since I have so many other things yet to implement.
A well designed "gui abstraction layer" would have the following properties:
* move the technology of binding forward
would you please be more specific?
* allow for the choice of being able to write "boost standard gui code" vs taking advantage of whatever specific thing you are working with
This IMO will most likely end up being pretty difficult. I'm quite curious how you can provide the right balance between offering some common features and allowing access to the underlying implementation.
These principles, also have the advantage of placing a combination of ltwindows and win32gui in a spot where a combination of the two would in fact meet those properties. AND it would be accomplishable in a short timeframe.
Unfortunately, I don't have the time to investigate. So, are you up for something like this (study both libs and find common ground)? Writing cross-platform GUI is far from easy. Also, you could work with Reece as well. Best, John -- John Torjo, Contributing editor, C/C++ Users Journal -- "Win32 GUI Generics" -- generics & GUI do mix, after all -- http://www.torjo.com/win32gui/ -- v1.5 - tooltips at your fingertips (work for menus too!) + bitmap buttons (work for MessageBox too!) + tab dialogs, hyper links, lite html