matthiasm wrote: > > On 12.02.2008, at 11:26, Yuri D'Elia wrote: > >> The nice thing about bundles however, is that you can >> have different GUIs for different locales, so I presume this the way it >> is actually used when needed, though I don't see how this is "efficient" >> to maintain in the long term. >> >> Has anyone experience on this? > > > Hah! ;-) I proposed this a log long time ago ;-) > > The idea was to allow FLUID to write efficient resource files that are > then included into the executable and interpreted at run time, creating > the default GUI. It would then be possible to extract the resource file, > localize it using FLUID (including text changes and widget sizes), and > write it back, or provide it as a seperate localized resource file. > > It was (probably rightfully so back then) dismissed as violating the > Fast and Light approach of FLTK. > > Maybe something to consider now?
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. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
