TODO

I list a lot of possible improvements:

• Parse the Matlab header files and build a tree to be able to perform easy transformation. Having a tree should help at applying different type of transformation (depending on the context) on the different section (Example section, See Also section). But building a tree may require a lot of memory.
• Fill in the Section ``Writing the Matlab headers''
• Code example Section: We should be able to extract the example code from the documentation, run separately those pieces of code and include the textual output as well as the figures in the final documentation. There should be a line-numbering system of the code and an automatic labelling of the code and the figure.

  How could we implement this?

  • Maybe with a code environement like this:

      \begin{code}[number=<number_of_figures>,
                   label=<label>]
      \end{code}
    

  • I suggest to internally construct the label of the code with cmd:<cmd_name>:code:<label>
  • The label of the associated figures could be
    cmd:<cmd_name>:code:<label>:fig<fig_number>
  • The Matlab command line input/output
    <cmd_name>:code:<label>:Matlab.txt. Which directory?
  • The figures could be saved under the name
    <cmd_name>:code:<label>:fig<fig_number>.<extension>. Which directory?