Messages

1

Suggestions and Requests / Re: Support Doxygen Comments

« on: December 23, 2008, 01:55:36 am »

count me in as a longtime Doxygen fan!

2

Suggestions and Requests / XAML Import?

« on: December 23, 2008, 02:04:37 am »

A quick search of the forums revealed no mention of XAML as an import format. However, with WPF as of .Net 3.5 sp1 and Visual Studio 2008, the declarative coupling in XAML is becoming a more important part of the object model.

Is there interest in discussing how this might be used to add to an EA model? Maybe it can be an add-on using automation, rather than pushing Sparx to include it as an import language?

(Happy to be back as an EA user after a year or so absence but now I'm doing WPF instead of geospatial schemas, just can't escape that XML!).

Andy

3

Suggestions and Requests / Re: Show Parent Attributes & Operations

« on: October 21, 2004, 02:11:40 am »

Thanks for the prompt reply (we're in Perth) but what EA currently provides is complementary to the MagicDraw feature.

I've put a screenshot up to help explain, on
http://www.oofile.com.au/files/misc/MagicDraw-inheritedAtts.png for the MagicDraw behaviour - it shows links and attributes within the Detail pane and doesn't touch the layout of the diagram.

This means you can use the diagram as a browser and see the aggregated attributes and relations (less important) for each class.

BTW the Set Feature Visibility is somewhat annoying in not resizing the shape back when you turn it off, so you end up fiddling with your diagram a lot.

4

Suggestions and Requests / Show Parent Attributes & Operations

« on: October 20, 2004, 11:44:28 pm »

We're new EA users and sorely missing a feature from MagicDraw - being able to see the attributes and associations (they call 'links') of a parent class combined in the details of a child.

I would call this a "flattened" view of an API, from framework documentation.

I've spent enough time looking through help and the forum to be fairly certain that EA doesn't provide such a feature but would be very happy to be enlightened otherwise!

5

General Board / Importing C++ with typedefs and standard libraries

« on: July 26, 2010, 04:19:59 pm »

I just tried importing a moderately complex codebase and was very disappointed with the experience.

Firstly, simple standard types like std::string are not recognised and I can't find a way to add those headers.

Secondly, it doesn't seem to understand typedefs. We follow the common idiom of using typedefs to simplify complex templated types, eg:

typedef Cfs::Internal::CfsIOHandleBase<Cfs::Internal::CfsRawStorage>    CfsStorageHandleBase; 
class CfsStorageHandle : public CfsStorageHandleBase 

It fails to recognise CfsStorageHandleBase in the last line, with an "unexpected symbol" error