ParaQ Applications

Overview

Following are a collection of screenshots, issues, and ideas raised in conjunction with a set of prototype "applications" built on the ParaQ framework. The goal is to explore what it means to build an application using ParaQ - does an application merely link with the ParaQ libraries, or is there some deeper level of integration? Is an application a separate executable, a dynamically-loaded plugin that reconfigures the user interface, or something else?

Prototypes

GeoViz Component

"GeoViz", a set of VTK-derived classes created at Sandia, linked into a "vanilla" pqClient as a "component". There is a low level of integration in this example, since the GeoViz componenet encapsulates a separate, client-side-only pipeline that is independent of the ParaView Server layer. The next step is to get the GeoViz classes accepted into VTK so that the GeoViz view can be implemented in PVS, possibly as a compound filter. This suggests that the GeoViz "component" may ultimately be just a user-interface component (i.e. a custom property sheet) that is designed to be connected to a specific subgraph (the GeoViz network) in the PVS pipeline. There might (or might not) be some C++ class that fronts for the collection of PVS proxies that make up the GeoViz subgraph.