ParaQ:Design: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
 
(14 intermediate revisions by 5 users not shown)
Line 8: Line 8:
==Applications==
==Applications==
* [[ParaQ Applications]] - prototypes of specialized applications built on the ParaQ framework.
* [[ParaQ Applications]] - prototypes of specialized applications built on the ParaQ framework.
==PGraph==
* [[Plotting Parallel Data (PGraph)]] - Initial design for the parallel plotting framework.
* [[PGraph Implementation]] - Notes on the (current) state of the PGraph implementation.
* [[PGraph User Interface]] - Initial discussion on how users could create and interact with PGraph.
==Time Support==
* [[Time Support]]


==Compound Filters==
==Compound Filters==
* [[ParaQ:Compound_Filter_Design]]
* [[ParaQ:Compound_Filter_Design]]
* [[Compound proxies in SM]]
* [[Compound Proxies - Copies or References]]


==Pipeline==
==Pipeline==
Line 23: Line 33:
* [[MultipleServerConnections]] - discusses modifications to the PSM API to support connections among multiple clients and servers.
* [[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.
* [[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.
* [[Server Connections]] - discusses requirements and design for making server connections.
* [[Where's The State?]] - covers some recently-identified issues with where we store state - client or server?
* [[Mulit-Client-Multi-Server Issues]] - discusses issues with multi-client-multi-server configurations.


==GUI==
==GUI==
* [[Modal Dialogs]] - how to (and how not to) implement modal dialogs in the Qt client.
* [[Modal Dialogs]] - how to (and how not to) implement modal dialogs in the Qt client.
* [[PipelineBrowser]]
* [[PipelineBrowser]]
* [[Remote File Browser API]] - proposed changes & additions to the current PSM API for remote file browsing.
* [[File Browser]] - the ultimate local/remote file browser!
* [[ThreadedGUI]]
* [[ThreadedGUI]]
* [[SynchronizingWidgets]] - How to keep GUI widgets synchronized with each other.
* [[SynchronizingWidgets]] - How to keep GUI widgets synchronized with each other.
Line 34: Line 46:
* [[ParaQ:API | GUI/ServerManager API]] - Architecture for how the GUI code interacts with the Server Manager.
* [[ParaQ:API | GUI/ServerManager API]] - Architecture for how the GUI code interacts with the Server Manager.
* [[ParaQ:Compound Filter Design | Compound Filter Design]] - Design of Compound Filters
* [[ParaQ:Compound Filter Design | Compound Filter Design]] - Design of Compound Filters
* [[Exodus Reader Object Inspector]]
* [[Overall UI Design]]


==Scripting==
==Scripting==
Line 43: Line 57:
==Selection==
==Selection==
* [[Selection]] - possible approaches to handling interactive selection of geometry.
* [[Selection]] - possible approaches to handling interactive selection of geometry.
 
* [[Selection Use Cases]] - Defining some use cases to help drive requirements for the selection implementation.
==Standards==
* [[CodingStandards]]


==Testing==
==Testing==
Line 63: Line 75:
* [[Undo Design]] - describes a framework for storing client-side and server-side state-changes that can be undone / redone.
* [[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.
* [[Screen Update / Undo Interaction]] - discusses use-cases where screen updates and undo / redo operations intersect.
==High level design==
* [[High Level Design]] - A high level design for how the core ParaQ functionality interacts with componentes of ParaQ.  And how multiple applications can work with ParaQ.

Latest revision as of 10:54, 28 September 2006

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

Applications

PGraph

Time Support

Compound Filters

Pipeline

Client / Server

GUI

Scripting

Selection

  • Selection - possible approaches to handling interactive selection of geometry.
  • Selection Use Cases - Defining some use cases to help drive requirements for the selection implementation.

Testing

UI Design

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.


High level design

  • High Level Design - A high level design for how the core ParaQ functionality interacts with componentes of ParaQ. And how multiple applications can work with ParaQ.