CTK-Roadmap - Revision history

Pieper: /* Five Year Goals */

2011-11-17T15:40:43Z

Five Year Goals

← Older revision		Revision as of 11:40, 17 November 2011
Line 59:		Line 59:
	* Support for scene data interchange beyond dicom images (surface models, colors, transformations, annotations)		* Support for scene data interchange beyond dicom images (surface models, colors, transformations, annotations)

			== Getting in Touch ==

			Additional details are available on the [http://commontk.org commontk.org] site.

			Feel free to contact ctk-developers@commontk.org for more information. Your feedback is welcome.
	~~{{note}} See milestone page on github: https://github~~.~~com/commontk/CTK/issues/milestones~~

Pieper: /* Overview */

2011-11-17T15:37:32Z

Overview

← Older revision		Revision as of 11:37, 17 November 2011
Line 12:		Line 12:
	The goal of CTK is to support biomedical image computing. Other application areas can benefit from CTK, but the needs of other domains will not guide the selection of CTK priorities (efforts to sway development in support of more generalized goals will be resisted).		The goal of CTK is to support biomedical image computing. Other application areas can benefit from CTK, but the needs of other domains will not guide the selection of CTK priorities (efforts to sway development in support of more generalized goals will be resisted).

	The tools used in CTK are Qt, DCMTK, CMake, C++, and Python. Other relevant technologies will be considered but are unlikely to be included. Some support for ITK, VTK, OpenInventor, and related toolkits is optionally supported in terms of adapters and interfaces but CTK is not a place to house, for example, a set of algorithms implemented in ITK.		The tools used in CTK are Qt, DCMTK, CMake, C++, and Python. C++, Qt, and CMake are essential in all CTK uses, and DCMTK is essential for all DICOM uses. Python wrapping can optionally be applied on top of CTK code. Other relevant technologies will be considered but are unlikely to be included. Some support for ITK, VTK, OpenInventor, and related toolkits is optionally supported in terms of adapters and interfaces but CTK is not a place to house, for example, a set of algorithms implemented in ITK.

	CTK code is licensed under [http://www.apache.org/licenses/LICENSE-2.0.html Apache 2.0]. This means that users of CTK are allowed use the code for academic, commercial, or other purposes without paying license fees or being restricted in their ability to redistribute their code or keep it private. Absolutely no GPL, academic-use-only, non-free, or patented code belongs in CTK, but CTK can be used in projects that also include this kind of code.		CTK code is licensed under [http://www.apache.org/licenses/LICENSE-2.0.html Apache 2.0]. This means that users of CTK are allowed use the code for academic, commercial, or other purposes without paying license fees or being restricted in their ability to redistribute their code or keep it private. Absolutely no GPL, academic-use-only, non-free, or patented code belongs in CTK, but CTK can be used in projects that also include this kind of code.

Pieper: /* Overview */

2011-11-17T15:36:14Z

Overview

← Older revision		Revision as of 11:36, 17 November 2011
Line 14:		Line 14:
	The tools used in CTK are Qt, DCMTK, CMake, C++, and Python. Other relevant technologies will be considered but are unlikely to be included. Some support for ITK, VTK, OpenInventor, and related toolkits is optionally supported in terms of adapters and interfaces but CTK is not a place to house, for example, a set of algorithms implemented in ITK.		The tools used in CTK are Qt, DCMTK, CMake, C++, and Python. Other relevant technologies will be considered but are unlikely to be included. Some support for ITK, VTK, OpenInventor, and related toolkits is optionally supported in terms of adapters and interfaces but CTK is not a place to house, for example, a set of algorithms implemented in ITK.

	CTK code is licensed under Apache 2.0. Absolutely no GPL, academic-use-only, non-free, or patented code belongs in CTK.		CTK code is licensed under [http://www.apache.org/licenses/LICENSE-2.0.html Apache 2.0]. This means that users of CTK are allowed use the code for academic, commercial, or other purposes without paying license fees or being restricted in their ability to redistribute their code or keep it private. Absolutely no GPL, academic-use-only, non-free, or patented code belongs in CTK, but CTK can be used in projects that also include this kind of code.

	CTK works on topics that are not covered by existing toolkits that support the mutual interest and needs of the CTK community. The scope of current CTK efforts includes:		CTK works on topics that are not covered by existing toolkits that support the mutual interest and needs of the CTK community. The scope of current CTK efforts includes:

Pieper: /* Background */

2011-11-17T15:31:18Z

Background

← Older revision		Revision as of 11:31, 17 November 2011
Line 7:		Line 7:
	==Background==		==Background==
	*This roadmap was developed during the [[CTK-Hackfest-Nov-2011\|Sophia Antipolis 2011 Hackfest]]		*This roadmap was developed during the [[CTK-Hackfest-Nov-2011\|Sophia Antipolis 2011 Hackfest]]
	*The roadmap is based on an earlier version which can be found [[Documentation/Whitepaper\|here]] and ideas for an overview which can be found [[CTK_Integration_Levels_Overview\|~~here~~]].		*The roadmap is based on an earlier version which can be found [[Documentation/Whitepaper\|here]] and ideas for an overview which can be found in the [[CTK_Integration_Levels_Overview\| CTK Integration Levels Table]].

	==Overview==		==Overview==

JChris.FillionR: /* Overview */

2011-11-17T14:58:30Z

Overview

← Older revision		Revision as of 10:58, 17 November 2011
Line 31:		Line 31:
	* CTK does not implement image processing algorithms		* CTK does not implement image processing algorithms
	* CTK only supports the technologies explicitly called out above -- some of us may love ObjectiveC or Lua, but they have no place in CTK		* CTK only supports the technologies explicitly called out above -- some of us may love ObjectiveC or Lua, but they have no place in CTK
	* CTK cannot commit to implementing all or even a majority of the DICOM specification -- ~~priories~~ will be defined by the needs and abilities of the CTK participants.		* CTK cannot commit to implementing all or even a majority of the DICOM specification -- priorities will be defined by the needs and abilities of the CTK participants.

	==Short Term Action Items==		==Short Term Action Items==

Pieper: /* Overview */

2011-11-17T08:34:37Z

Overview

← Older revision		Revision as of 04:34, 17 November 2011
Line 31:		Line 31:
	* CTK does not implement image processing algorithms		* CTK does not implement image processing algorithms
	* CTK only supports the technologies explicitly called out above -- some of us may love ObjectiveC or Lua, but they have no place in CTK		* CTK only supports the technologies explicitly called out above -- some of us may love ObjectiveC or Lua, but they have no place in CTK
			* CTK cannot commit to implementing all or even a majority of the DICOM specification -- priories will be defined by the needs and abilities of the CTK participants.

	==Short Term Action Items==		==Short Term Action Items==

Pieper: /* Five Year Goals */

2011-11-17T07:06:08Z

Five Year Goals

← Older revision		Revision as of 03:06, 17 November 2011
Line 55:		Line 55:

	Possible developments over the 5 years if sufficient support is available:		Possible developments over the 5 years if sufficient support is available:
	* Extension of CTK to related biomedical standards (IHE)		* Extension of CTK to related biomedical standards (such as a clearly defined subset of IHE)
	* Support for scene data interchange beyond dicom images (surface models, colors, transformations, annotations)		* Support for scene data interchange beyond dicom images (surface models, colors, transformations, annotations)

Pieper: /* Overview */

2011-11-17T07:02:52Z

Overview

← Older revision		Revision as of 03:02, 17 November 2011
Line 10:		Line 10:

	==Overview==		==Overview==
	The goal of CTK is to support biomedical image computing. Other application areas can benefit from CTK, but needs of other domains will not guide the selection of CTK priorities (efforts to sway development in support of more generalized goals will be resisted).		The goal of CTK is to support biomedical image computing. Other application areas can benefit from CTK, but the needs of other domains will not guide the selection of CTK priorities (efforts to sway development in support of more generalized goals will be resisted).

	The tools used in CTK are Qt, DCMTK, CMake, C++, and Python. Other relevant technologies will be considered but are unlikely to be included. Some support for ITK, VTK, OpenInventor, and related toolkits is supported in terms of adapters and interfaces but CTK is not a place to house, for example, a set of algorithms implemented in ITK.		The tools used in CTK are Qt, DCMTK, CMake, C++, and Python. Other relevant technologies will be considered but are unlikely to be included. Some support for ITK, VTK, OpenInventor, and related toolkits is optionally supported in terms of adapters and interfaces but CTK is not a place to house, for example, a set of algorithms implemented in ITK.

	CTK code is licensed under Apache 2.0. Absolutely no GPL code belongs in CTK.		CTK code is licensed under Apache 2.0. Absolutely no GPL, academic-use-only, non-free, or patented code belongs in CTK.

	CTK works on topics that are not covered by existing toolkits that support the mutual interest and needs of the CTK community. The scope of current CTK efforts includes:		CTK works on topics that are not covered by existing toolkits that support the mutual interest and needs of the CTK community. The scope of current CTK efforts includes:
	* Medical and visualization customizations of Qt in the form of widgets, testing, and support code		* Biomedical, Medical and visualization customizations of Qt in the form of widgets, testing, and support code
	* DICOM Networking including Qt wrappers around DCMTK		* DICOM Networking including Qt wrappers around DCMTK classes
	* DICOM Application Hosting		* DICOM Application Hosting
	* Build system to support CTK		* Build system to support CTK
Line 25:		Line 25:
	* EventBus		* EventBus

	Topics other than those listed above may be considered in the future if they meet the 'mutual interest and need' criterion -- anything that is too specialized or application specific does not belong in CTK.		Topics other than those listed above may be considered in the future if they meet the 'mutual interest and need' criterion -- anything that is too specialized or too application specific does not belong in CTK.

	The scope of CTK does '''not''' include:		The scope of CTK does '''not''' include:
	* CTK does not do GPU computing		* CTK does not do GPU computing
	* CTK does not implement image processing algorithms		* CTK does not implement image processing algorithms
	* CTK only supports the technologies explicitly called out above -- some of us may love ObjectiveC or Lua, but they have no place in CTK		* CTK only supports the technologies explicitly called out above -- some of us may love ObjectiveC or Lua, but they have no place in CTK

	==Short Term Action Items==		==Short Term Action Items==

Pieper at 06:58, 17 November 2011

2011-11-17T06:58:00Z

← Older revision		Revision as of 02:58, 17 November 2011
Line 5:		Line 5:


	=~~2011~~=		==Background==
	*This roadmap was developed during the [[CTK-Hackfest-Nov-2011\|Sophia Antipolis 2011 Hackfest]]		*This roadmap was developed during the [[CTK-Hackfest-Nov-2011\|Sophia Antipolis 2011 Hackfest]]
	*The roadmap is based on an earlier version which can be found [[Documentation/Whitepaper\|here]] and ideas for an overview which can be found [[CTK_Integration_Levels_Overview\|here]].		*The roadmap is based on an earlier version which can be found [[Documentation/Whitepaper\|here]] and ideas for an overview which can be found [[CTK_Integration_Levels_Overview\|here]].

Pieper: /* Short Term Action Items */

2011-11-17T06:57:06Z

Short Term Action Items

← Older revision		Revision as of 02:57, 17 November 2011
Line 39:		Line 39:

	During 2012, CTK expects to deliver a series of 0.x releases for use in applications. Because the API and technology will continue to evolve, these will not be considered 1.x releases but will be stable and tested enough for use in application level code and inclusion in, for example, OS distributions such as debian.		During 2012, CTK expects to deliver a series of 0.x releases for use in applications. Because the API and technology will continue to evolve, these will not be considered 1.x releases but will be stable and tested enough for use in application level code and inclusion in, for example, OS distributions such as debian.

			Consistent with the technical targets, CTK software is expected to evolve in terms of API and structure. Some unused or little used dependencies will be removed (such as log4qt) and other CTK elements may be split into sub libraries. For example the Qt widgets that are not visualization or biomedical imaging specific may be split into a distinct repository so that they can be used in non-biomedical applications with minimal dependencies and excess source code.

	==Five Year Goals==		==Five Year Goals==