Difference between revisions of "User:Barre/2008 Summer Project Week"
From Slicer Wiki
Line 12: | Line 12: | ||
** Alex: check the Models tree widget issue, i.e. that it is lacking the usability found in Slicer2 (see [[User:Barre/TODO|TODO]]) | ** Alex: check the Models tree widget issue, i.e. that it is lacking the usability found in Slicer2 (see [[User:Barre/TODO|TODO]]) | ||
** Add option vtkKWTreeWithScrollbars to resize the tree manually (see [[User:Barre/TODO|TODO]]) | ** Add option vtkKWTreeWithScrollbars to resize the tree manually (see [[User:Barre/TODO|TODO]]) | ||
+ | * Thursday | ||
+ | ** Steve, Ron, Will: strategy for the infrastructure required to create Slicer3 binaries and separate modules that can be reviewed, downloaded, integrated in Slicer3. Not to be completed by RSNA. Experimentation for the moment. I (Seb) will produce some installers for Slicer3-Core + Modules, installers/ZIP for the CLP (which need to be fixed so that they can be built/installed separately against Slicer3), installers/ZIP for Slicer3-modules (using the macros that will pull them out of their repository and build them automatically), and a GUI in Slicer3 to fetch the ZIP and unpack them. |
Revision as of 15:42, 26 June 2008
- Various user-friendly optimization (see TODO)
- Steve Aylward: SlicerIGT funding?
- Tuesday
- Ipek Oguz: Help with Offscreen Rendering and making sure it can behave as a command-line program (without a KWW GUI)
- Ragani: Try to convert legacy code, vtkImageResliceST.cxx, based on old vtkImageReslice
- Craig Sharp: Help with Plastimatch; including the CMake code for a CLP was conflicting with his own CMake code. At the end of the day, his library needed to be linked against ITK, as opposed to just his executables; why the CLP CMake code revealed that "problem" is not clear, but in any case that's the way to go in general...
- Luis: discuss the IO formats introspection (see TODO)
- Cleanup some installation/configuration rules in QdecModule and TumorGrowth
- Wednesday
- Thursday
- Steve, Ron, Will: strategy for the infrastructure required to create Slicer3 binaries and separate modules that can be reviewed, downloaded, integrated in Slicer3. Not to be completed by RSNA. Experimentation for the moment. I (Seb) will produce some installers for Slicer3-Core + Modules, installers/ZIP for the CLP (which need to be fixed so that they can be built/installed separately against Slicer3), installers/ZIP for Slicer3-modules (using the macros that will pull them out of their repository and build them automatically), and a GUI in Slicer3 to fetch the ZIP and unpack them.