          Some ideas about how vpApp could be improved:
          =============================================

o Faster redrawing

  Possible ways to speedup the redrawing:

  - Use off-screen Pixmaps in the Composite class. This would enable faster
    refresh when EXPOSE event take place.

  - Using a display-list class in the Composite class where the speed-critical
    parts are coded in C. This would also require changes in the Primitive
    classes, i.e. they would somehow have to hand over the redrawing to the
    display-list. 


o Use the public domain Layout widget <keithp@ncd.com> in the Box class 

  The Layout widget has more or less the same functionality as the Box
  class. Being implemented in C it should be quite a bit faster.

  ftp location: export.lcs.mit.edu
  file name:    (dir?)/Layout.tar.Z


o Use the public domain XmGraph widget to create tree layouts
  (TreeEditorView and TreeNodeView classes).


o Implement the Model-View notification system with a general object
  dependency mechanism ala Smalltalk. This concerns the following methods:
 
  - Object.AddCallback( .. )
  - Object.RemoveCallback( .. )
  - Object.ExecuteCallback( .. )
  - Model.NotifyChange( .. )
  - View.InstallChangeHandler( .. )
  - View._ModelChanged( .. )
  - View.ModelChanged( .. )
  - View.StoreChange( .. )
  - View.ProcessOldChanges( .. )


o Built-in support for run-time object inspection 

o Adding a HTML class using Marc Andriessen's HTML widget

o Making a generic help systems using the HTML class

o Persistence. This has been partly done in the ObjectIO module.

o Interface builder

  
