Each GTK+ toplevel window runs it's own thread in GTK+ for BeOS. GDK is thread-safe. Since the compiler on BeOS is gcc and g++, of course you can use C just fine. It is the higher-level libraries which are written in C++, like BeOS's native interface toolkit. Mixing C and C++ isn't a problem.
Others could port Gtk-- to beos, but it's not a priority at all.
The BeOS version does run themes, although the only one so far that I've tried is ThinIce. It works wonderfully.
Slashdot Mirror
How much work would it be to integrate the changes required for OS/2 into the main GTK+ tree? Is it all build process stuff?
-Shawn
Each GTK+ toplevel window runs it's own thread in GTK+ for BeOS. GDK is thread-safe. Since the compiler on BeOS is gcc and g++, of course you can use C just fine. It is the higher-level libraries which are written in C++, like BeOS's native interface toolkit. Mixing C and C++ isn't a problem.
Others could port Gtk-- to beos, but it's not a priority at all.
The BeOS version does run themes, although the only one so far that I've tried is ThinIce. It works wonderfully.
This isn't GNOME news. It's GIMP news. CmdrTaco should have used the Wilber the GIMP icon instead. ;-)
-Shawn