User:Barre/2008 Summer Project Week - Revision history

Barre at 14:58, 27 June 2008

2008-06-27T14:58:58Z

Barre at 13:47, 27 June 2008

2008-06-27T13:47:38Z

Barre at 17:56, 26 June 2008

2008-06-26T17:56:44Z

Barre at 15:42, 26 June 2008

2008-06-26T15:42:17Z

Barre at 21:26, 25 June 2008

2008-06-25T21:26:09Z

Barre at 21:04, 25 June 2008

2008-06-25T21:04:11Z

Barre at 16:35, 25 June 2008

2008-06-25T16:35:00Z

Barre at 03:31, 25 June 2008

2008-06-25T03:31:35Z

Barre at 21:42, 24 June 2008

2008-06-24T21:42:17Z

Barre at 20:27, 24 June 2008

2008-06-24T20:27:31Z

@@ Line 1: / Line 1: @@
 * Various user-friendly optimization (see [[User:Barre/TODO|TODO]])
 * Tuesday
 ** Ipek Oguz: Help with Offscreen Rendering and making sure it can behave as a command-line program (without a KWW GUI)
@@ Line 12: / Line 13: @@
 ** 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]])
 * 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.

← Older revision		Revision as of 13:47, 27 June 2008
Line 25:		Line 25:
	**** <small>[http://www.codeproject.com/KB/dialog/splasher.aspx Splasher v1.32 - A Splash Screen Implementation]</small>		**** <small>[http://www.codeproject.com/KB/dialog/splasher.aspx Splasher v1.32 - A Splash Screen Implementation]</small>
	*** X11 Resources:		*** X11 Resources:
		+	* Friday
		+	** Bill: work on the launcher with splashscreen
		+	** Nathan (Gary Christensen): work on the Atlas app, optimize memory consumption

← Older revision		Revision as of 17:56, 26 June 2008
Line 14:		Line 14:
	* Thursday		* 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.		** 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.
		+	** Wendy: got some info about the current font system, and make sure she agrees with the rewrite. We will stick to a simpler system, i.e. stick to the default system font and compute a smaller font from there. There will still be a (likely hidden) way to increase the font size globally, in case somebody is presenting through a projector. Feedback from the community will lead to some adjustment, but we will stay clear from hardcoding font size and family.
		+	** Bill: work on the launcher so that it supports a splash screen and the current StarKit launcher can be avoid in RPM installers...
		+	*** Win32 Resources:
		+	**** <small>[http://www.microsoft.com/msj/1099/c/c1099.aspx How can I implement a start-up screen that displays a bitmap in MFC?]</small>
		+	**** <small>[http://support.microsoft.com/kb/815376 How to create and insert a splash screen in an SDI application or in an MDI application by using Visual C++ .NET or Visual C++ 2005]</small>
		+	**** <small>[http://www.ucancode.net/Visual_C_Control/Splash-screen-of-transparent-bitmap-vc-sample.htm VC++ MFC Sample Code: Transparent bitmap splash screen]</small>
		+	**** <small>[http://www.codeproject.com/KB/winsdk/win32splash.aspx Own-thread Win32 splash screen]</small>
		+	**** <small>[http://www.codejock.com/support/articles/mfc/general/g_2.asp Dialog With Splash Screen]</small>
		+	**** <small>[http://www.endurasoft.com/techtalk/splash.htm Making a Splash]</small>
		+	**** <small>[http://www.codeproject.com/KB/dialog/splasher.aspx Splasher v1.32 - A Splash Screen Implementation]</small>
		+	*** X11 Resources:

← Older revision		Revision as of 15:42, 26 June 2008
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.

@@ Line 10: / Line 10: @@
 ** Gary Christensen & team: CMake/CPack presentation, help
 ** Will: build Slicer3 (need to update the Wiki)
 ** Add option vtkKWTreeWithScrollbars to resize the tree manually (see [[User:Barre/TODO|TODO]])

@@ Line 5: / Line 5: @@
 ** 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...
 ** Cleanup some installation/configuration rules in QdecModule and TumorGrowth
 * Wednesday
-** Gary Christensen & team?
+** Gary Christensen & team: CMake/CPack presentation, help

← Older revision		Revision as of 16:35, 25 June 2008
Line 6:		Line 6:
	** 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...		** 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...
	** Cleanup some installation/configuration rules in QdecModule and TumorGrowth		** Cleanup some installation/configuration rules in QdecModule and TumorGrowth
		+	* Wednesday
		+	** Gary Christensen & team?

@@ Line 2: / Line 2: @@
 * Steve Aylward: SlicerIGT funding?
 * Tuesday
-** Ipek Oguz: ?
+** Ipek Oguz: Help with Offscreen Rendering and making sure it can behave as a command-line program (without a KWW GUI)
-** Craig Sharp: Helped 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...
+** 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...