Doxygen comments such as: //!< and ///< and /**< */ can easily be patched, just truncate the extra "<".
Unfortunately, Doxygen and EA with HTML generations are the only tools so far which can deals with C, C++, Java and similar languages.
However, on the good side, Doxygen jams on large and very complicated template "code", while EA doesn't show everything that doxygen produce, but at least "works" somehow, but doesn't show "meaningful" associations, which must be manually added. The work around for doxygen being of reverse engineering small digestible subsets.
The example template in question << 255
Try this:
LargeClassName<LARGE_PARAMETER_NO_1,LARGE_PARAMETER_NO_2,LARGE_PARAMETER_NO3,LARGE_PARAMETER4,LARGE_PARAMETER_N5,LARGE_PARAMETER_N6,PARAMETER7,PARAM_NO8>
or with params:
LargeClassName<LARGE_PARAMETER_NO_1 : size_t =0,LARGE_PARAMETER_NO_2 : size_t =0,LARGE_PARAMETER_NO3 : size_t =0,LARGE_PARAMETER4 : size_t =0,LARGE_PARAMETER_N5 : size_t =0,LARGE_PARAMETER_N6 : class,PARAMETER7 : class,PARAM_NO8 : class = XClass>
I get 141 and 251 bytes respectively including spaces and class name, in the graph it gets truncated around LAR after Pameter 4. :-/
Also, each template parameter should "normally" be on a database in seperate table rows/cols, right?!
So, in theory each template parameter name/type/value could be varchar(255)... like this?
CREATE TABLE template_params (
uiid int NOT NULL,
parent_id int NOT NULL,
no int NOT NULL,
name VARCHAR( 255 ) NOT NULL,
type VARCHAR( 255 ),
value VARCHAR( 255 ),
);
RTF generation, I'm not sure how I'm still figuring out, I try to have "everything" in EA... However, I'm still playing with tags. For instance, having the Software Design Document (IEEE SDD), having the introduction in plain text in EA... glossary... definitions, assumptions, risks, assessments, dependancies, etc. Samething for the Software Requirement Specification Document (IEEE SRS) or Software Architecture Document (SAD).
Such that when I regenerate the document from EA,
I don't have to copy-paste around or hard-code things into a RTF template.
I'm also not sure how to create a Revision History of the document in the RTF template, with date, version, author, description of changes... inside a table such that when I change the document in EA, the generated RTF document shows the change being done.
Also, right-clicking and go to "notes" for every class, functions, attributes is not really "efficient".
Editing in plain-text is however, so having an XML file would be handy, or having proper comments in the generated C++ source code, that could be afterwards be reparsed and reintegrated easily would be handy.
Also, it seems that enum values are not properly reverse engineered into "tagged values", don't know why.
Finally, what I meant was that an EA project (EAP extension) can be exported/imported into a single XML database flatfile. It doesn't have to be efficient just 1:1 mapping would be sufficient, so we can add other scripts and tools around it more easily.
Have a nice day!
