Messages

31

Automation Interface, Add-Ins and Tools / Re: TOGAF

« on: March 07, 2009, 03:38:46 am »

I understand the delay in the support of something like that, I'm just looking for a timeline.

To follow-up from the first post, TOGAF 9.0 was released Feb 2.

32

Automation Interface, Add-Ins and Tools / Re: TOGAF

« on: March 06, 2009, 07:48:27 am »

Bump. We are currently evaluating a multi-license purchase and are also interested in how soon the TOGAF support will be updated to match TOGAF 9.

33

Automation Interface, Add-Ins and Tools / Re: On the fly screen creation

« on: November 18, 2004, 02:20:33 pm »

Bump and +1 to enable add-ins to be able to identify the currently selected element or elements via the object model.

Repository.GetCurrentElements()

like the current method

Repository.GetCurrentDiagram()

34

Automation Interface, Add-Ins and Tools / Re: Trouble Getting AddIn Loaded

« on: October 06, 2003, 09:04:21 pm »

Yep, that did it.  I was at the wrong level.  I expected it to go under the EA360 key.

35

Automation Interface, Add-Ins and Tools / Trouble Getting AddIn Loaded

« on: October 03, 2003, 08:28:28 am »

I seem to be having trouble with getting my add-in loaded.  Is there a log that gets generated that might tell me where it is going wrong?

I noticed after I installed, there was a pre-existing add-in parent key: HKEY_CURRENT_USER\Software\Sparx Systems\AddIns.

The help specifies to put the user add-in key under HKEY_CURRENT_USER\Software\Sparx Systems\EAAddIns.

I've tried adding my key to both locations.  My add-in isn't even getting CoCreate'd which leads me to believe that the key isn't being recognized or read correctly.  And ideas?

36

Automation Interface, Add-Ins and Tools / Enforcing profile constraints

« on: January 19, 2004, 10:15:33 am »

I know that the UML profile schema allows you to specify constraints for profile elements, but is there a switch or something you can turn on in EA to enforce those constraints?  By enforcing, I mean, disallowing a relationship that isn't permissible according to the profile constraints, or maybe providing a warning when a constraint specifies that an element requires the existence of a relationship and/or other element that currently doesn't exist.

37

Automation Interface, Add-Ins and Tools / Re: .NET class library Exporter: Method to generat

« on: October 07, 2003, 08:42:05 am »

Check out:
http://home.wi.rr.com/skulkarni/COM/COM_Interop.html

Make sure to set 'Register for COM Interop' to True under Project Properties->Configuration Properties->Build.

Here's one I created that loads up:

[size=10]namespace EAAddIn
{
     [Guid("BC797ACA-E8F7-42e7-95CB-BF9832A3F91F"),
     ClassInterface(ClassInterfaceType.None)]
     public class EAAddIn : EAAddInTemplate.Addin
     {

           public EAAddIn()
           {
           }
     
           #region _Addin Members

           public void ShowHelp(string MenuName, string ItemName)
           {
                 // TODO:  Add EAAddIn.ShowHelp implementation
           }

           public void MenuClick(ref EA.Repository Repository, string MenuName, string ItemName)
           {
                 // TODO:  Add EAAddIn.MenuClick implementation
           }

           public object GetMenuItems(string MenuName)
           {
                 // TODO:  Add EAAddIn.GetMenuItems implementation
                 return null;
           }

           public void FileOpen(ref EA.Repository Repository)
           {
                 // TODO:  Add EAAddIn.FileOpen implementation
           }

           public void Connect(ref EA.Repository Repository)
           {
                 //System.Windows.Forms.MessageBox.Show( "TestAddin connected" );
           }

           #endregion
     }
}[/size]

A contribution area for uploads here would be really nice.

38

Automation Interface, Add-Ins and Tools / Re: XMI export - useless ?

« on: December 15, 2003, 07:53:21 am »

Something that has plagued XMI as a 'standard' since its inception is that it needs quotes around it, because despite being a 'standard', due to one reason or another (the openness of it, being one) support across tools has been less than perfect.

In my experience, Sparx has done everything possible to make EA as XMI-compliant as possible, and most problems I've had (Visio and Rose) have been because of lack of compliance by the other tools.

I don't know how much the politics play into it as well -- a standard is nice, but many companies probably don't want XMI to be a universal UML file format like the rest of us would like.

Try to determine the level of compliance with the tools you are having problems with, and if the problems are caused by those tools, put pressure on the tool makers to be more compliant.  If the problem is with EA, speak up here.  My personal opinion is that Sparx is committed to XMI and knows that a quality tool beats the pants of politics every day.

It's sad, but the UML community might have to take over the task of standardization by creating stylesheets that 'convert' Company A's XMI to Company B's XMI.

XMI, the UML 'standard'

39

Automation Interface, Add-Ins and Tools / Re: New Language Support

« on: September 30, 2003, 02:36:50 pm »

This seems like something that might be best implemented by adding .NET CodeDom support to EA.  CodeDom is Microsoft's strategy for language-neutral tools that allow people to create custom providers for different languages.