Kepler

When a user has a remote repository configured for actor searching, they are prompted to login to search for a component. Clicking Login Anonymously causes Kepler's user interface to stop responding to user input. Some users at a demo interpreted this as Kepler freezing, and so killed the Kepler process. I tried this, and the login eventually completes and Kepler becomes responsive again. But there is no indication in the UI that we are waiting for the login to complete, and so this is easily confused with a crash of the program. Two potential solutions:

1) Make login much faster, on the order of subsecond
2) Provide a UI indicator that we are waiting for login to complete, such as a progress meter