In no particular order:

	o make use of the Layout widget for geometry management of the main GUI
	o more intelligent use of the command line ... command completion
	  and argument specification ... type node hit space,
  	  get a "list of options" type delete hit space, get a prompt
	  for a number, type number hit return, etc.  In other
	  words make it something along the lines of some of the
	  popular CAD systems.
	o add some sort of drawing loads, forces, constraints, etc.
	  Either bitmaps or colors or force arrows or something.
	  Anyone have a nice generic way to do this?
 	o improve plotting of displaced shapes. This probably means that
	  element writers need to provide a pointer to a function which
	  knows about the shape functions for an element and can fill in
	  a vector over the area or length of the element based on 
	  nodal displacements which when plotted, will reflect the true
	  displaced shape of the element ...  time-history plot once 
	  dynamics is in
	o add snap to tool capability
	o dynamics
	o quadrilateral mesh generation, 3-d mesh generation, etc, etc.
	o kinematic boundary conditions, element constraints (constraining 
	  the entire edge of an element).  We should probably do something
	  about the way hinges are treated on beam elements.  It's kind of
	  limiting right now.
	o get rid of the .vlv files and add a section to the standard
	  FElt syntax (velvet) which contains clear text descriptions of
	  everything that is in the .vlv file
	o additional higher-order elements
	o fold Timoshenko beam theory into the standard beam, i.e., if
	  kappa or nu is given then expect a G and use Timoshenko
	  theory instead of Euler-Bernoulli.
	o a converter to go from the geometric model created in AutoCAD or
	  some such and stored as a DXF to at least the nodes and elements
	  section of a FElt file.  The user could fill in the object 
	  information by hand after all.
	o switch from the current, fairly limited, XWD capabilities in
	  velvet to dumping postscript, at least for the drawing area
	  dumps and line plots (this will be real important for the time-
	  history plots).
	o put some real effort into internationalization.  The current 
	  functionality is there because it was easy.  More robust
	  implementation would mean maintaining a table, in code probably,
	  that mapped all possible input and as much output as possible
	  to a language determined by the user.
