[IGSTK-Developers] some short suggestions

[David Gobbi]

Hee-su Kim wrote:

>Hi, guys:
>
>I have some suggestions for IGSTK.
>
>*creating FLTK UIs for controlling transfer function and level window
>
>Because most of image-guided surgery application may need UIs for transfer function and level window, a lot of redundant efforts of application developers could be reduced if IGSTK provides UIs. Level window UI may be integrated into View class or not.
>
>IGSTK is dependent on FLTK so it's a very good place to put common UI classes.
>  
>
We want to restrict IGSTK's dependence on FLTK as much as possible.
Ideally, we should write IGSTK so that people can choose to use a
different interface (Qt, MFC, etc). I know that some IGSTK classes
require FLTK, but I don't think this is a good thing.

I think that it is good to have reusable FLTK controls for color
transfer functions, window/level, etc., but I don't think those controls
should go into the View class.

It is best if the View class allows the user to control zoom, pan, etc.
by dragging the mouse in the View window, so at least for those
operations, no FLTK controls are required.

>Maybe, you guys already planned to create those.. I don't know.
>
>*3D annotation should be in front of the object
> : applying 3D transform (object and camera) -> use vtk 2D text objects to show annotation. (scaling may be done depending on Z-coordinate)
>
>I think 3D annotations might become behind objects.
>
>It might be irritating to rotate and pan cameras to find necessary 3D annotations.
>
>So, I suggest to use 2D text objects after transforming.
>  
>
Yes, that is a very good idea. I have used embedded 3D text annotations
before, and the users always find them annoying.

>If vtk's annotation 3D widgets support or behave like that, we don't need to worry.
>  
>
Right now Kitware is redesigning the VTK widgets:
http://www.vtk.org/Wiki/VTKWidgets

- David