[Paraview] KWWidgets and ParaView III

[John Biddiscombe]

Berk et al, (I've cross posted this to paraview/visit and kwwidgets, but 
it'll probably bounce as I'm not subscribed to kwwidgets and I think the 
visit users list was inactive last time I tried...)
> We will reimplement those two widgets in Qt. Actually, let me 
> rephrase: we will implement however much we use in ParaView 2 in 
> ParaView 3. I am guessing that we are only using a subset of the 
> functionality they provide.
I'd just like to note that the GUI widgets for volume rendering in Visit 
are extremely nice. I have successfully <cough> "lifted" the Gaussian 
editor control (part of the opacity transfer function editor) from visit 
to use in my own Qt application - it was a Qt3->Qt4 change plus some 
tweaks to remove dependencies. The entire volume rendering widget would 
be a lot more work, but in my opinion well worth it - because it is very 
good. I am willing to volunteer to port the entire volume property 
control set from visit since I need it anyway.
Note that the visit license was recently changed to remove any 
commercial usage restrictions and I believe is compatible with paraview now.

If it is possible to make the widgets shareable between visit/paraview 
it'd be very useful. However since visit is qt3 and paraview qt4 this 
might mean an excessive amount of #ifdefs etc. I mentioned this to one 
of the visit people a little while ago and they said that sharing had 
been "discussed" at some point, but no action had been taken.

Can anyone provide more information?

JB


>
> -berk
>
> On 10/17/06, *Jean Favre* <jfavre at cscs.ch <mailto:jfavre at cscs.ch>> wrote:
>
>     /Message: 3
>     Date: Mon, 16 Oct 2006 15:13:44 -0400
>     From: Sebastien BARRE <sebastien.barre at gmail.com>
>      <mailto:sebastien.barre at gmail.com>
>
>
>     Well, you nailed it here: KWWidgets is obviously 
>     not as full featured as wxWidgets or Qt, which I 
>     think you can use from Python the way you 
>     described. But it provides nice widgets that can 
>     be interfaced to VTK objects very easily, and 
>     that are likely to take a lot of time to recode. 
>     Now trust me if I'm telling you that recoding 
>     those widgets will take wayyyyyy longer than 
>     using an intermediate class for your callbacks./
>
>
>     The comment above by Sebastien prompts me to ask:
>
>     Is there a plan to migrate the volume-rendering widgets used in ParaView 2.x to ParaView III?
>     If recoding these widgets takes "wayyyyyy too long", are there ready-made Qt widgets with the same functionality:
>
>     I mean vtkKWVolumePropertyWidget, with color transfer and opacity transfer editors?
>
>     Just curious
>         
>
>     -- 
>
>     _______________________________________________
>     ParaView mailing list
>     ParaView at paraview.org <mailto:ParaView at paraview.org>
>     http://www.paraview.org/mailman/listinfo/paraview
>
>
>
>
>
> -- 
> Berk Geveci
> Kitware Inc.
> 28 Corporate Drive
> Clifton Park, NY, 12309
> ------------------------------------------------------------------------
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>   


-- 
John Biddiscombe,                            email:biddisco @ cscs.ch
http://www.cscs.ch/about/BJohn.php
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Cantonale, 6928 Manno, Switzerland      | Fax:  +41 (91) 610.82.82