> One of the reasons this works so well for Cocoa is that nib files > are serialized Objective C objects, and it is relatively easy to > do that because Objective C classes are dynamically typed and use > a message-passing interface. > > This kind of interface is not easy to reproduce with C++. Qt has > a meta-compiler to support their signal/slot (message-passing) > interface, but you still don't get dynamic typing. > > Probably the best we could do is something like Motif Tools - you > register callback functions and classes, load the interface file, > and then lookup any widgets you need. The widget classes would > need type name, widget name, and static constructor methods at a > minimum, and then we'd need a function to load the interface file > and return the top-level widget.
And let's store the "fl-nib" as a JSON file. Not so much because I think that's a good solution. More because it really annoys the XML folk. :-) -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
