Difference between revisions of "Developer Meetings/20130702"
From Slicer Wiki
| (9 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
== To discuss == | == To discuss == | ||
* Release plans | * Release plans | ||
| − | ** Need to have a version for upcoming training events [http://www.na-mic.org/Wiki/index.php/Events starting in September] | + | ** Need to have a version/stable release for upcoming training events [http://www.na-mic.org/Wiki/index.php/Events starting in September] |
** Need time to test and update documentation | ** Need time to test and update documentation | ||
* Triage of [http://www.na-mic.org/Bug/roadmap_page.php the 4.3 release roadmap] | * Triage of [http://www.na-mic.org/Bug/roadmap_page.php the 4.3 release roadmap] | ||
| + | ** What to do with 'unfunded' feature requests and issues? Suggestion is to assign them to None as a flag that these are good project for new developers to address. | ||
| + | * How to simplify the workflow for contributing extensions. Goal: That a biomedical engineer can contribute an extension without hand holding. | ||
| + | ** Documentation to warn against adding new libraries and listing of ones that are available. | ||
| + | ** One click upload | ||
* [http://www.na-mic.org/Bug/view.php?id=3200 #3200]: Option to make non-interpolated views as default | * [http://www.na-mic.org/Bug/view.php?id=3200 #3200]: Option to make non-interpolated views as default | ||
** Sorry I won't make the hangout. Viewing individual pixels is generally useful for technical work, such as medical physics. It is a common feature in commercial programs, and we eventually will want in Slicer, but not terribly urgent. -Greg | ** Sorry I won't make the hangout. Viewing individual pixels is generally useful for technical work, such as medical physics. It is a common feature in commercial programs, and we eventually will want in Slicer, but not terribly urgent. -Greg | ||
| + | ** It is available on a per volume level in the volume module and on a per volume and viewer level in the Slice viewers/3D viewers. | ||
| + | [[image:Screen Shot 2013-07-01 at 4.32.41 PM.png|thumb| 200px|right|different interpolation options in slice and 3D viewers]] | ||
| + | [[image:Screen Shot 2013-07-02 at 2.20.17 PM.png|thumb| 200px|right|Turn off interpolation attribute of the volume using the slice view controller]] | ||
| + | * Why does this work to get at displayable managers in python: | ||
| + | <code> | ||
| + | lm = slicer.app.layoutManager() | ||
| + | td = lm.threeDWidget(0) | ||
| + | ms = td.getDisplayableManagers() | ||
| + | </code> | ||
| + | *but not this: | ||
| + | <code> | ||
| + | slicer.vtkMRMLAnnotationFiducialDisplayableManager() | ||
| + | </code> | ||
| + | * Answer: we need an __initi.py__ with <code> from MRMLDisplayableManagerPython import * </code> similar to Base/Python/mrml.py | ||
| + | * Also, why are the public methods in the superclass vtkMRMLAnnotationDisplayableManager not available when getting a vtkMRMLAnnotationFiducialDisplayableManager? | ||
| + | <code> | ||
| + | lm = slicer.app.layoutManager() | ||
| + | td = lm.threeDWidget(0) | ||
| + | ms = td.getDisplayableManagers() | ||
| + | afdm = ms.GetItemAsObject(4) | ||
| + | </code> | ||
Latest revision as of 18:43, 2 July 2013
Home < Developer Meetings < 20130702Contents
To discuss
- Release plans
- Need to have a version/stable release for upcoming training events starting in September
- Need time to test and update documentation
- Triage of the 4.3 release roadmap
- What to do with 'unfunded' feature requests and issues? Suggestion is to assign them to None as a flag that these are good project for new developers to address.
- How to simplify the workflow for contributing extensions. Goal: That a biomedical engineer can contribute an extension without hand holding.
- Documentation to warn against adding new libraries and listing of ones that are available.
- One click upload
- #3200: Option to make non-interpolated views as default
- Sorry I won't make the hangout. Viewing individual pixels is generally useful for technical work, such as medical physics. It is a common feature in commercial programs, and we eventually will want in Slicer, but not terribly urgent. -Greg
- It is available on a per volume level in the volume module and on a per volume and viewer level in the Slice viewers/3D viewers.
- Why does this work to get at displayable managers in python:
lm = slicer.app.layoutManager()
td = lm.threeDWidget(0)
ms = td.getDisplayableManagers()
- but not this:
slicer.vtkMRMLAnnotationFiducialDisplayableManager()
- Answer: we need an __initi.py__ with
from MRMLDisplayableManagerPython import *similar to Base/Python/mrml.py - Also, why are the public methods in the superclass vtkMRMLAnnotationDisplayableManager not available when getting a vtkMRMLAnnotationFiducialDisplayableManager?
lm = slicer.app.layoutManager()
td = lm.threeDWidget(0)
ms = td.getDisplayableManagers()
afdm = ms.GetItemAsObject(4)
