Messages

1

Suggestions and Requests / Reverseengineering: Doxygenstyle

« on: March 26, 2012, 09:56:00 pm »

Please make EA able to parse the Doxygen-style comments, I guess we are not the only ones programming using this particular style.
example:
/** This function returns the last error information and should be called if an API
*  function does not return RETURN_OK.
*
* @note
* funktionnotes
*
* @param[out] pErrorInfo    ErrorInformation blabla
*                          
*/
void getLastErrorInfo(ErrorInfo *const pErrorInfo);

@param[kind] marks the parameter notes, and should be added as the parameters notes -- and the kind should also modify the parameterkind in the EA-model.

see: http://www.stack.nl/~dimitri/doxygen/commands.html

Thank you

2

General Board / CodeGen automatically add behavior of element

« on: July 21, 2012, 12:06:43 am »

Is there a possibility of letting the codegen modify the behavior field of the element it was used on?
And is the DocumentGenerator able to print the contents of this field?

Or do you know of another way to get the function signature into the EA doc?

Thx

3

General Board / Re: Reverseengineering: Parameter-Notes (doxygenst

« on: March 28, 2012, 01:43:04 am »

4 years ago EA was capable of understanding at least the @param part, see:
http://dev.lsstcorp.org/trac/wiki/EaIngestNeeds

4

General Board / Re: Reverseengineering: Parameter-Notes (doxygenst

« on: March 26, 2012, 09:48:35 pm »

Ok,

thank you, writing a feature request now ;-)

5

General Board / Re: Reverseengineering: Parameter-Notes (doxygenst

« on: March 23, 2012, 06:02:08 pm »

*poke*

6

General Board / Reverseengineering: Parameter-Notes (doxygenstyle)

« on: March 20, 2012, 02:34:42 am »

Hi,

Does anyone know, how I can import sourcecode (C) with parameter-notes and parameter-kind?
Our projects are Doxygenstyle commented, so the information is there and parseable, but EA doesn't seem to understand where to put the comments.
example:
/** This function returns the last error information and should be called if an API
 *  function does not return RETURN_OK.
 *
 * @note
 * funktionnotes
 *
 * @param[out] pErrorInfo    ErrorInformation blabla
 *                          
 *
 */
void getLastErrorInfo(ErrorInfo *const pErrorInfo);

This whole comment get's into the function-notes, I want the "ErrorInformation blabla" in the parameter-notes and the out in parameter-kind.

Every help will be greatly appreciatet.  

7

General Board / Re: Set Constants for a single Documentation(not P

« on: February 22, 2012, 11:36:01 pm »

The project constants work in EA 8 too, but they are for the whole project.
I need constants for a single Documentation-Folder

8

General Board / Set Constants for a single Documentation(not Proj)

« on: February 22, 2012, 01:01:38 am »

Hi,

does anyone of you know a way to set some constants for a single Documentation?
We have a project with more than one documentationfolder, and the DocIDs of each document need to be unique (and be set prior to the documentation template run, I know how I can set Fieldfunctions and later add the DocID in Word, but that's not what I want).
Tagged Values kinda work, but you can't add a tagged-value-field into the firstpage-header (or at least I couldn't).

Any help would be appreciated

edit: EA 8.0, if you found a nice EA9 trick, it wouldn't help much  :-/

9

General Board / Re: RTF Documentation: add single Diagram

« on: January 11, 2012, 01:32:42 am »

TY,
tho it didn't help

If I use simple/extended search from the standard searches I only get the first diagram of any result-component.

If I use a search that results a diagram the document generator failes.

10

General Board / RTF Documentation: add single Diagram

« on: January 10, 2012, 07:41:59 pm »

Hi folks,
hope you can help me.
I want to add a single diagram into my documentation, I tried some ways, but none worked.

best way so far: create custom search that returns only the diagram, but as soon as I create a model document and add the tagged values the RTF-Generator quits with an error (Document generation failed) and returns an empty document.

Since there are more than only one digram in the package I can't just add the package.

Any help would be greatly appreciated

11

General Board / Re: reuse of elements/diagrams in new projects

« on: December 20, 2011, 02:59:46 am »

I dont know the cvs capability of Visual Studio, but the builtin-package-control can work with .xml import/export -- I would suggest you use that and work in different models of the same project. The path to the .xml should be a networkpath with all reading- and you writing-rights
That way you can use linked components and the like.

12

General Board / Re: About Classifier ":"

« on: December 20, 2011, 02:50:52 am »

It's not a bug, it's a feature

solution:
1:you could only link the class2 into the class1s-diagram and keep class 2 in the package1 (yah, solves the problem, but readability...)
so here is the real solution:

2:Set Diagram > Properties > Diagram > "Use Alias if Avaible" to True and set an alias for Class2.
Problem solved

13

General Board / Generate Code for Components

« on: December 16, 2011, 02:48:37 am »

Hi,
since there is no 'Newbie'-section, I'm posting here.
I'm using EA 8.0.864

First of all -- why dont packaging components behave like components in a diagram (e.g. it doesnt get to use ports, assembly, exposed interface and the like)?

A Packaging Component is an element that appears very similar to a Component in a diagram but behaves as a Package in the Project Browser (that is, it can be version controlled and can contain other Packages and elements). It is typically used in Component diagrams.

Or am I getting something wrong?

Secondly:
I think I missed somewhere a setting -- "generate code" is greyed out for the component in the Project Browser, and if I try to generate the code for the class/interface within the component I get

Generation of code for inner classes is only supported through generation the outer class

So a component behaves like a class, but I cant get it to genrate me some code  

The optimal solution for me would eithe be, that packaging components behave like components in the diagram (and not only look alike) or that components behave like packages while generation code.

Any help will be greatly appreciated.

Niy

14

Bugs and Issues / Re: RTF Documentation: only first Diagram of Compo

« on: January 19, 2012, 01:35:17 am »

Hi,
I tryed it, it's unrelated -- still only the first diagram, I think there is a Problem with the way EA handles subcomponents.

It's really bad that there is no debugging for the RTF- and Code-Generator, could help solving a lot of issues to see what happens when and why

15

Bugs and Issues / RTF Documentation: only first Diagram of Component

« on: January 17, 2012, 03:30:46 am »

EA v. 8.0.864

If I generate a documentation containing Diagrams and use the simple search to identify a single component in my model, it only generates the first diagram into my document.
(If I tick the box 'exclude image from documentation' for the first diagram, it doesn't generate any diagram at all)