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.

Messages - Simon M

Pages: 1 ... 411 412 [413] 414 415 ... 417
You shouldn't be able to include anything between the tags.

It outputs the contents of that elements linked document into the file.  For more information please see

There wasn't, but what are you wanting to do with it?

No it's not.

I think what is happening here is the one of your packages (Domain Model) has spaces in the name.  EA tries to find a namespace "Domain Model" and can't.  So it generates the corresponding code for it.

The CONVERT_NAME and related functions are all there for transformation templates, not code templates.  In code generation the name needs to match between the model and code.  If you want to do something like this you'll have to write a transformation to convert the names for you.

Automation Interface, Add-Ins and Tools / Re: Add connector to diagram
« on: November 20, 2005, 01:26:27 pm »
Excuse me, that's how you spell "Realisation" ... unless you're American !

I agree.  Unfortunately I believe the UML spec was written in American English.

As I said previously, there isn't any direct access to the attributes at the other end of a connector.  The closest that you can come to that is the following.

Code: [Select]

%if connectorDestElemMultiplicity=="1" or connectorDestElemMultiplicity=="0..1" or connectorDestAggregation == 2%
           <component name="%connectorDestRole%" class="%connectorDestElemName%">
      <one-to-one access="field" name="%connectorDestRole%" column="%connectorDestRole%" class="%connectorDestElemName%" />

Note that I also modified your if condition to handle your multiplicity constraint.  The ordering of the expression is important because and/or precedence isn't handled.

1) Not really any supported way at the moment.  You can work around the issue by setting the default extension for C++ (because that appears to be your default language) to .xml instead of .h.

2) Unfortunately there isn't currently any support for getting tagged values from connectors.  So again you would need to make an addin call using EXEC_ADD_IN to get them.

3) classBaseName won't be defined outside of a ClassBase template.  So you'll need to add a %list="ClassBase" @separator=", "% and %list="ClassInterface" @separator=", "% if you need interfaces too.  Then you'll need to define a template for Class Base, Class Interface, Linked Class Base and Linked Class Interface.  If you actually have the link/Generalization then you'll need to use %linkParentName% in the LinkedClassBase template.

Hi Casper,

1) Currently the only way to do list over base class contents is to use an addin call witin the template.  I'd recommend adding a list over all generalization connectors and making a call using the opposite end to your current class.

The following may help.

Code: [Select]
%if classGUID==connectorSourceElemGUID%$guid=%connectorDestElemGUID%

2) a. Tagged values on the class accessed with %classTag:"tagName"%
b. Stereotyped attributes/operations, then add stereotype override template.  Lists can then have a condition on the stereotype.

3) Tools | Export Referenece Data.  Select nHibernate_Code_Template

If you are allowed to share them, you could upload them onto

Automation Interface, Add-Ins and Tools / Re: XMI tag documetation
« on: October 27, 2005, 04:16:21 pm »
I don't know the exact answer, but that string appears to be specifying how a connector is drawn on a diagram in EA.

It may be used for some diagram interchange, in that case it's probably documented somewhere, otherwise it won't be.

Automation Interface, Add-Ins and Tools / Re: Auto Counters
« on: October 25, 2005, 05:04:48 pm »
The t_trxtypes table.

Automation Interface, Add-Ins and Tools / Re: Auto Counters
« on: October 25, 2005, 04:49:10 pm »
It definately saves the auto counter to the database, and in a quick test between two users here it just worked.  So I'm not sure what the problem would be.

Automation Interface, Add-Ins and Tools / Re: Generate code from Screens
« on: October 23, 2005, 04:30:40 pm »
Hi Thomas,

I haven't tried much, but I briefly modified the C# transformation to force everything to become classes and UI controls were transformed.

Try something like this in your class template.

%if elemType == "Screen"%
$comment="This is a cut down example of what a transformed screen should look like"
%list="InnerClass" @separator="\n" @indent="  "%
%elseIf elemType=="GUIElement"%
$comment="This is a cut down example of what a transformed ui control should look like"
%list="InnerClass" @separator="\n" @indent="  "%

Automation Interface, Add-Ins and Tools / Re: invisible add-ins
« on: October 12, 2005, 03:15:13 pm »
I have seen a problem with this before.  What I saw could be fixed by resetting your menu.  (Tools | Customize | Menu | Reset)

Automation Interface, Add-Ins and Tools / Re: Code Generation
« on: March 15, 2005, 08:21:32 pm »
I just had a brief look at it.  I don't know ColdFusion, but it looks pretty good.

You could also consider putting it on the EA User Group website.  (May want to see if a new category for MDG Technologies can be added)


Automation Interface, Add-Ins and Tools / Re: Code Generation
« on: February 15, 2005, 08:02:03 pm »
Officially you can't...  :'(

Unofficially you can import an MDG technology file that looks a bit like this.

Code: [Select]
<MDG.Technology version="1.0">
<Documentation id="YourLanguage" name="YourLanguage" version="1" notes="Sets the default extension for your language"/>
 <CodeModule language="YourLanguage" notes="">
   <CodeOption name="DefaultExtention">.extension</CodeOption>

You could also use the technology wizard to create a file containing all the datatypes and code templates to include this in.  Then you will have a complete distribution file for your new language.


EDIT: The version can't be an empty string.

Pages: 1 ... 411 412 [413] 414 415 ... 417