Messages

1

Suggestions and Requests / Re: Polls for features

« on: April 10, 2006, 11:32:22 am »

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!

2

Suggestions and Requests / Polls for features

« on: April 10, 2006, 09:50:24 am »

I would like to make a small suggestions would it be possible to add a small vote sections for new features.  

I think it would be a nice way of asking us ,
if a feature is needed, really needed or not at all, instead of searching the forums.  

You can add me for:
- Doxygen comment style parsing  
- Unlimited character length template parameters, since it gets automatically truncated  
- Better control over RTF document generations
- Being able to import/export EAP into XML format for scripting purposes.

For what is worth, I've been using Rational Rose since the beginning,
but since I used EA for a while now, I can say that it is definitively
better, easier and the RTF document generation is just awesome!  

3

Suggestions and Requests / Re: JavaDoc comment construct "///<"

« on: April 16, 2006, 03:30:48 pm »

Well, I think that being able to support "C++, C, Java, Objective-C, Python, IDL (Corba and Microsoft flavors) and to some extent PHP, C#, and D" and even some Javascript, in both directions (before or after the code) in contextual mode or out of context is quite interesting no?  

http://www.stack.nl/~dimitri/doxygen/

4

Suggestions and Requests / Re: JavaDoc comment construct "///<"

« on: April 11, 2006, 05:10:03 pm »

I agree that it is not "simple" to provide all the feature of Doxygen in one go; however, like I said a short-term patch can be made such that it "seems" to works in "most cases". Which would be better than the current statu quo.

If it is wrongly assigned then we can still hand edit it ourself, like we currently do.

I really would appreciate like others if all doxygen style extension were supported like @param, \param, @author, \author, @return, \return, @see, \sa, @deprecated, @warning, etc.

At least, the major ones, more can be added in a "future version".
I'm sure some folks might use all of them, but these are the ones I use the most.

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

5

Suggestions and Requests / Re: JavaDoc comment construct "///<"

« on: April 11, 2006, 07:07:39 am »

Doxygen comments which are right handed have an extra "<" character like this:

int x; ///<  some comment X
int y; //!<  some comment Y
int z; /**< some comment Z */

or like this:

int x;


///<  some comment X

int y;

//!<  some comment Y

int z;

/**< some comment Z */


The other possibility is like this:

/// Some comment X
int x;

//! Some comment Y
int y;

/** Some comment Z */
int z;

/** Some comment W */  int w;

The reasons for the extra "<" is that Doxygen use GNU Flex and whitespace considerations are not retained; therefore, a marker must be used to distinguish between the comment applies for the code after on the right-hand-side (Default) and the comment applies for the code before on the left-hand-side //!<

In EA, whitespace are retained in the parser and this is automatically done, so no need for the extra "<" character.

The only thing that needs to be done is very simple, just add a patch to the parser, such that
//!< ///< and /**< */ removes the extra "<" character.

Also, this form is also valid:
/**************************< Some comment */
/////////////////////////////////////////////< Some Comment

6

Automation Interface, Add-Ins and Tools / Re: XML import/export of complete EAP Project File

« on: April 30, 2006, 06:11:06 pm »

Then why not have a "Save as EAX" / "Open as EAX" options, would be much simpler...
BTW, I don't want to "Select anything",
I want an exact photocopy of the file in XML.

I will try it tomorrow...

7

Automation Interface, Add-Ins and Tools / XML import/export of complete EAP Project File

« on: April 29, 2006, 11:19:01 am »

Basically, my request is very simple.

I want to be able to dump an entire "EAP" project file *AS IS* with "COMPLETE" information
(NOTHING must be stripped, such that it can be reimported back *AS IS*):

- diagrams
- schemas
- class information  
- class diagrams
- state machine
- activity diagram
- use cases
- package diagrams
- behavior code
- notes
- initial code
- relationships
- links, (X,Y)-(width,height) position of elements
- fonts being used
- curvature and bends into the association lines
- all attributes, operations, functions

Basically, everything into 1 BIG XML file,
even if it's 600 MB, I don't care, just gzip it if needed.

It does not have to be fast or even efficient,
it just have to work, even if it takes an hour
and it's crude, to import/export, that's fine with me.

AS LONG AS it is a "one to one" identical copy of the EAP binary file serialized into one BIG XML file.

I could explain in detail, why I need this, but to make it short "my fancy scripting needs is way ahead and too advance for what EAP currently offers", such that
I have to rely on exporting stuff that is tagged.
That is "so so" for now, but the remaining 20%
cannot be done without that XML export.

But I have no way of reimporting it back into Enterprise Architect, such that the project is always "in sync".

If any one knows a way of importing/exporting a complete EAP project using other tools... let me know.
Any open format or detailled format will do, XML is just one of them, any text format is preferred.