<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<!-- BEGINNING of header -->
<!-- $Id: help.html,v 1.1 1999/03/10 00:58:59 jon Exp $ -->
<html>
  <head>
    <title>Help wanted!</title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    <table border=0 width="100%">
      <tr><td><img src="imgs/lesstif.jpg" align=left></td></tr>
    </table><br>
<!-- END of header -->

<!-- BEGINNING of opening -->
    <table border=0 width="100%">
      <tr>
        <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
        <td>
<center><b>Have you ever wanted to help out LessTif?  Here's your chance.</b></center>
        </td>
      </tr>
    </table><br>
<!-- END of opening -->


<!-- BEGINNING of content -->

<p>We're occasionally asked on the mailing list "Can I help?"

<p>In a word, YES!

<p>Perhaps we (the core team) isn't being specific enough about what
people can do to help.  The overall project can seem a bit overwhelming
and perhaps some people don't know where to start.  Here's a list of ways
that the interested developer with moderate knowlege of Motif programming
can help out.

<ol>
<li> The test programs.  These are a suite of programs which, in many
cases, exhibit horrible programming style, are an awful example of Motif
programming, but have the redeeming fact that at one time or another
showed something which we were doing different from motif.  Most of these
tests have auto-checks on the geometry and layout so that we can see if
we're at least getting that right.

How to use the tests.  The best thing is to use the testall script:
<pre>
  cd /usr/src/lesstif/test/Xm  (or wherever you've got the lesstif source)
  ./testall -a                 (once I manage to commit the version with
                                the -a option)
</pre>

This will run all the tests and report on which ones have failed.  Then
you can look closer at the failed tests and attempt to fix lesstif so that
the test passes.  The DEBUGSOURCES environment variable may help in this
regard.

<li> We also need people to make detailed comparisons of LessTif to
OSF/Motif.  See <a href="testers.html">testers.html</a>.  Basically, this
involves building both Motif and LessTif versions of our tests and
documenting any differences between their behavior.

<li> Read <a href="http://bugs.hungry.com">bugs.hungry.com</a>.  Pick any of
the outstanding bugs and try to track it down.  Announce on the mailing
list that you're working on a particular bug so that we don't duplicate
effort.  Also post an update to the bug on the web page.
<br>
One of the most helpful things you can do short of actually fixing the bug
is creating a simple test case for it.  Many of the bugs are of the form:
"in my huge app, when I press button foo, bar happens".  It's much easier
to find the bug when you've stripped the problem down to the bare minimum.
Take everything out that you can, and create the smallest possible test
case which shows the problem, and then send in the test app.  If you fix
the bug, the test app will still be useful, and if you don't fix the bug,
the test app will make it easier for someone else to find.

<li> Tell all your friends about lesstif, and try to get them to use it.
With many eyes, all bugs are shallow, right?

<li> Finally, we could always use help with the documentation!
</ol>

<br> 
Thanks!<br>
The LessTif Core Team<br>

<!-- END of content -->

<!-- BEGINNING of footer -->
    <br>
    <center>
      <font size="-1">
Send any questions or comments to the
<a href="mailto:lesstif@hungry.com">mailing list</a>.
      </font>
    </center>
  </body>
</html>
<!-- END of footer -->
