MacArthur, Ian (SELEX GALILEO, UK) wrote: > ... > I thought (and am likely wrong) the "nib" idea was that, in your app > bundle, you have localised sub-folders, plus a default. When the app > runs, it loads the appropriate nib for your locale, if present, or the > default one if not, and forms the GUI. > These localised items are "hard coded" by the app creators, and are > basically fixed at compile time. They are not intended to be modified by > the end-user (although I think sometimes they can be.)
They can be using Interface Builder. Basically, Interface Builder reads and writes nib files, which serialize the objects in the user interface. If we did a simplified .fl parser that supported standard FLTK widgets with no extra code and callbacks specified by name only, we would have a (very) basic form of what you get with Cocoa. Adding custom class support would require the application to register that class with the parser. Similarly, widget pointers could be set by name... -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
