-RM-56-MR-Redesign Selection and ROI Mechanism
Parts of this are distributed over several parts of OpenWalnut? like Kernel and Graphics Engine. Besides this, the Selection mechanism is not implemented in an easy expandable and reusable way. I.e., the graphics part of a ROI is implemented in its own class without any polymorphic relation to the ROI implementation in the kernel. Most of the selection related code is neither necessarily nor suitably placed in the kernel and too strongly related to other code. This makes maintenance and extendability a hard thing.
What needs to be done here?
- Move selection code to a subdirectory in GE and Kernel
- Review the architecture of the code
- Refactor it and implement it on the base of a more abstract architecture ** This can be implemented by using some abstract classes encapsulating the selection itself and some further classes implementing this abstract class in certain ways, like ROI or a crosshair on kernel-side and and additional layer implements the graphical representation.
This certainly can be seen as its own milestone with certain separate tickets. We should think about the selection mechanism together and find some solution.
(from redmine: created on 2011-09-19)