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 - Oliver F.

Pages: 1 ... 35 36 [37] 38 39
Automation Interface, Add-Ins and Tools / Re: RTF templates and MDG
« on: October 23, 2008, 09:54:42 pm »
Not that I know of. Templates are exchanged via the reference document export mechanism which is separate from MDG technologies.

However if you have a shared model then templates are accessable from anybody using the same model.


I am a bit concerned about the XMI and EAP situation.

I suggest you read the latest EA build (833, which came out in the past 24 hours) release notes on the history page to see if this has been addressed.

If not, and following a test with Build 833 just to be sure the bug persists, please report this to Sparx using the Report a Bug link on any forum page. Remember to tell them that you are using the Java API, as this bug might only occur there.

Michael told me that such issues had been addressed in 833 and at least for CreateBaseline I can confirm the issue is fixed without being mentioned in the docs.
Obviously in the reference doc there was a mixture of guid and xmlguid where only xmlguid was valid.
I am not going to say that there are no further issues of that kind but fingers are crossed.


Automation Interface, Add-Ins and Tools / Re: Automate export of XMI
« on: October 17, 2008, 07:04:48 pm »

A little respect here, please...   :-X


No, you can' t have it

That quote and the sig make a good combination :)

Besides that I get the feeling of having been misunderstood, but maybe this is caused by the language barrier. Take my apologies uin that case.


Automation Interface, Add-Ins and Tools / Re: Automate export of XMI
« on: October 17, 2008, 12:49:04 am »

The important thing here is that you've found something to fill the empty hours.   ;D

Propably those hours of time shift between Canada and Europe- you guys wake up too late :)


Automation Interface, Add-Ins and Tools / Re: Automate export of XMI
« on: October 16, 2008, 07:40:48 pm »
Sorry about that all - and even more so to Culpers.

Frank and Oliver are completely correct of course. [Not to suggest that we would expect otherwise.   ;) ]

I have waited for long on that occasion- proving that David is wrong and slap him on the back for this  ;D
It took quite a while and dozens of excellent posts have past until I finally found one- strike :D


P.S.: Just kidding ;)

Automation Interface, Add-Ins and Tools / Re: Automate export of XMI
« on: October 15, 2008, 08:52:22 pm »
No, not as yet.

Why not? You can make a command line application with anything that understands COM, create a new EA.Repository, open a project with its OpenFile method and then iterate through the packages and export e.g. the ones with names matching command line parameters.

Just did something similar and added it via the Tools menu to EA.
The JAVA program gets its input package guid as a parameter via main(arg0) and then processes it.
It works the same way from the command line. The only challenge is to get the input package GUID to be pasted as command line parameter which is a bit cumbersome. Called from EA it can be automatically set from the item selected. Make sure to check in your program whether the input GUID is really a package to avoid surprises.

It is very straightforward. The JAVA API is nothing but a wrapper for the COM API so it works the same way with C++, C# and any other wrapper available.


Automation Interface, Add-Ins and Tools / Re: Outputting Multiple Models
« on: October 17, 2008, 12:54:09 am »
Similar issue here.
I have a JAVA deamon, which runs every 24 hours. Then it sets baselines for some packages and afterwards tries to export the model to HTML.

Sometimes it works, sometimes not. Baselining is ok, HTML export regularly stops without notice. I have a tray icon set up with a menu which lets me manually trigger the export and it perfectly works then.

However HTMLExport has proven to be very unreliable.


The EA User Guide (at states that users can "View Tagged Values inherited from parent Classes or realized interfaces or applied stereotypes", override them and delete them, but what is the use if not accessible using the macros.  Am I missing something?

Inherited tags will only be part of that element, if you override them.
I assume that the inheritance takes place in the EA GUI layer only so they are not part of the model element unless you apply overriding on them.
The automation interface accesses the model information only, not what is visible in a dialog so in that case you will not be able to benefit from the inheritance mechanism.

A workaround would be to gather the realize link of the elements and explicitely get the tags from the parent element.

Maybe someone can prove me wrong here but I believe this is the way it goes.


About an hour later I get a call from one stakeholder saying its not very easy to add comments becasue as soon as he highlights the required bit he want to comment on the whole document gets highlighted and the comment ends up at the bottom of the document.

Try to set the "Overwrite document fields" checkbox when generating the document. This will not generate fields in the document but plain text which I believe is the annoying part here.


Automation Interface, Add-Ins and Tools / Re: User group in Switzerland?
« on: September 25, 2008, 07:45:25 pm »
We (SIS in Olten) are looking at using EA across our applications (waterfall and UML) for documentation as well as development. The organisation of projects, packages and use of Version Control could well be critical and my goal was mainly to find and contact other people in Switzerland administering EA to share their experiences and recommendations.

John, I believe this is not only a swiss problem, but a world wide one :)

If you have specific questions we can discuss them here or point you to the best fitting literature.

BTW, I don´t mind if you post your contact data here but be aware that Google is also indexing this forum, so this is the best way to become a personal spam colloctor ;)


Automation Interface, Add-Ins and Tools / Re: User group in Switzerland?
« on: September 25, 2008, 12:45:18 am »
AFAIK there is none but I wondered why we would want to start one.

IMHO the EA forum here is the largest UG in the world and you can get all help you want from here.

Forgive me of saying this but I have always doubted the usefulness of user groups because I have experienced dozens of groups for a certain topic each with its own web site and information separated from each other.

However you might have some good reasons to ask for it I have not taken into account, in that case I´d be rather interested to hear them.

BTW, what's your location in CH ?


Hi Coen,

Sorry forgot to mention... the protocol handler will be free.

There's a link on the Canonic Labs page you can use to request the beta version when it's available.

Done ;)

This is terrific. Any time frame you could give us as a teaser?


You can set the size of stereotyped ports to something other than the 16x16 default, and you need to be aware of that if you are checking the "Element Size" option on the Save as UML Profile dialog. In that case, give the stereotype element the attributes: _sizeX=16 and _sizeY=16.

OK, thanks for pointing this out.

However if I set something different for eg. an ExposedInterface than the standard values the EA layout engine gets highly confused by making the element jump around rather unmotivated in the diagram instead of smothly move along the edges.


Hi all.

Just to let you know and before people fall into the same pit...

When creating UML profile one is able to "override" the ExposedInterface and Port elements by creating the corresponding metaclasses and  extended stereotypes.

If you do this and export the profile make sure not to check the "Element size" option to include the element sizes in the profile.
If you do this EA will get confused about the display and dragging size because it does not expect size information for non-resizable elements like ports and ExposedInterfaces.
It will lead to very strange effects in the diagrams.

Just to let you know, I have not decided yet whether it should be considered to be a bug or not.


Automation Interface, Add-Ins and Tools / Re: RTF report
« on: July 24, 2008, 09:59:29 pm »
There is no direct filtering on the sub-element level of the RTF report generation. If you want to filter at this level it may be best to look into creating a query in the Advanced Search (ctrl-F).

To round this up, as I believe it only partially solves the issue: You can create an advanced search filtering for basic paths.
Then you can assign this search criteria to model document as part of a complex document when generating documentation.
Meaning: You set several "chapters" by defining model documents made of either pacakges or aearch criteria (or both, though I am not sure about combing both). One chapter might be the result of the search rule extracting only the basic paths from your model.

I hope this helps.


Pages: 1 ... 35 36 [37] 38 39