File: readme.txt

package info (click to toggle)
paraview 5.1.2%2Bdfsg1-2
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 221,108 kB
  • ctags: 236,092
  • sloc: cpp: 2,416,026; ansic: 190,891; python: 99,856; xml: 81,001; tcl: 46,915; yacc: 5,039; java: 4,413; perl: 3,108; sh: 1,974; lex: 1,926; f90: 748; asm: 471; pascal: 228; makefile: 198; objc: 83; fortran: 31
file content (24 lines) | stat: -rw-r--r-- 1,130 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

This example contains:

1.  A server manager xml file (helix.xml) which defines a programmable source 
    that creates a helix.  It also contains extra properties for variables in
    the python script.

2.  A custom gui created in the Qt designer.  When opening the designer, a
    blank widget may be used.  Place all labels and widgets in their places,
    add a spacer at the bottom then lay them out in a grid.  The widgets are
    named after their associated server manager property.  For example,
    NumberOfRounds is a string property with 2 values.  The first value is the
    name of the python variable, and the second is the value of the python 
    variable.  The widget is named NumberOfRounds_1, where _1 tells the GUI to
    tie the value of the widget with the second value of the server manager
    property.

3.  A helix.qrc file specifying the .ui file to include in the resource.
4.  A binary resource helix.bqrc, created from helix.qrc by the Qt's rcc command:
    rcc -binary -o helix.bqrc helix.qrc

  Although the Qt files aren't required, it does give a better user interface
  to the helix source.