ParaQ:Design: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
No edit summary
Line 76: Line 76:
* [[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.

Revision as of 15:53, 17 July 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.


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.