"Max Motovilov" <max@yymap.com> wrote
9. (really 0 in my view) It should use an extensive resource description schema or language (for widget properties, layouts and relations) that is either interpreted at run time or (though I like it less) compiled into code transparently to the user. This resource description should probably be XML-based.
XML adds very little except troubles (IMHO). Enhanced RTTI can be implemented directly in C++, either using: - macros approach (GUI framework called VCF does this) - having class description similar to one found in Boost.Python. AFAIK Daniel Wallin is refactoring this functionality into general purpose library. Builders/customization software/etc than has direct access to always valid GUI information.. /Pavel