[Paraview-developers] ParaView Usability Improvements

[David E DeMarle]

One thing that new users don't like is that it is hard to find out
what filters do really and more frustratingly, why they are greyed out
once you know what one you want.

We should do a better job of documenting the input and output types of
each reader/source/filter/writer, what specifically it does, and what
the input restrictions (domains) are. Perhaps we can automate the
collection of that from the class hierarchy, doxygen, and the xml and
expose it in some intuitive manner in the UI. For example using icons
to represent input data set types and presence of cell/point scalars
etc.

I will try to put up some mockup on the wiki page shortly.

David E DeMarle
Kitware, Inc.
R&D Engineer
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x109



On Sat, Feb 27, 2010 at 11:45 AM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
> There is lots of good stuff here.  I added a bunch of megalomaniacal
> comments.
>
> -Ken
>
>
> On 2/26/10 10:27 AM, "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com> wrote:
>
> Folks,
>
> Following a discussion with Berk, I've started consolidating the ideas
> for the improvements on a Wiki page.
> Please start contributing your suggestions.
>
> http://www.paraview.org/ParaView3/index.php/ParaView_Usability_Improvements
>
> Utkarsh
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
>
>
>    ****      Kenneth Moreland
>     ***      Sandia National Laboratories
> ***********
> *** *** ***  email: kmorel at sandia.gov
> **  ***  **  phone: (505) 844-8919
>     ***      web:   http://www.cs.unm.edu/~kmorel
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>