2. Internal Launch

A Swing program can be launched in a seperate windows (or Linux) file explorer on
a file of type .abc. The application has a menubar, toolbar, and a text area for 
editing text. It can open a .abc file, edit, and save. There's also a plugin.xml file 
that registers this editor as an external editor on .abc files 
After the Swing application saves the file, it calls the plug-in to update the Eclipse
workspace.
  File
    New... Displays a dialog (wizard style) asking for some information to put in an initialized .abc file
    Open... Uses a file chooser to open an existing file
    Save Save the currently open file
    Exit

Toolbar
   New
   Open
   Save
   Add... Displays a dialog that allows a couple of choices for text to append to the end of the current .abc file

What you get:
- ability to launch Swing application with other applications
- single point of control for all project resources
- can use Eclipse to manage team development and versioning

- DOES NOT require refresh from local to update Eclipse meta-data after save.
- exploits data integration with other tools

Problems:
- The page layouts in the new wizard are pretty simple and ugly. 
- For some reason, some of the text in page 2 shows up over page 1 when the new wizard is first displayed. Subsequent displays have no problem, and it clears up after pressing next followed by previous. Might be a Swing bug.
