View source for Engineering:Project:2006 AHM Programming:MeshVisu:KWWidgets

'''Results'''

* We are mostly done with this, except a couple of minor things to add.
* It was a nice experience, because I got to check out KWWidgets, and I have a very positive first impression.
* As compared to FLTK (that I was using before), KWWidgets is rather easier to use, and has more built-in components (like the color transfer function editor) that are very useful in applications.
* In the beginning, we had quite some trouble to get things to compile and link together with ITK and VTK, but I think it was a nice experience, because everything that can ever go wrong went wrong, and I learned how to solve them if they happen again. We also caught a couple of bugs, which Sebastien fixed. After the programmer's week I tried installing KWWidgets on a different computer and everything went very smoothly. So I suppose this experience helped to enhance the compatibility of KWWidgets with the other libraries we use.
* Sebastien was really helpful (thanks!). I am really glad that we had a chance to work together during programming week, I thought it was very productive.

<br />'''[Mostly Random] Thoughts & Notes'''

* Here are a few snapshots from current interface:

   [[Image:Engineering%5CProject-2006_AHM_Programming%5CMeshVisu%5CKWWidgets%5Cmain.png|[[Image:Engineering%5CProject-2006_AHM_Programming%5CMeshVisu%5CKWWidgets%5Cmain.png| Main Window]]]]
   [[Image:Engineering%5CProject-2006_AHM_Programming%5CMeshVisu%5CKWWidgets%5Cpvalue.png|[[Image:Engineering%5CProject-2006_AHM_Programming%5CMeshVisu%5CKWWidgets%5Cpvalue.png| P-Value Map Settings]]]]
   [[Image:Engineering%5CProject-2006_AHM_Programming%5CMeshVisu%5CKWWidgets%5Cdistance.png|[[Image:Engineering%5CProject-2006_AHM_Programming%5CMeshVisu%5CKWWidgets%5Cdistance.png| Distance Map Settings]]]]

* As can be seen from the snapshots, in this application there is one main widget for rendering one 3D spatial object. The rest is essentially only standard GUI elements (buttons, etc).
* I'm not particularly happy with the way the color scheme setup (for p value and distance maps) is right now - we might want to implement a better way of visualizing the current set of parameters as the user is interacting with the system. ''Maybe a small bar that will show the range?''
* The current implementation is really 'dirty' - which means an accumulated pile of little quick hacks. I'd like to take this oppurtunity to make things neat and easy to maintain and/or extend.
* MeshVisu is intended to be a standalone tool, rather than a Slicer module. For the moment, at least.
* MeshVisu is making use of ITK, VTK and SOViewer libraries.