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

Pages: [1] 2
General Board / Re: XMI import problem
« on: October 23, 2018, 09:11:45 am »
Although the Microsoft support article doesn't mention it, I needed to restart Windows before the larger MaxLocksPerFile value seemed to take effect. Once I'd done that, all good. FWIW.

(I was getting those pesky DAO errors pasting a diagram.)

What's the best way to model, and explore within EA, a hierarchy of Solution Explorer filter folders from Visual Studio?

I need to model legacy code currently arranged in solution explorer folders, filesystem folders, and C++ namespaces. The three hierarchies are not orthogonal, but not isomorphic either. Anybody have a preferred modeling pattern/practice for this?

What I've been doing is manually creating a package structure that aspires to somehow unify the C++ namespaces and solution explorer folders. C++ namespaces have packages, and if pretty much isomorphic to a solution explorer folder, I use the latter as a package alias. For a solution explorer folder not isomorphic to a C++ namespace, I make it its own package but set "Suppress Namespace". Then I import whatever C++ headers are assign to a solution explorer folder within whatever model package represents that folder (either as itself or as a C++ namespace alias). In this manner I get a model that is somewhat useful as a starting point, but only that. I generally have to manually fix various relationships, because the solution explorer folders are just this fiction not actually represented in the C++ source code that was imported.

For policy and/or institutional cultural reasons, C++ namespaces are pretty coarse-grained and historically not really encouraged. Likewise with source filesystem folders. Whether I had EA's importer assign a package per C++ namespace or per filesystem folder, either way if I just ignored the solution explorer folders entirely, the model package hierarchy would be overly flat, with enormous packages serving as dumping grounds for hundreds of elements.

For better or worse, the VS folder hierarchy does embody much of the design. Round-tripping isn't needed at this time, but being able to re-sync the model to updated source code would be great.

Any suggestions? Thanks for reading.

Suggestions and Requests / hide specific return types
« on: May 14, 2016, 07:37:35 am »
Diagram properties -> Features -> Feature Options -> Show Operation Return Type

This really wants a subordinate property to hide specific operation return types. For example, the types 'void' for Java/C#/C++ and 'nil' for Lua. As return types, they're usually just diagram noise.

Suggestions and Requests / import utility functions in C++ namespaces
« on: March 25, 2016, 05:57:44 am »
I wish EA had a C++ import option to treat namespaces declaring non-class functions as <<utility>> classes with static methods. Rather than not importing them at all. These are often functions that I'd like to include on sequence diagrams and drill down to model their behavior.

Or maybe leave the namespace a namespace, and instead create a class named "<anonymous>" to hold static method declarations, as is already done for anonymous enumerations.

I've been informed by Sparx that MDG Integration is still in active development, and the latest version is undergoing testing. Which reassurance is all that was really expected, pending a final release. Every little bit of transparency is much appreciated.


OK then, thanks for redirecting me in a more productive direction. A FAQ/sticky would have been useful, and I did actually look for one. Pending information directly from Sparx, the most value I can contribute here is probably this.


I did that, back in May, and was pleased to receive a thoughtful response indicating that the product was still in beta and held up because of a few issues. It sounded like it was still in active development. That was about four months after the beta 1 announcement, and since another four months have now passed it seemed reasonable to rattle somebody's cage again.

Also, since as noted at the top of this thread I'm not the only one interested, I thought a more widely disseminated response would be helpful to others. But it's not my place to forward any private email response from Sparx to this forum.

(And if I'm really asking other users here, I'm a bit mystified as to the point of this particular forum, "Suggestions and Requests". Is the idea that users can post suggestions and requests for other users to implement as 3rd-party add-ons?)

Anyway, Roy, thanks for your reply.


Suggestions and Requests / status update please re. MDG Integration for VS
« on: September 17, 2009, 04:24:56 am »
Don't you think maybe it's about time for some official announcement re. MDG Integration for Visual Studio? Almost eight months is an extraordinarily long time between beta and either a subsequent beta or an official release. Particularly for Sparx, which has such a history of frequent updates.

What are Sparx's intentions for this product? Is it considered to be at its end of life and no longer under active development?

Ref.  MDG Integration for Visual Studio v4.0, Beta 1, Jan 29th, 2009; and also I'm not the only one asking.

Best regards,

I understand. Fortunately it's not too frequent a user operation, and the version control system not handling large commits is of course something that must be overcome somehow. That notwithstanding, and just so you know what the user experience can be like, recently I put a model structure in Perforce that resulted in 305 changelists, and tediously had to confirm in the changelist comment dialog for each one of those 305. Maybe there's a happy middle ground, say batching changelists based on some reasonable data size. Or maybe interface a little more directly with Perforce such that changelist submission is entirely automated.


When using Add Branch to Version Control on a nested package hierarchy, EA submits each package in a separate Perforce changelist. One. At. A. Time. Trying to workaround by saving to a numbered changelist (that is, a non-default changelist) fails to add the package to Perforce. Submitting all the package XMI files as a single changelist would be much more convenient, particularly when writing a single changelist description to be used for all of the packages.


Suggestions and Requests / Re: single EA icon in alt-tab task switcher
« on: October 26, 2007, 01:10:42 pm »
(EA 7.0 build 817)

This information might be useful:

 "Which windows appear in the Alt+Tab list?"


Suggestions and Requests / single EA icon in alt-tab task switcher
« on: January 09, 2007, 05:41:13 pm »
(EA 6.5 build 802)

Currently the alt-tab task switcher on Windows shows a separate icon for every floating EA window. It would be much more convenient if EA would show up as a single icon in the task switcher, so I don't have to alt-tab-tab-tab-tab-tab-tab to switch to the next most recent app.


Suggestions and Requests / EABase_JET4.eap
« on: January 23, 2006, 01:10:53 pm »
From another thread in the General forum,

Re: new project in ea 6.1
You can no longer select which file will be the used as the base model for new projects - it is now always EABase.eap (found in the EA dir).  You can replace this file with your preferred base model.  
The Sparx Team

It would be helpful if EABase_JET4.eap were included in the EA full installation package, and selecting

   Tools -> Options -> General -> Use JET 4.0

would cause new models to start from EABase_JET4.eap instead of EABase.eap.


Suggestions and Requests / UI inconsistency re. multiple stereotypes
« on: November 02, 2006, 06:19:39 pm »
The EA 6.5.799 UI allows specification of multiple stereotypes for class attributes via the "..." button next to the stereotype drop-down list, but no such button is displayed for «table» columns.

Likewise for class operations vs. «table» constraint operations.

General Board / Re: MDG Integration
« on: June 11, 2014, 04:00:18 am »
Any status update re. Visual Studio 2013? Or even re. VS 2012 being ready for production use rather than a 10-month-old beta?

Pages: [1] 2