Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - MMI

Pages: [1]
1
General Board / C++ Generation Problems
« on: July 16, 2002, 03:57:22 am »
Hi,

I have tried re-generating our C++ code using version 499 of the tool. It seems that the pure virtual interface methods in interface classes are no longer generated? This was working with version 497. Any ideas???

Thanks,

Mike.

2
General Board / Directory structure during code generation
« on: February 07, 2002, 06:29:12 am »
EA allows you to generate code from a particular package starting point within the design hierarchy. However, the tool does not provide the ability to create code into a corresponding file directory structure. The only way to do this is to manually create the directories, and then to set the file generation path for each class. This is far from ideal, particularly when you have a lot of classes!

Can EA be modified such that you can define a code gen directory for a root package? Then, when you generate code for that package, the file system directory structure generated reflects the package nesting within EA.

Thanks,

Mike.

3
General Board / Documentation format control
« on: January 30, 2002, 07:31:24 am »
We use EA to generate documentation that is baselined (version controlled), and delivered to the customer. I am concerned that the structure of the generated document is currently dependent on the version of EA used. A year from now we may generate a new document, but the format could be completely different due to changes made to the EA RTF generator.

Is there any way of separating the RTF document format generated by EA from the version of EA being used, i.e. extend the current template concept to cover not only the content but also the layout and format of the generated document.

M

4
General Board / Code generation of association to Interface Class
« on: January 30, 2002, 07:02:36 am »
The C++ code generation for an association between a class and an interface class does not look correct to me. The C++ for the class correctly has a #include to the interface class. However, I would have expected the class to then contain an attribute that is a pointer to the interface class type, i.e. the code that is already generated by the tool for an association between a class and another non-interface class. This is the C++ that is generated by other UML tools.

Assuming that my understanding is correct, can this fix be added quite quickly to EA - we use interface classes a LOT within our system.

Thanks

M

5
General Board / Accessors for association attributes
« on: January 30, 2002, 07:12:04 am »
Can the EA tool be modified such that the C++ code generator can be configured to provide accessor methods for class associations, i.e. Set and Get methods to the class pointer used to represent an association.

In addition, when the association represents a one-to-many relationship, the C++ generated still only contains a single class pointer. I would have expected an array, or perhaps some sort of container class. Can EA not contain the relationships within an array, for example. The Get and Set methods could then be auto-generated with a parameter to represent the association number. Other UML tools manage to generate code for one-to-many relationships in this way.

The Options menu for attributes has a tick-box for "Generate Get/Set methods for associated attributes". Perhaps this is meant to be used for the above. However, it does not seem to impact the generated code at all.

Thanks,

M.

Pages: [1]