Developer Meetings/20130326 - Revision history

Grundlett: Text replacement - "slicerWiki/index.php" to "wiki"

2019-11-21T17:05:21Z

Text replacement - "slicerWiki/index.php" to "wiki"

2013-03-27T21:21:28Z

Conclusion

2013-03-27T18:48:43Z

Conclusion

2013-03-27T18:48:18Z

Conclusion

2013-03-27T17:21:14Z

2013-03-27T17:16:42Z

2013-03-27T14:20:07Z

Conclusion

2013-03-26T21:43:39Z

Conclusion

2013-03-26T21:37:04Z

2013-03-26T21:33:03Z

@@ Line 3: / Line 3: @@
 == To discuss ==
 *the discussion about how to reorganize the modules in Slicer should continue.
-http://wiki.slicer.org/slicerWiki/index.php/Developer_Meetings/20130226#Module_reorganization
+http://wiki.slicer.org/wiki/Developer_Meetings/20130226#Module_reorganization
 *installed extensions do not display their logos but a generic image. Why?
@@ Line 92: / Line 92: @@
 ** Why? Supporting internationalization properly would require to test all ITK/VTK/Teem/.. readers and we don't have the funding or resources to support that effort. If it is something you are interested in, make sure to drop an email on the developer list. We will be happy to provide more information.
 ** Issues: [http://www.na-mic.org/Bug/view.php?id=3029 3029]
-** Additional note will be tracked on the following page: http://www.slicer.org/slicerWiki/index.php/Documentation/Labs/I18N
+** Additional note will be tracked on the following page: http://www.slicer.org/wiki/Documentation/Labs/I18N

← Older revision		Revision as of 21:21, 27 March 2013
Line 92:		Line 92:
	** Why? Supporting internationalization properly would require to test all ITK/VTK/Teem/.. readers and we don't have the funding or resources to support that effort. If it is something you are interested in, make sure to drop an email on the developer list. We will be happy to provide more information.		** Why? Supporting internationalization properly would require to test all ITK/VTK/Teem/.. readers and we don't have the funding or resources to support that effort. If it is something you are interested in, make sure to drop an email on the developer list. We will be happy to provide more information.
	** Issues: [http://www.na-mic.org/Bug/view.php?id=3029 3029]		** Issues: [http://www.na-mic.org/Bug/view.php?id=3029 3029]
		+	** Additional note will be tracked on the following page: http://www.slicer.org/slicerWiki/index.php/Documentation/Labs/I18N

← Older revision		Revision as of 18:48, 27 March 2013
Line 91:		Line 91:
	** We reach consensus: Official support for i18n will be disabled. A CMake option named Slicer_BUILD_I18N_SUPPORT will be added and the option won't be actively supported or tested.		** We reach consensus: Official support for i18n will be disabled. A CMake option named Slicer_BUILD_I18N_SUPPORT will be added and the option won't be actively supported or tested.
	** Why? Supporting internationalization properly would require to test all ITK/VTK/Teem/.. readers and we don't have the funding or resources to support that effort. If it is something you are interested in, make sure to drop an email on the developer list. We will be happy to provide more information.		** Why? Supporting internationalization properly would require to test all ITK/VTK/Teem/.. readers and we don't have the funding or resources to support that effort. If it is something you are interested in, make sure to drop an email on the developer list. We will be happy to provide more information.
		+	** Issues: [http://www.na-mic.org/Bug/view.php?id=3029 3029]

← Older revision		Revision as of 18:48, 27 March 2013
Line 87:		Line 87:
	* CLI category		* CLI category
	** Slicer should propose a mechanism to map CLI to different category. Application specific category shouldn't be added to the CLI itself.		** Slicer should propose a mechanism to map CLI to different category. Application specific category shouldn't be added to the CLI itself.
		+
		+	* Internationalization
		+	** We reach consensus: Official support for i18n will be disabled. A CMake option named Slicer_BUILD_I18N_SUPPORT will be added and the option won't be actively supported or tested.
		+	** Why? Supporting internationalization properly would require to test all ITK/VTK/Teem/.. readers and we don't have the funding or resources to support that effort. If it is something you are interested in, make sure to drop an email on the developer list. We will be happy to provide more information.

← Older revision		Revision as of 17:21, 27 March 2013
Line 81:		Line 81:
	** User manual should be editable by both developer and user		** User manual should be editable by both developer and user
	** Current documentation system (wiki) need to be updated to be more user-friendly.		** Current documentation system (wiki) need to be updated to be more user-friendly.
		+
		+	* Jc: Will be adding a "Developer Tools" option in the setting
		+	** When enabled, it will show the developer category in the module menu.
		+
		+	* CLI category
		+	** Slicer should propose a mechanism to map CLI to different category. Application specific category shouldn't be added to the CLI itself.

@@ Line 54: / Line 54: @@
 * CMake'ified python: https://github.com/jcfr/Slicer/tree/use-cmakeified-python
 ** Currently investigating:
 *** Windows: Crash on start.
@@ Line 63: / Line 64: @@
 ** The idea would be to move every "legacy" cli into an extension and create a "meta" extension allowing to install all these cli modules at ones.
 ** Andriy is clarifying with Andras and Tamas the move of MRIBiasFieldCorrection" into legacy category.
 * Ron asked where the extension description should be entered so that it appear on the extension catalog.
@@ Line 70: / Line 72: @@
 *Ohloh presence: All agree we should have on entry named "Slicer".
-* Nicole, Sankhesh and Julien discussed the "Model Hierarchies" +  "scene views" issue
+* Extensions catalog: Extension screenshots have the wrong aspect ratio

← Older revision		Revision as of 14:20, 27 March 2013
Line 70:		Line 70:
	*Ohloh presence: All agree we should have on entry named "Slicer".		*Ohloh presence: All agree we should have on entry named "Slicer".

−	* Nicole, Sankhesh and ~~Nicole~~ discussed the "Model Hierarchies" + "scene views" issue	+	* Nicole, Sankhesh and Julien discussed the "Model Hierarchies" + "scene views" issue

← Older revision		Revision as of 21:37, 26 March 2013
Line 60:		Line 60:

	== Conclusion ==		== Conclusion ==
		+	* Discussed module re-organization
		+	** The idea would be to move every "legacy" cli into an extension and create a "meta" extension allowing to install all these cli modules at ones.
		+	** Andriy is clarifying with Andras and Tamas the move of MRIBiasFieldCorrection" into legacy category.
		+
		+	*Ohloh presence: All agree we should have on entry named "Slicer".
		+
		+	* Nicole, Sankhesh and Nicole discussed the "Model Hierarchies" + "scene views" issue