ParaQ:Design

Overview

This page serves as the formal gathering place for discussions, documentation, and doodling related to ParaQ design. It's the final resting place for documents that may appear other places in the site (for example, on the page for a meeting, if the document was presented at that meeting).

Initial Design

• Design document, presented and discussed at the first ParQ summit.
• Crash Test Dummies - the modern-day equivalent of straw men.

Applications

• ParaQ Applications - prototypes of specialized applications built on the ParaQ framework.

Compound Filters

• ParaQ:Compound_Filter_Design
• Compound proxies in SM

Pipeline

• Pipeline IDs

Client / Server

• AsynchronousUpdates
• ClientSideData
• Loading state from XML
• ParaQ:Multiview
• ParaQ:Client-Server_Connections - an overview of client / server connections.
• MultipleServerConnections - discusses modifications to the PSM API to support connections among multiple clients and servers.
• Secure Connections - discusses using SSL to secure forward and reverse connections, plus reconnects, etc.
• Server Connections - discusses how clients interface with the PSM to allow for server disconnects/reconnects.

GUI

• Modal Dialogs - how to (and how not to) implement modal dialogs in the Qt client.
• PipelineBrowser
• Remote File Browser API - proposed changes & additions to the current PSM API for remote file browsing.
• ThreadedGUI
• SynchronizingWidgets - How to keep GUI widgets synchronized with each other.
• ThreadedGUI - Discussion of issues related to threading a GUI with the Server Manager.
• GUI/ServerManager API - Architecture for how the GUI code interacts with the Server Manager.
• Compound Filter Design - Design of Compound Filters

Scripting

• Scripting
• Notes on ParaQ and PSM Scripting
• Scripting:Requirements
• Embedded Python

Selection

• Selection - possible approaches to handling interactive selection of geometry.

Testing

• Early Testing Prototype - brief overview of the prototype testing implemented in the original "Hello, World" client.
• Testing Design - discusses the later, agreed-upon design for testing in the ParaQ client.
• ParaView 2.4.x User Testing - User testing on the existing ParaView user interface, to find out requirements and other improvments that we can make in ParaQ.
• ParaQ User Testing - User testing on ParaQ.

UI Design

• UI Design Guidelines document
• UI Design Literature Study
• High Level Usability Goals
• Popup/Panel/Modal and Non-modal Dialog Discussion

Undo

• Screen Updates - a framework for handling screen updates that allows for a wide variety of update policies.
• Undo Design - describes a framework for storing client-side and server-side state-changes that can be undone / redone.
• Screen Update / Undo Interaction - discusses use-cases where screen updates and undo / redo operations intersect.