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 - Sunshine

Pages: 1 ... 32 33 [34] 35
If you have no luck getting the original EA model you could reverse engineer the UML profile into a model then extend it and save the new profile. The options here are;

a) Manually recreate the profile model in EA.
b) Use XSL transformation to create the stereotype, toolboxes etc into XMI file and import back into EA.

I was thinking of doing a similar thing with Archimate profile to extend it with the proposed ARMOR extensions that cover motivation, project and programme migration. I just haven't motivated myself to do it yet  ;D

Automation Interface, Add-Ins and Tools / Re: Alternate image in MDG
« on: July 28, 2010, 09:34:31 am »
Just to clarify something about using images in shapescripts mentioned in the previous post, incase like me you thought you could get away with just one MDG Technology file. You still need to import the images into the model otherwise it doesn't work even though you can export the images into the MDG Technology file.   :(

If you don't you end up with a grey box indicating its referencing an image that doesn't exist in the model.

Here is the description of using the image() function from the help
Draws the image that has the name imageId in the Image Manager.

The image must exist within the model in which the stereotype is used. If it does not already exist in the model, you must import it as reference data.

Automation Interface, Add-Ins and Tools / Re: Alternate image in MDG
« on: July 13, 2010, 07:17:37 am »
Sparx Systems have come back to me regarding the images in MDG. Here is their response with suggested work around;

Thanks for your note.

There are two ways to deploy a technology:
1. Model-based deployment (import into Resources view) imports images but you can't use a number of features of technologies including custom toolboxes.

2. File-based deployment (using the Settings > MDG Technologies command) doesn't import images.

We do not recommend using both deployment methods simultaneously as the imported resources (e.g. stereotype definitions) will interfere with the external resources.

The better solution is to export images as reference data (Tools > Export Reference Data) and import the reference data into the target databases, and use the file-based deployment of the technology.  You may also consider applying the images using a shape script:

shape main

      shape name

See the "Shape Scripts" topic in EA help for details.

I hope that helps.  If you have further questions or issues please let us know.

So it looks like my work around of deploying two different ways is not recommend. It doesn't look like they are going to fix the problem either. :(

Automation Interface, Add-Ins and Tools / Re: Alternate image in MDG
« on: July 02, 2010, 07:23:10 am »
Okay after a few days of trying different things to get alternative images to work from a stereo type in a profile. I've exhausted various options and the only things that seems to work is as described in my previous post. So I decided to raise the alternative images behaviour in profiles as a bug with Sparx Systems and see if they can fix it so you only have to deploy the MDG file once.

Automation Interface, Add-Ins and Tools / Re: Alternate image in MDG
« on: June 29, 2010, 10:04:09 am »
I've recently had the opportunity to create another profile using images. One of the things I've found is that there are two ways to deploy the technology xml file created by the tools>generate MDG Technology file menu.
a) copy the file to C:\Program Files\Sparx Systems\EA\MDGTechnologies and restart EA.
b) Import the technology file via resources>MDG Technologies.

Thinking back a few years now it was option b) I used to get alternative images working.

With option a) the toolbox associated with the new diagram type works but the images don't seem to show.
However with option b) the images show but the toolbox doesn't work.

Don't you love it. :-?

My workaround is to use both approaches so the images work with the toolbox. Alternatively you can reference the image in a shape script. I confess I haven't gone down that path as I have 78 stereotype and don't what to write 78 shapescripts.

Automation Interface, Add-Ins and Tools / Re: Alternate image in MDG
« on: April 30, 2010, 01:36:13 pm »
As far as I know there are two approaches to applying alternative images to stereotypes.
a) Use shape script as mention in previous lists.
b) apply the alternative image to the stereo type on the profile diagram.

I think you are after the easiest option which is option b)
On your profile diagram where you inherit from an existing meta class you need apply the alternative image (ctrl+shft+w) to the new stereotype you are creating. Then when you save as profile ensure you have the alternative image tick box selected.

I've used both techniques on past versions of EA. Although haven't tried it with V7.5 or 8.0.

To draw original shape use with a decorator on top you probably want to do something like this

Code: [Select]
decoration star
   // insert drawing code here...

shape main

Look at orientation in the help under shape attributes to position the decoration in NW, N, NE, E, S, SW ow W within in the containing element glyph.

If you want to see examples load the archimate mdg file located in the folder C:\Program Files\Sparx Systems\EA\MDGTechnologies into a model so you can see the shape scripts associated with the stereotypes.

Hope that helps.

Automation Interface, Add-Ins and Tools / Re: DBMS -> EAP
« on: November 16, 2010, 05:30:40 pm »
It's easy inside of EA but don't want to do it that way.
Preferably by the API

You haven't explained why you want to use an alternative way to that is provided by EA so not sure of the motivation here. However you can try using one of the many ETL tools available such as powercentre or SAS data integration studio if you can afford it.

Alternatively if you are just looking for ways to inflict pain on yourself put the crown jewels on the table and hit each one with a hammer  :) (Joke)

If you use MS SQL Server as the repository you can use SQL Server Reporting Services (SSRS) for free. Crystal reports usually costs extra dosh $.
To get the numbering working properly you need to set up a base template with all the numbering styles sorted. i.e. Header 1, Header 2 etc to get;
1. Header
1.1 Sub header
1.1.1 sub-sub header
Then use the base template in all the EA templates you create so the numbers flow.
It will be the same for other types of numbering such as lists.
Having used both SSRS and CR in the past I'd prefer SSRS. Mind you I have spent a lot of hours getting reports working in EA and have managed to use the EA native report generator for just about all the documents I need.

On the crashing side of things may I suggest you send in a bug report and provide the model to Sparx so they can make EA more stable.  :)

The secret to getting heading level numbering working is to use a base template with the header numbering in it. For instance I found it easier to create a MS Word template with Header 1, Header 2 etc then import it as a base template. Use that base template for all the parts of the document and the numbering will flow consistently. I originally tried to do this in the RTF editor in EA but wasted days trying to get to work.

I understand what you are trying to do as I've used both methods in the past so you can use either one of those approaches. The trick with the "document artifact>linked document attached" method is to ensure that the template you use for the master document has following box tick in the sections explorer of the template. Package>Element>Linked Document. Once that has been ticked it will include the contents of the text of the document artifact>linked document. Cool eh?  8-)

Automation Interface, Add-Ins and Tools / Re: Clean HTML report template
« on: October 05, 2010, 06:38:17 pm »
You haven't mentioned what programming language you are trying to document but it sounds like you'd be better off using something equivalent to javadoc or ndoc (in .net world) as these were specifically designed for such a purpose.

I had a similar problem, it turned out that I'd mistyped the stereotype name in the toolbox so perhaps just double check there is no typos.
Hang in there sounds like you've nearly cracked it. :)

Think you'll find you have some degree of customisation of the information as well as the style. I concur its not as flexible as one would like. There are some tags such as #NAME# and #TYPE# that can be added/removed.
See the following url for more info on the tags that you can use;

I'm afraid that's the degree of customization available with EA at present.

If you want more flexibility then the other alternative is to consider creating your own HTML generator using the automation interface. If you don't have MS visual studio then you can download one of the express editions from Microsoft. Its not hard just a little more time consuming than one would like.

Pages: 1 ... 32 33 [34] 35