Some needs in documentation generation

[fbp]

Hi,

Here are some requirements i think necessary to improve documentation generation, some of them are from SODA

- First of all, the hability to add "if...then...else" statement in documentation generation. Thus it would be possible to add relevant elements to thegenerated parts
- hability to follow "relationship": for example,the hability to find all object which are aggregating (or agregate this element). This is a real problem in usecase report, when i whant to know whitch arctor is linked to my useCase...
- more flexible recursivity in package : i maybe need only 1 level under, not all levels... i need flexibility in titles numbering too, the level are not corresponding to model levels...
- hability to generate a more clean RTF. Here the image are well embended for microsoft ... not for openOffice. (in word, i need to show field (alt+f9), select all (ctrl+a), remplace field by their value (ctrl+f9) and the save if i want to open it with a non-microsoft editor). Other point, the used styles are not readable with a non-microsoft editor.
- hability to generate a PDF report : if i do a model centric approach, i want my document read only... that ask a goog documentation generation ;-)

Open to work on documentation generation if needed...

Regards,
Fred

[marcel_str]

I think you're right that document generation can be boosted with some additional or more flexible functionality.

Though, I think some subjects in your post are allready covered.

- hability to follow "relationship": for example,the hability to find all object which are aggregating (or agregate this element). This is a real problem in usecase report, when i whant to know whitch arctor is linked to my useCase...

If I'm right you should be able to do something like this with an element called: "model document". This element has a tagged value called: "Searchname" and "Searchvalue". I'm still exploring this functionality myself as well, but it sounds like a possible match for your issue.


- more flexible recursivity in package : i maybe need only 1 level under, not all levels... i need flexibility in titles numbering too, the level are not corresponding to model levels...

Recursivity in packages is not really flexible, though you can deside not to generate RTF for child packages or child elements. But I guess that's where flexibility stops as well.
I don't actually understand what you mean by synchronising the title numbers to level numbers. Why would you want to synchronise these?