Writing Custom Applications: Difference between revisions
(New page: =Motivation= This document describes how to create Qt-based custom visualization applications using ParaView's Parallel Visualization framework. Applications based on ParaView have grown...) |
mNo edit summary |
||
| Line 10: | Line 10: | ||
All such custom applications created using this framework will be referred to as ParaView-brands in this document. | All such custom applications created using this framework will be referred to as ParaView-brands in this document. | ||
=Do I need a | =Do I need a Custom App, or merely a Plugin?= | ||
When adding functionality to ParaView eg. filters, panels, menus, views etc. without changing the application level behavior of ParaView, plugins are the easiest. Note that plugins are only "additive" i.e. you can add functionality to ParaView using plugins, never remove or qualify existing behavior i.e you cannot change what happens when user clicks "File-Open" in ParaView using plugins, however, you can add support for a new reader that becomes available for the user in the File-Open dialog. | When adding functionality to ParaView eg. filters, panels, menus, views etc. without changing the application level behavior of ParaView, plugins are the easiest. Note that plugins are only "additive" i.e. you can add functionality to ParaView using plugins, never remove or qualify existing behavior i.e you cannot change what happens when user clicks "File-Open" in ParaView using plugins, however, you can add support for a new reader that becomes available for the user in the File-Open dialog. | ||
If what you need is change the way ParaView as an application works, i.e. totally customize the menus, get rid of the pipeline browser, change the pipeline centric user interface etc., then you should look into creating a custom application. Of course, custom applications can use plugins to add new features required by them. | If what you need is change the way ParaView as an application works, i.e. totally customize the menus, get rid of the pipeline browser, change the pipeline centric user interface etc., then you should look into creating a custom application. Of course, custom applications can use plugins to add new features required by them. | ||
Revision as of 18:10, 20 November 2009
Motivation
This document describes how to create Qt-based custom visualization applications using ParaView's Parallel Visualization framework.
Applications based on ParaView have grown since the release of ParaView 3.0. In spite of best of our intentions we soon realized that it was not very easy to create applications that use ParaView core without subscribing to an user interface identical to ParaView's. The infamous pqMainWindowCore ended up being copy-pasted for every application and then tweaked and modified breaking every possible rule for good programming practices. Also it was hard to create domain specific ParaView-clones with limited user interface components, since various components have cross dependencies among each other and it becomes hard to ensure that all signals/slots are connected correctly for them to work.
To address these issues, we re-structured the application layer in Paraview. The main goals we set out to address are:
- Facilitate creation of applications radically different from ParaView, with totally different workflows.
- Facilitate creation of ParaView-variants that use most of ParaView functionality with minor behavioral or user-interface changes.
All such custom applications created using this framework will be referred to as ParaView-brands in this document.
Do I need a Custom App, or merely a Plugin?
When adding functionality to ParaView eg. filters, panels, menus, views etc. without changing the application level behavior of ParaView, plugins are the easiest. Note that plugins are only "additive" i.e. you can add functionality to ParaView using plugins, never remove or qualify existing behavior i.e you cannot change what happens when user clicks "File-Open" in ParaView using plugins, however, you can add support for a new reader that becomes available for the user in the File-Open dialog.
If what you need is change the way ParaView as an application works, i.e. totally customize the menus, get rid of the pipeline browser, change the pipeline centric user interface etc., then you should look into creating a custom application. Of course, custom applications can use plugins to add new features required by them.
