130 likes | 343 Views
ParaView. Future, vision, …. ParaView Architecture. Thin Client. Thin GUI code Most of work done by other components: Client Support Code (“ClientManager”) Server Manager Server. Model-View-Controler. Clear Server Manager driven design Load GUI from Server Manager
E N D
ParaView Future, vision, …
Thin Client • Thin GUI code • Most of work done by other components: • Client Support Code (“ClientManager”) • Server Manager • Server
Model-View-Controler • Clear Server Manager driven design • Load GUI from Server Manager • Load / Save XML (Server Manager) • State, Batch – same? • Things driven by properties and domains
Model-View-Controler • Disconnect / reconnect GUI from SM? • Collaborative interface?
XML GUI Description • Simple XML • No redundancy with Server Manager • Support for algorithm/reader pages • Support for arbitrary views
XML GUI Description • All of it described in XML? • Have programmable widgets for whole GUI? • Have properties for data page? • Have properties for camera settings? • Have properties for lookmarks?
Client Support Code • Code that can be reused between clients • VTK based • VTK, STL, kwSys • No Qt, Tcl, Tk, Python, … • Wrapped to Tcl, Python
ServerManager • Stable ServerManager API • Everybody talks proxy/property/domains • Simple initialization • Simple interaction • No more drastic changes • Add readers/writers/algorithms
Data Analysis • Combine pick/probe/xyplot/… • Require Server Manager framework • Combine • 3D widgets • Analysis filters • 2D and 3D graphs • Send data from server to client
Saving / Loading State • XML • We can already save it • In PVEE we are already loading it • Want to store global information • Server Manager • GUI + layout