#131: Implement area closing and attribue closing
-----------------------+----------------------------------------------------
Reporter: levill_r | Owner: Olena Team
Type: defect | Status: closed
Priority: minor | Milestone: Static 1.0
Component: Milena | Version: 1.0
Resolution: fixed | Keywords: completion dual naming routines algorithms
-----------------------+----------------------------------------------------
Changes (by levill_r):
* status: new => closed
* resolution: => fixed
Old description:
Currently, these files are available:
* source:trunk/morpho/mln/opening_area.hh
* source:trunk/morpho/mln/opening_attribute.hh
but there is no equivalent for closings. Implement them.
BTW, these files and their routines are called
`opening_area` and
`opening_attribute`, which is not elegant. Of course the goal is to put
forward the opening term; but IMHO, we should use namespace to do this,
not prefixes. Or rename them to `area_opening` and `attribute_opening`,
which are much more natural. Anyway, any further discussion on the
subject of naming algorithms should be carried on in another ticket.
New description:
Currently, these files are available:
* source:trunk/milena/mln/morpho/opening_area.hh
* source:trunk/milena/mln/morpho/opening_attribute.hh
but there is no equivalent for closings. Implement them.
~~BTW, these files and their routines are called `opening_area` and
`opening_attribute`, which is not elegant. Of course the goal is to put
forward the opening term; but IMHO, we should use namespace to do this,
not prefixes. Or rename them to `area_opening` and `attribute_opening`,
which are much more natural. Anyway, any further discussion on the subject
of naming algorithms should be carried on in another ticket.~~ (Moved to
#74.)
Comment:
Close this ticket (fixed in r1696).
--
Ticket URL: <https://trac.lrde.org/olena/ticket/131#comment:1>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.