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.

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 .

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)

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.

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.

Do I have to answer that? Let's just say that I don't know very many people who enjoy being on a leash (my husband and I don’t lean that way), and I am no different. I have to psych myself up to run a full 12 hours of TPN, but I make sure I do that at least once a week. Since I work 10-hour days, I usually get about ten hours in on work nights, and do the full runs on my days off (when I can sit in my recliner and thus avoid those fabulous [IV] line dances).

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.

Because BitWise is only used for transmission of data (not storage of data), our access controls and logs of who is granted what rights (i.e. who has access to use BitWise and thus receive the data) is sufficient for HIPAA in most environments. That is to say, the information being transmitted over BitWise must come from somewhere--which would be your HIPAA-compliant environment; BitWise is only used for transmission, and our transmission encryption and access controls meet HIPAA guidelines.

Longer answer: Tcl 7.5 and 7.6p0/1 had bugs that caused them to be noncompliant with regard to how POSIX defines 2-character years. If your scripts use 2-character years, you should upgrade to a modern version of Tcl. If your scripts use 4-character years, than you have nothing to worry about.

Apache internally never stores years as two digits. On the HTTP protocol level RFC1123-style addresses are generated which is the only format a HTTP/1.1-compliant server should generate. To be compatible with older applications Apache recognizes ANSI C's asctime() and RFC850-/RFC1036-style date formats, too. The asctime() format uses four-digit years, but the RFC850 and RFC1036 date formats only define a two-digit year.

Whew! After a long delay, I am returning to the FAQ. A lot of information has been out-of-date for some time, so I felt I had to at least get us back in place. I have noticed a growing number of sites out there that have copied all or part of my FAQ. While I should be angered at what is clearly a violation of copyright, I'll choose to be understanding and a little flattered. Honestly, people, you could at least mention that it's my work, you know.

Yes! GAGEtrak is compliant with the millennium change. Just set the year value to be 4-digits in your Windows control panel and the program will honor the setting. Actually, all date formats are supported (i.e., "2004/11/02", "11/02/2004", etc.) and can even be run in a mixed mode on a network (i.e., if some users prefer dates to be displayed one way and other users prefer their dates in another way).