Difference between revisions of "2010 Summer Project Week PythonQt"
From NAMIC Wiki
| Line 22: | Line 22: | ||
<h3>Approach, Plan</h3> | <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). | 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> | ||
<div style="width: 40%; float: left;"> | <div style="width: 40%; float: left;"> | ||
Revision as of 18:57, 3 June 2010
Home < 2010 Summer Project Week PythonQt
Example Python Shell session with only a subset of QtGui exposed.
Key Investigators
- Isomics: Steve Pieper
- Kitware: Jc
Objective
A ctkPythonShell widget [1] 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).
Approach, Plan
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.
Progress
TBA
