Well, I am sorry, but I am confused about the thesis.
For a moment, I thought you are going to do Chameleon replacement (for U++?).
Well I'm not going to replace entire Chameleon, I'm thinking only at the part that read the look from the system. If U++ get ported to MacOSX how will the glue code which read the look from system will looks like? I'm trying to do a lib with which the controls will interact in the same way and system dependent parts to be hidden behind it. Well maybe you know but MacOSX have specifications about the space between buttons, the distance from the outer frame of the window, etc and if an application doesn't respect these hints it will look "ugly" compared to other Mac applications and i know that mac users are choosy when talking about the look. So at this time U++ Chameleon can't do these kind of actions like reading size hints and what I'm trying to do is library to make it possible.
If you believe it doesn't worth then I will make something else regarding my thesis. When I've choose cross-platform GUI as a subject of my thesis I've thought that I will may help U++ while working on thesis and also do something i like to do.
You're the one who have the final word It worth or not?
(Still some changes to widgets will have to be made in order to use the new system for size hints and how widgets will behave)
If you think that is simple and better to fix the current Chameleon state then i apologize for wasted your time.
Andrei
P.S. I may send a list with current glitches in Chameleon in gtk+ or better try to solve these and send the patches.