View source for 2010 Summer Project Week PythonQt

__NOTOC__
<gallery>
Image:PW-MIT2010.png|[[2010_Summer_Project_Week#Projects|Back to Projects List]]
Image:CtkPythonShell-in-SlicerQT.png|Example Python Shell session with only a subset of QtGui exposed.
</gallery>

[[Image:CtkSimplePythonShell.png|Example GUI created within ctkPythonShell|thumb|400px]]

==Key Investigators==
* Isomics: Steve Pieper
* Kitware: Jc

<div style="margin: 20px;">
<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Objective</h3>
A ctkPythonShell widget [http://github.com/pieper/CTK/tree/master/Libs/Scripting/Python/Widgets/] is based on the example given in PythonQt and is already included in SlicerQT.

Our goal is to enable a usable subset of QtGui capability via python (currently on a basic subset is available).

</div>
<div style="width: 27%; float: left; padding-right: 3%;">

<h3>Approach, Plan</h3>
First we should have a stand alone example in CTK, then this will be exposed in slicer.  A few issues about how options for external projects should be handled when nested in external projects (PythonQt is an external project of CTK, which is an external project of Slicer4).

If time, also look at how to get ipython embedded in ctkPythonShell.
</div>
<div style="width: 40%; float: left;">

<h3>Progress</h3>
We have confirmed that this can be done, but it is not yet enabled through CTK and Slicer by default.

We spent a lot of time on architecture and our divide and conquer strategy for implementing the slicer4 qt functionality with working alpha versions by September and Betas for the January 2011 project week.  Near term focus for Steve will be porting SWidget tcl functionality to tcl and the new vtkMRMLDisplayableManager framework using a python interpreter layer for vtk calls.  

</div>
</div>

<div style="width: 97%; float: left;">

==Delivery Mechanism==

CTK and Slicer4.

==References==
* http://commontk.org
* http://pythonqt.sourceforge.net
* http://ipython.scipy.org/
</div>