Messages

1

General Board / Re: running EA with parameters

« on: May 19, 2008, 05:04:20 pm »

Does anybody know?

2

General Board / Re: running EA with parameters

« on: May 13, 2008, 08:19:31 pm »

Is this still the case? That you can't start EA with parameters?

/N

3

General Board / Re: Problems with UML profiles from MDG Technology

« on: May 05, 2008, 08:35:09 pm »

Why isn't the stereotypes from the MDG Technology visible under Settings-UML. Am I doing something the wrong way?

/N

As I understand, the stereotypes you create under Settings -> UML are stored separately from any profiles you import.  In other words, if you import a profile - it "hides" the stereotype and its behaviour under Settings -> UML.

I reecommend you avoid touching Settings -> UML and focus just on getting the MDG / profile to work.  Sorry I can't help you onthat, other than Settings -> UML will just confuse things.

I presume you are regenerating the MDG through the EA wizard?  If so - I think all you need to do is plonk it into the MDGTechnologies folder (as you are doing) then restart EA to reload the changes.

David.

The big problem is that the color is not right on "old" elements in the project with the same stereotype as in the MDG Tech. When I create new elements with the stereotype, then the color is right.

/N

4

General Board / Re: Problems with UML profiles from MDG Technology

« on: April 29, 2008, 10:22:35 pm »

I have placed it in the MDGTechnologies folder. I'm running build 828.

/N

5

General Board / Problems with UML profiles from MDG Technology

« on: April 29, 2008, 06:25:19 pm »

Hi!

I'm using a MDG Technology that contains several profiles with stereotypes. When I create a new element with a stereotype from the MDG Technology it is created with the color set in the profile. But when I change the stereotype on an existing element then the color is not changed.

In the menu Settings->UML I can't see the stereotypes from the MDG Technology. I have to add the profiles from the profile packages that I used to create the Technology. Then I can see them under Settings->UML, but the stereotype doesn't have the right color. I have to manually set it, and then the stereotype is working as it should in the project.

Why isn't the stereotypes from the MDG Technology visible under Settings-UML. Am I doing something the wrong way?

/N

6

General Board / Re: How to structure huge EA project?

« on: April 21, 2008, 08:13:35 pm »

You can add configure version controll on packages, not just to the entire project. This way a dev can check out just the packages he needs to work in.

/N

7

General Board / Re: Auto-genrating sequence diagrams

« on: April 29, 2008, 06:30:13 pm »

I have only been creating sequence diagrams from add-ins. So I'm not able to help you.

/N

8

General Board / Re: Auto-genrating sequence diagrams

« on: April 28, 2008, 11:33:36 pm »

Hi,

I have succesfully generated sequence diagrams in 7.1.828. How are you generating the diagrams? I don't have enough information to be able to help you.

/N

9

General Board / Re: Adding Model Templates to A MTS file

« on: April 22, 2008, 12:13:57 am »

I have now added a model template. I added the template in the mts file in the same way you do with Toolboxes or Modelsearches.

I added the <ModelTemplates> tag to the mts file just before the </MDG.Selections> line. And it worked!

/N

10

General Board / Re: Adding Model Templates to A MTS file

« on: April 21, 2008, 08:24:53 pm »

The <MDG.Technology> block exists in the technology xml file. I would test to paste it into the xml file and see if that works.

/N

11

General Board / Re: Toolbox Profiles

« on: April 14, 2008, 11:14:55 pm »

I have found the problem. Only one technology can be active, and my technology was not. After I made it active it works.

/N

12

General Board / Re: Toolbox Profiles

« on: April 14, 2008, 10:33:15 pm »

This was certainly part of the problem.  Using the diagram "save as profile",  and with the diagram notes set to

RedefinedToolbox=Extended::Requirements;Alias=nnnnnn;Notes=yyyyyy;

I now get the following in the XML file

<Options>
   <Option name="RedefinedToolbox" value="Extended::Requirements"/>
</Options>

which looks promising.  However,  this doesn't seem to have any effect - the technology gets loaded fine automatically at EA start up and is the active technology.  I can use the profiles/toolboxes, and pin them to the main toolbox but still don't seem to get this toolbox displayed automatically if I open a requirements diagram.   So what else am I doing wrong ?

I did get a reply from Sparx Support along the same lines and have replied with this info and the XML file.

Graham

I have the same problem. I have the options tag with redefinedtoolbox in my MDG file. But it don't work. If I do the same in a profile then it works. Is this a bug?

/N

13

General Board / Set options for project

« on: April 07, 2008, 04:54:05 pm »

Hi!

We want all the users working on the same project to have the same settings in EA options. Is there a way to tie the options to a project?

/N

14

General Board / Verifying model against well-formedness OCL constr

« on: April 04, 2008, 05:41:36 pm »

Hi!

We want to verify our model with ocl constraints. Is it possible to write the rules in a textfile and use it for the entire model. I know that you can add OCL constraints to elements, but it would be much easier to manage one file for the entire model.

/N

15

General Board / Re: Handling several branches

« on: March 13, 2008, 02:26:14 am »

I have been testing this today:

Each branch is a EAP file. To create a new branch I copy the model I want to branch and rename it with a name containing the branch version(v2). I then open it and create a baseline named with the version of the branch(v2.0). When I want to merge the branch back to another branch(v1) I create a new baseline in this branch(v2.1).

I then open the other EAP file with the other branch (v1). Create a baseline (v1.4) to save the model before the merge. Then I open the "Manage baselines" and use the "Load Other Baselines" and open the v2 file. I select the baseline v2.1 and use "Show differences". Now I can select what I want to merge to the v1 file.

You can merge from "Show differences" even if the packages are version controlled and not checked out. But the result is not good, not everything is merged. I think you should checkout all packages before you try to merge. Then it seems to work well.

"Check In branch" is good when you whant to check in after the merge. But is no help when you want to check out all packages. I wrote a plugin that checks out a package and all its child packages.

/N