Testing Matchbox *initial draft* 
Matthew Allum 2003

Presented here are some methods for testing Matchbox. Used in
combination they should help alot.

o compiling with --enable-debug

  Very useful. Apart from enabling gdb support it also spools lots of
  interesting information to stdout. Beware this is a little messy at
  the moment, Im in the process of making it readable by more people
  than just me...

  The debug option does not alter any of matchboxs logic. Its a
  compile time option as to save a few bytes. 
  
o 'winspew'

  Winspew is contained within this directory. It can be used to create
  dummy windows with varying types and propertys. After creation they
  reprot various pieces of event infomation to stdout.

  Uses;

    - Test Matchbox handling of window types. 
      
      o Do obscure combinations of window types behave as expected ?

    - Can be scripted. 
    
      o Used it combination with some monitoring tool ( see below ),
        can be used to discover leeks with window types etc. 

  Of course it can be used with other EWMH window managers, its not
  matchbox specific.

o mbcontrol

  mbcontrol can be used to control matchbox from the command line or
  script. See mbcontrol --help for more info.
  
o monitoring tools : memprof, efence, valgrind

  XXX todo. 

o X Tools

  'xprop' can be a very useful tool for observing properties set on
  X11 windows. Please refer to the man page on usage. 

o Just using random apps !

  The more obscure the better. Its worth remembering however that
  matchbox is simply not designed to work well ( from a usability
  point of view ) with 'multiple' window apps such as the gimp.

XXX TODO

 o X Errors 
 o X Resource extension 
 o A 'standard' test ?
 o Building with different configure options and running tests.
 o Building on platforms other than Linux, *bsd, solaris etc. 