A more accurate list is available in an extraneous file. Here's an excerpt, with version numbers stripped for brevity: Linux, FreeBSD, NetBSD, OpenBSD, BSDi (BSD/OS), Sun (SunOS, Solaris), MkLinux, OS/2, AIX, Digital UNIX/Compaq Tru64, HP/UX, Windows NT, Windows 95 (with cygwin)

LessTif is a clone of the Motif® toolkit. Currently LessTif is partially implemented with most of the API in place. Saying this a lot of the internal functionality is still missing. Compatibility can have several degrees, the ultimate one being binary compatibility. This is the one we're aiming for.

A few Internet based individuals as listed in core.html. Nobody is paid to work on it, all is effort by volunteers. Look for an all-time list of authors in the AUTHORS file in the LessTif distribution, while CREDITS acknowledges the contributions of various other people. Keeping a list of developers for each widget is not really possible mainly because the we're not fanatic about ownership of a widget. We do keep in touch enough to know who's messing with what so we don't overlap too much.

Regularly, questions about LessTif (or about any free Motif®) clone are asked in comp.windows.x or comp.windows.x.motif .

Actually most LessTif widgets work somewhat. Many work fairly well. Things like traversal and focus handling have been worked on, but probably aren't really all that functional yet. The menu system is quickly losing its child diseases (occasionally freezing the X server with grabs). If you're not in a rush when working the menus, the odds are low that you'll get in much trouble. Also dragging in the menus will get you in trouble faster than clicking.

Yes the LessTif Documentation Project (LessDox) check out the LessDox home page at: http://www.lesstif.org/Lessdox/lesstif.html

You should be able to compile and run your code, how well it works is another matter... If it doesn't, then we're very interested in hearing about what doesn't work and why (we can't fix bugs that we don't know about), and we're even more interested in a fix. If your favorite application does work, please tell us so we add it to the list of apps known to work.

Up to now we are very close, all interfaces are in place, we might only have to fight against some remaining bugs ... Therefore, we expanded the source directory tree to make it easy to add new stuff, and to build several versions of the library (and the corresponding tools). So if anybody has a widget, or an application, to offer which can advance us in the 2.x or CDE areas, please E-mail us. Somewhere along 1997 we actually started building 2.0 compliant widgets.

We have some documents which should help to track down bugs in LessTif-based applications. BUG-HUNTING.html describes some specifics of LessTif's built-in debugging facilities while bugs.html covers more general the topic of debugging X11 applications.

You may have an application that's not error-free; or (more likely) one which needs configuration for your site, computer platform, etc. If it's not a bug within the application it probably has to do with your compiler options. If it's indeed that, there are several possibilities. In the examples we'll give now, we'll be using some installation directories that may differ from your installation.

Throughout the Grace docs, saying "M*tif" we actually refer to the M*tif API, defining a set of functions for building graphical user interfaces (GUI) via numerous widgets (buttons, labels, etc). Grace makes a heavy use of the M*tif API. There are several implementations of the interface. The original OSF Motif (see http://www.opengroup.

No, none of the shoes shown at my site are mine. I haven't had the time to take pictures of them yet. Soon, though, very soon.

NVIDIA has provided source code for key portions of the NVIDIA Cg Compiler front-end to enable rapid adoption for alternative platforms.

For years, the answer was no, but this has changed dramatically with the development of multiple Bolo Clones, culminating in the recent release of WinBolo/LinBolo for the Windows/Intel and Linux/Intel platforms.

The simple answer is "None" which is why CSS offers five generic font names as 'serif', 'sans-serif', 'cursive', 'fantasy' and 'monospace'. Never put any of these generic font names in quotes. A CSS aware browser should make a suitable choice from the available fonts in response to each of those generic names. Specifying any other font name in a www environment comes out as a suggestion only, that may or may not be acknowledged by a browser.

All new scenery editing tools will run on Macintosh and Windows. Betas may come out first for one platform and then the other. Because the tools will be open source, a port to Linux is possible but not planned at this time.

Adobe Reader 7.0 is supported by the later Windows® platforms (Windows 2000 with Service Pack 2, Windows XP Professional or Home Edition, or Windows XP Tablet PC Edition), Mac OS X v.10.2.8 or 10.3, Palm OS® 3.0 (or later) and Pocket PC 2002 or 2003 platforms for handheld devices, Symbian OS™, Linux®, AIX®, HP/UX, and Solaris™.

The following platforms are fully supported and have nightly builds. See the binary downloads page: https://java3d.dev.java.net/binary-builds.html The following platforms can be built from the Ant build.xml file, but are not supplied as pre-built downloads. Java 3D 1.3.1 is bundled with Mac OS X 10.4 (Tiger) and is an optional install available from Apple for 10.3.1 or later. Java 3D 1.4 is not available for Mac OS X. See Apple's download site: http://www.apple.

Current implementations with graphics support are available for Unix (including Linux) and Windows. The Unix implementation also runs on Darwin, the Macintosh development environment, or the Cygwin environment under Windows. Older versions of Icon are available for some other systems. An alternative Java-based implementation for Unix, Jcon, is also available.