#145: Add a n-dimensional regular image type on a cubical/rectangular grid
----------------------+-----------------------------------------------------
Reporter: levill_r | Owner: Olena Team
Type: task | Status: new
Priority: major | Milestone: Olena 1.0
Component: Milena | Version: 1.0
Keywords: |
----------------------+-----------------------------------------------------
This image type, e.g.
{{{
#cpp
template <unsigned Dim, typename T>
class regular_image
}}}
(with `Dim` being the dimension and `T` the value type) would generalize
`image1d`, `image2d` and `image3d`.
* First, develop a version with no support for borders.
* Then, add support for borders.
See the code in Olena 0.11: a similar image type was present in this
version.
--
Ticket URL: <https://trac.lrde.org/olena/ticket/145>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.
#138: Factor code between native and BGL-based graph structures
---------------------------------+------------------------------------------
Reporter: levill_r | Owner: Olena Team
Type: task | Status: new
Priority: major | Milestone: Olena 1.0
Component: Milena | Version: 1.0
Keywords: boost graphs factor |
---------------------------------+------------------------------------------
This is a continuing work of #123.
* Ensure the native and BGL-based graphs offer the same services.
* Ensure graph-based images can be built upon any of these categories of
graphs.
* Milena should provide a uniform interface, whatever the graph engine
used (native or BGL-based).
* Moreover, `configure` should check for the BGL presence and usability,
and disable the BGL-based code when needed (at least in tests, and in
compiled tools -- we should install headers, even if the BGL is not
present, IMHO).
--
Ticket URL: <https://trac.lrde.org/olena/ticket/138>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.
#209: Fix copyright headers in documentation
----------------------+-----------------------------------------------------
Reporter: levill_r | Owner: Olena Team
Type: defect | Status: new
Priority: minor | Milestone: Olena 1.1
Component: Milena | Version: 1.0
Keywords: |
----------------------+-----------------------------------------------------
LaTeX files in milena/doc/ have the special clause:
{{{
As a special exception, you may use this file as part of a free
software library without restriction. Specifically, if other files
instantiate templates or use macros or inline functions from this
file, or you compile this file and link it with other files to
produce an executable, this file does not by itself cause the
resulting executable to be covered by the GNU General Public
License. This exception does not however invalidate any other
reasons why the executable file might be covered by the GNU General
Public License.
}}}
which is meaningless! Remove it.
Moreover, we might want to consider another license for the documentation,
like the GNU FDL or the LPPL (I'm not sure the GPL is suited for
documentation).
EDIT: The products (e.g. `tutorial.pdf`) have FDL headers! WTF?
--
Ticket URL: <https://trac.lrde.org/olena/ticket/209>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.
#169: Lighten the repository
-------------------------+--------------------------------------------------
Reporter: levill_r | Owner: Olena Team
Type: enhancement | Status: new
Priority: minor | Milestone: Olena 1.0
Component: Milena | Version: 1.0
Keywords: |
-------------------------+--------------------------------------------------
Getting a fresh working copy from the repository takes time, as there are
many medium- or big-sized files (images and meshes). We should probably
remove some of them, or move them elsewhere.
Of course, we should remove most of these files from the distribution as
well.
--
Ticket URL: <https://trac.lrde.org/olena/ticket/169>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.
#202: Document build procedures
----------------------+-----------------------------------------------------
Reporter: levill_r | Owner: levill_r
Type: task | Status: new
Priority: critical | Milestone:
Component: Trac | Version: 1.0
Keywords: gcc icpc |
----------------------+-----------------------------------------------------
Write a Trac page (several pages?) on these topics:
* Why `make` is the way to go.
* Why you should (normally) run `bootstrap` only once.
* Why you should (normally) run `configure` only once per build
directory.
* How to build Olena with the Intel C++ Compiler (ICC)
* By setting it a build time (not very good).
* By setting it a configuration time (better).
* By setting it in a `config.site` file (the best).
* How to automate things using `CONFIG_SITE`.
* Why compiling from Emacs (using `M-x compile`) is better than...
* ...Compiling with `make` from a terminal.
* ...Compiling with `g++` from a terminal (arg!).
This is not restricted to Olena, so we might want to move this material
elsewhere later.
--
Ticket URL: <https://trac.lrde.org/olena/ticket/202>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.
#196: Kill Doxygen warnings in Olena 1.0
--------------------+-------------------------------------------------------
Reporter: theo | Owner: Olena Team
Type: task | Status: new
Priority: major | Milestone: Olena 1.0
Component: Milena | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
`doxygen` emits warnings for certain documented parts; adjust the
documentation or Doxygen's options to get rid of them.
--
Ticket URL: <https://trac.lrde.org/olena/ticket/196>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.
#208: Fix dependencies of the HTML documentation generation?
----------------------+-----------------------------------------------------
Reporter: levill_r | Owner: Olena Team
Type: defect | Status: new
Priority: minor | Milestone: Olena 1.1
Component: Milena | Version: 1.0
Keywords: doc |
----------------------+-----------------------------------------------------
The generation of the HTML documentation requires a file named `html.sty`,
which is not provided by HeVeA, but by latex2html. Is that right? I
thought we only had a dependency on the former, not the latter.
--
Ticket URL: <https://trac.lrde.org/olena/ticket/208>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.
#172: Experiment SCOOP 1.5/2 with C++0x concepts
-------------------------+--------------------------------------------------
Reporter: levill_r | Owner: Olena Team
Type: enhancement | Status: new
Priority: trivial | Milestone: Olena 2.0
Component: Olena-NG | Version: 2.0
Keywords: |
-------------------------+--------------------------------------------------
What I call SCOOP 1.5 is the paradigm currently used in Milena 1.0 (as of
Nov. 2008), and SCOOP 2 the paradigm described in the MPOOL'08 paper (used
in Olena-NG).
--
Ticket URL: <https://trac.lrde.org/olena/ticket/172>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.
#210: Check ImageMagick save() routine
---------------------+------------------------------------------------------
Reporter: freling | Owner: freling
Type: defect | Status: new
Priority: minor | Milestone: Olena 1.1
Component: Milena | Version: 1.0
Keywords: io |
---------------------+------------------------------------------------------
The save() routine located in mln/io/magick/save.hh has a weird behavior.
We have to do a strange affectation (IM_value = 256 - MLN_value) but we
don't really know why.
--
Ticket URL: <https://trac.lrde.org/olena/ticket/210>
Olena <http://olena.lrde.epita.fr>
Olena, a generic and efficient C++ image processing library.
