Difference between revisions of "Slicer3:Developers:Projects:QtSlicer/OpenDiscussions"
From Slicer Wiki
| Line 8: | Line 8: | ||
=Closed Issues= | =Closed Issues= | ||
* Module Logic | * Module Logic | ||
| − | ** Issue: Change qSlicerModuleLogic into | + | ** Issue: Change qSlicerModuleLogic into vtkSlicerModuleLogic |
** Reporter: Alexander Yarmarkovich | ** Reporter: Alexander Yarmarkovich | ||
| − | ** Motivation: A lot of slicer logics already exist, using qSlicerModuleLogic implies to wrap this logics. Why not directly use the | + | ** Motivation: A lot of slicer logics already exist, using qSlicerModuleLogic implies to wrap this logics. Why not directly use the vtkSlicerModuleLogic? |
** Decision: Talked by email and over the phone during the Tuesday TCon (01/26/10). The suggestion has been accepted. | ** Decision: Talked by email and over the phone during the Tuesday TCon (01/26/10). The suggestion has been accepted. | ||
** Result: The change has been committed on 01/28/10 (r11850, r11852, r11853, r11854) | ** Result: The change has been committed on 01/28/10 (r11850, r11852, r11853, r11854) | ||
| + | ** Note: While new module logics must derive from vtkSlicerModuleLogic, logics deriving from vtkSlicerLogic are supported for backward compatibility reasons (the core module logics derive from vtkSlicerLogic). | ||
Revision as of 16:03, 29 January 2010
Home < Slicer3:Developers:Projects:QtSlicer < OpenDiscussionsThis page gathers discussions about code architecture/implementation/design of the Slicer port to Qt. This page is mainly for developers as it concerns the internal/implementation part of Slicer, discussions about the interface design or user feedback should be listed on the UIDesign wiki page.
- Please add your comments and feedback below.
- Points will be discussed during regular TCon meetings , as well as on the Slicer developer list.
- Decisions resulting from discussions should be tracked by adding an issue into Mantis under the category:
QtGUI.
Open Issues
Closed Issues
- Module Logic
- Issue: Change qSlicerModuleLogic into vtkSlicerModuleLogic
- Reporter: Alexander Yarmarkovich
- Motivation: A lot of slicer logics already exist, using qSlicerModuleLogic implies to wrap this logics. Why not directly use the vtkSlicerModuleLogic?
- Decision: Talked by email and over the phone during the Tuesday TCon (01/26/10). The suggestion has been accepted.
- Result: The change has been committed on 01/28/10 (r11850, r11852, r11853, r11854)
- Note: While new module logics must derive from vtkSlicerModuleLogic, logics deriving from vtkSlicerLogic are supported for backward compatibility reasons (the core module logics derive from vtkSlicerLogic).
