|
|
| (18 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| − | This 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 should be listed on the [http://www.slicer.org/slicerWiki/index.php/Slicer3:UIDesign#NEW.21:_QT_Interface_Design_Discussions UIDesign wiki page]. User feedbacks should be reported on the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Usability#Collecting_user_feedback Usability wiki page]. | + | This page has been obsoleted by [[Slicer4:QtPort/OpenDiscussions]]. Refer to it for an up-to-date status of the port to Qt. |
| − | *Please add your ideas/comments/remarks/feedback/suggestions/problems/... below.
| |
| − | *Points will be discussed during regular TCon meetings , on the Slicer developer list and/or by email.
| |
| − | *Decisions resulting from discussions should be tracked into the [http://www.na-mic.org/Bug Mantis] under the category: <code>QtGUI</code>.
| |
| − | | |
| − | =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).
| |
Latest revision as of 15:05, 21 July 2010
Home < Slicer3:Developers:Projects:QtSlicer < OpenDiscussions
