#294: Streamline and improve morphers -------------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: major | Milestone: Component: Milena | Version: 2.0 Keywords: | -------------------------+------------------------ Foreword: this should of course be done both in the code *and* in the documentation (e.g. in a section "Guidelines for future morphers"). Some reflexions: * We must carefully set a policy regarding embedded images (are they copied into morphers or manipulated through references/pointers?) * Hence a potential directive in the documentation regarding the implementation/manipulation of all images in Milena: should they all be manipulated by copies, but behaved as smart pointers, sharing data? * Does this mean we should never manipulate images through references (within morphers, but also elsewhere) and let the smart (tracked) pointer do the job of allocating/freeing memory? * Also, what about the constness of embeded images? All morphers are currently not equal before this aspect. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/294> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform