
                        The MayaVi TODO List
                        --------------------

1.2 release:
^^^^^^^^^^^^

    (*) Try to see if ConfigVtkObj and friends can be abstracted and
    reused more.

    (*) Redesign to separate GUI from main classes.  This will make it
    easy to port it to a different GUI.

    (*) Make most classes pretty much completely scriptable with a
    clean interface.

    (*) Split up the functionality into smaller pieces that can be
    reused more.
    
    (*) Improved file format.

    (*) Add more gui controls for clamped variables in the
    vtkMethodParser.

    (*) Remove debug functions and use trace.py instead.  Change code
    style?

    (*) Create a simple custom module creator and create more filters
    like objects so user can build custom visualizations.

    (*) Debianize MayaVi and get it into the next release?

    (*) Update docs and web pages.


Future releases:
^^^^^^^^^^^^^^^

    (*) Advanced visualization pipeline editor for custom modules and
    filters.

    (*) Use weakrefs for the pipeline code and try to deal with memory
    leaks.

    (*) Add help menu and use webbrowser to show docs.  Also add an
    'about' dialog message.


Todo or not todo?
^^^^^^^^^^^^^^^^^

    (*) Add support for other types of data: OBJReader etc. will need
    to modify some modules so that it works with any source and not
    just VTK data files or PLOT3D stuff.  Things like grid_type
    etc. have to be looked into.  Look at OBJ, BYU, PLY, SLC, STL,
    UGFacet.

    (*) More export options? vtkPolyDataWriter, CGM, OBJExporter.

    (*) Generalize the streamlines a bit and allow for using
    PlaneSource, LineSource, SphereSource and DiskSource?

    (*) Keyboard motion for camera?

    (*) Find values along a line (arbitrary probe?) or picking?

    (*) Arguments can be passed on the command line for different
    modules?  Might need to use Optik for this.

