MagiCapture Things To Do List
=============================

ALPHA TEST RELEASES:

 1. Allow the user to continue saving the screen capture even if the
    program was unable to render the captured image into a window.

 2. Clean up variable names in capture.c, options.c, and save.c.

 3. Move all widget management functions to widget.c, and ensure that all
    routines are creating widgets using widget.c calls rather than direct
    GTK+ calls.

 4. Ensure that all options management functions are contained in
    options.c. At this point, changing the OptionData structure requires
    changes in too many parts of the code, including panel.c.

 5. Define a set of default keyboard bindings for all the windows, buttons,
    entry fields, and dialog boxes.

 6. Determine a way to enforce linking against ImageMagick Version 4.2.8,
    rather than just checking for APIs that might be present in any version
    of ImageMagick. This can be done by adding a test in configure.in to
    take a look at the MagickLibVersion macro in <magick/version.h>, and
    make sure that the macro's value is equal to or greater than 0x0428.

 7. When the user saves the screen capture into an existing file, prompt
    the user if it's okay to overwrite the file.

 8. Move all strings to stringtable.h so that they may be
    internationalized during the BETA development cycle.

BETA TEST RELEASES:

 1. Start the BETA releases with version 0.9.

 2. Improve the current documentation and add some examples. All
    documentation shall be completed before the first public release.
    In addition, provide a MagiCapture User's Manual in the doc/
    subdirectory.

 3. Change the "About" button to a "Help" button and provide
    documentation within a help window. Use a GTK notebook with organized
    tabs (e.g. "Using MagiCapture", "Examples", "About") if necessary.

 4. Internationalize all strings and provide a message catalog for
    U.S. English.

 5. Possibly change the copyright to a less restrictive license than the
    GPL.

PUBLIC RELEASES:

 1. Start with MagiCapture 1.0.0, and increment the last digit (1.0.1, 1.0.2,
    etc.) as problems are found and fixed.

 2. Increment the last digit as new native-language translations are
    submitted.

FUTURE RELEASES:

 1. New features will be added to the next cycle of development releases.
    Start the development cycle with 1.1.0.

 2. During the ALPHA development phase, create a Win32 version of
    MagiCapture. 

 3. Start the BETA development cycle with version 1.9.0.

 4. Release the next public version as 2.0.0.
