Difference between revisions of "2017 Winter Project Week/Slicer Qt5 and Python3"

Revision as of 18:43, 12 January 2017

Home < 2017 Winter Project Week < Slicer Qt5 and Python3

Objective	Approach and Plan	Progress and Next Steps
Bring Slicer up to speed with the latest supported versions of key infrastructure Ensure we support key features, bug fixes, etc for the latest OS versions and compilers Stay in sync with global development community Get a specific idea of how much work remains to implement the required ports Building Slicer core Packaging releases Building and packaging extensions Develop a release plan and general schedule Develop transition guides for Slicer community	Review preliminary work on Qt5 port ~~Try to get a running build~~ Use the work-in-progess build! Develop a punch list of work required to complete the ports	Multiple strong motivations to upgrade Qt 4 no longer supported, doesn't build or work right on new OS versions Qt5's QtWebEngine provides many important features OAuth2 for SlicerPathology Database browsers Web visualization packages WebGL Progress Steve's initial port covered many of the important issues Jc has dug into the CMake files in CTK and Slicer Hope is to have Qt4 and Qt5 Nightly builds "soon"

@@ Line 38: / Line 38: @@
 |
 <!-- Progress and Next steps bullet points (fill out at the end of project week -->
-*
+Multiple strong motivations to upgrade
+* Qt 4 no longer supported, doesn't build or work right on new OS versions
+* Qt5's QtWebEngine provides many important features
+** OAuth2 for SlicerPathology
+** Database browsers
+** Web visualization packages
+** WebGL
+Progress
+* Steve's initial port covered many of the important issues
+* Jc has dug into the CMake files in CTK and Slicer
+* Hope is to have Qt4 and Qt5 Nightly builds "soon"
 |}
 ==Background and References==
 <!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->