Messages

1

Suggestions and Requests / Linked document also in generated HTML docs

« on: January 30, 2006, 01:52:24 am »

Hi,

I know this is a difficult request, but it would be nice if the contents of the "linked document" (right-click an element, select "Linked Document" in the context menu) is also exported to the HTML documentation (as it is by the RTF Generator).

Of course, including the images contained in these linked documents...

Any chance to see this feature in EA at some time? It would be very nice for us becasue we use these "linked documents" e.g. for attaching a screenshot of a screen design to a requirement.

Best regards,
Markus

2

Suggestions and Requests / Specify default color of UML profile elements

« on: February 17, 2006, 02:39:27 am »

Hi!

I'd like to be able to specify the default color for elements of an UML profile. Example: I'd like that all object with the stereotype <<orangeobject>> are displayed in orange when they are created from my UML profile.

I exported my profile preparation package as UML profile (in XML). I noticed these "bgcolor="-1"" attributes, and manually edited them before importing the file as UML profile, and voilà - all <<orangeobjects>> created from this profile appear in the color I specified!! So basically this feature exists!!

Unfortunately, I always have to edit the XML file manually - I could not find a way to have "bcgolor="<my desired color>"" in an exported UML profile.

Would be very nice to have this.

Best regards,
Egon Schneider

3

Suggestions and Requests / Re: Note in Diagram which display element descript

« on: January 31, 2006, 11:36:59 am »

Thanks! Works great!

4

Suggestions and Requests / Note in Diagram which display element description

« on: January 26, 2006, 07:26:06 am »

It would be very helpful sometimes if (in a diagram) I could add a note to an element which automatically displays its description instead of entered text.

This would enable me to use the same content for both the diagram and the generated documentation (and I don't have to remember updating both of it in case of a change).

5

Suggestions and Requests / Filter tagged values in documentation

« on: January 30, 2006, 01:46:53 am »

Hi,

it would be nice if one could filter the tagged values that are written to the RTF documentation (and maybe to HTML as well).

Example: I'd like to see the "readonly" tagged value (or some other user-defined one), but not the "ea_guid" tagged value.

If I get it right, this is not possible today.

Best regards,
Egon Schneider

6

Suggestions and Requests / Generate DDL for different databases

« on: January 04, 2006, 04:47:44 am »

Hi *,

we are building a system that supports different databases (MySQL, Oracle, SQL Server).

We'd like to manage the Data Model with EA. Unfortunately, you have to specify the target Database Type per table, so we cannot generate the DDL for all three databases from the same model (which would be nice!).

EA supports generating Database-dependent generation of DDL anyway - why not let the user choose the target database in the "Generate DDL" dialog (which then overrides the per-table setting)?

Best regards,
Egon Schneider

7

General Board / ea_guid tagged value

« on: July 22, 2005, 12:30:45 am »

Hi *,

i just generated rtf / html documentation from my model and found out that some of my methods have a tagged value "ea_guid" (probably set to some internal identifier for that method).
Are these tagged values necessary or can I safely delete them? If they are needed, why not for all methods?

Reason is that I don't want them in my documentation, but need other tagged values (so I cannot switch them of in my templates generally).

If they are needed, maybe they should be filtered out when generating documentation (this is a feature wish!)

Apart from that, EA is great!

Best regards,
Egon Schneider

8

General Board / Full namespace in diagrams

« on: May 12, 2005, 11:15:52 pm »

Hello,

you can set a package to be "namespace root". Sub-Packages automatically become sub-namespaces. This works quite well, especially when generating code (c#, in my case).

# MyPackage (package, namespace root)
 # Level1Name (package)
   # Level2Name (package)
       MyClass   (class)

In the generated code, the namespace of MyClass is set to Level1Name.Level2Name. Thus, the full name of this class is Level1Name.Level2Name.MyClass

Is it possible to display this name in the diagrams? When I add MyClass as a simple link to a diagram in another packe, currently, it only displays:

Level2Name::MyClass

I'd like to have something like

Level1Name::Level2Name::MyClass

This would help a lot in larger projects, especially when there are multiple classes with the same name.
Is there any way to achieve this?

Best regards.

9

General Board / Readonly properties in an interface (C#) ???

« on: March 22, 2005, 04:59:00 am »

Hello *,

currently I am desperately trying to design a readonly property in a c# interface. "Readonly" means: The property shall have a getter, but no setter.

A code example would be:

Code: [Select]


namespace MyNamespace {

public interface MyInterface {



void MyProperty {



get;


}

}//end MyInterface

}//end namespace MyNamespace


How do I do this in EA? This is what I found out:

1.) You can design it as an operation with the "property" stereotype. In this case, I cannot specifiy whether it is readonly or not (by default, a getter and a setter is generated). If create a .cs file, remove the setter manually and synchronize with the model, EA seems to notice it, and when I generate code again (even to another location), no setter is created. So it works! But this is quite complicated and I cannot see in EA whether the property is RO or RW.

2.) I can design it as an attribute and check the "property" checkbox. In this case, I can specify whether it it should have a setter and/or a getter. But then,  I have both an attribute and a property (=an operation with "property" stereotype), which is not what I want in an interface. I also cannot delete the attribute afterwards, because then the property is also deleted.

Any ideas on how to create an RO property without hassle? What is the recommended way?

Thanks in advance.
Egon Schneider