Issues with Connection and Recent Files

Connect and Disconnect

We want to support a simpler, quicker connect/disconnect design, in conjunction with a recent files list that encodes server information. Working with recent files, servers, and connect/disconnect should be as simple as browsing for files on a local machine. The only difference should be that the user will need to be prompted for passwords in some cases, but this will depend entirely upon the setup of the customer's network.

Requirements

1. ParaView shall be configurable so that a list of possible server connections is available at startup. This configuration is to be obtained through one of the following methods:
   1. URI
   2. Default configuration file, located in a known place in the installation.
   3. User-specified configuration file, located in a place designated by an environment variable.

Use Cases

• Start client on a machine which cannot save client data.
• Start client on a machine which cannot save client data, start making movie, then disconnect once ParaView has started to create the movie. The movie should continue to be made on the server. Server exits after movie is created.

Assumptions

• State is saved as follows:
  • ParaView Server state is saved on the server
  • User's settings for the server are saved on the server. These settings apply for this user on this server only.
  • Client-side settings that are not needed on the server are saved on the client. These include:
    • Recent files list.
    • Window sizes, etc.

Recent Files List

The recent files list is a hierarchical list of recent files kept on the client (only) by the client. The recent files are grouped by server name in the UI (the recent files menu).

Figure 1: Recent files menu, showing hierarchical ordering of recent files by 1) Server 2) type (pvs, then data types). Note that 1) the icons show pvs and 'other' (data) files, and 2) the 'Local' heading is bold, indicating that this is the server to which the user is currently connected.

Actions

• Selecting a recent file:
  • Asks the user if he wants to close the current file.
  • Closes the current file.
  • Connects to the requested server, if that server is not the one that is currently connected.
  • Locates the requested file.
    • If it exists, opens it.
    • If it does not exist, reports that to the user. The connection is kept alive, in case the user wants to try to open a different file.

Connect/Disconnect Actions

A user can disconnect from a server at any time, using 'Connect/Disconnect' menu items or buttons. Disconnecting from a server requires that the current session be terminated. The user is offered the option of saving the session before it is terminated.