ParaQ:Design: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
No edit summary
 
(One intermediate revision by one other user not shown)
Line 40: Line 40:
* [[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 57: 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.
 


==Testing==
==Testing==

Latest revision as of 11: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.