Hi The wx RTTI was used in the ill-fated Borland RAD-Designer, so there we, as library developers, had to expose this information about our widgets, and we did this using the metadata mechanisms, just adding some more properties to the meta information about the properties... Best, Stefan
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of John Torjo Sent: Freitag, 12. November 2004 20:43 To: boost@lists.boost.org Subject: Re: [boost] Re: GUI Library Proposal for a Proposal
There were some additional requirements for this kind of runtime information, as it was directed towards RAD-Tools and not for crossing languages
- Grouping of properties (e.g. all props dealing with the layout of a control, dealing with the appearance etc)
- Additional meta information whether the property should be persisted or not (properties useful for GUI-data binding but not for persistence), construction properties (after creation read-only), always read-only properties, help strings etc
I see these on top of reflection. That is, once the RAD-tool has the reflection mechanism, then it can allow the user to say: - this is readonly - this is persistable, etc.
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 _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost