Removed the captureThread methods

The functionality was implemented in EventProcessor and then exposed
through the Application class via the WebApplication class.
Removed Dialog's waitForWindow property

When this property was set, the Dialog would capture the EventProcessor
thread when it was visible, thus blocking the execution of the app until
the Dialog was dismissed.
Removed the static Dialog methods of FileChooser

I think this was one of those features that was driven by a CCS specific
need. If someone wants to put a FileChooser in a Dialog there is nothing
stoppint them, so I don't feel bad about removing this.

Mainly, this depended on blocking Dialogs, and rather than re-write it,
it seemed like a good time to just get rid of the feature.
MessageBox.confirm no longer blocks

This was a tricky one. The solution for now is to have the confirm
methods take an ActionListener as a parameter. When the MessageBox is
closed, the ActionListener executes the actionPerformed() method. The
ActionEvent's source property is set to the id of the Button that was
clicked (this used to be the return value of confirm())

I'm not sold on this approach. Part of me wanted to just get rid of it,
but too much testing code is dependent on blocking MessageBoxes right
now. MessageBoxes with callbacks takes care of my test cases, so that's
what I'm going with for the moment.
Merge pull request #3 from tedchoward/remove_thread_capture

Remove thread capture