Book a Demo

Author Topic: Navigating to the parent Repository from children  (Read 6815 times)

fwoolz

  • EA User
  • **
  • Posts: 435
  • Karma: +0/-0
  • We have met the enemy, and he is us.<Pogo, 1970>
    • View Profile
Navigating to the parent Repository from children
« on: June 26, 2010, 07:55:39 am »
In Microsoft's Office object model, it's often possible to navigate upwards to an object's parent, as in, say, Range.Document. It would be quite helpful if Sparx added similar functionality to its object model, so that one could get to the Repository object by invoking, for example, Element.Repository. This would simplify things like static method calls; instead of having to pass a Repository reference in addition to the object involved, one could pass just the object and get the associated Repository as described above.

FEATURE REQUEST ADDED with same title as the subject of this post.
Fred Woolsey
Interfleet Technology Inc.

Always be ready to laugh at yourself; that way, you beat everyone else to the punch.


Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Navigating to the parent Repository from child
« Reply #1 on: June 26, 2010, 09:58:39 am »
Supported!

I ended up adding it to my wrapper classes for this very reason.  But, as Fred says, it woudl be better if it was "native".

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

beginner

  • Guest
Re: Navigating to the parent Repository from child
« Reply #2 on: June 28, 2010, 06:58:41 am »
I'll stop voting for anything but correcting known bugs. I'm totally sick of getting new features that do not work. You know that Donald E. Knuth (and other authors who's name I do not remember) pays real money for each bug found in his books. Knuth pays double the amount for each bug found. And he's not poor yet (and probably will never be). I guess Sparx would be bankrupt if the only would have payed a static sum for each bug.

b.
« Last Edit: June 28, 2010, 06:59:31 am by beginner »

skiwi

  • EA Expert
  • ****
  • Posts: 2081
  • Karma: +46/-82
    • View Profile
Re: Navigating to the parent Repository from child
« Reply #3 on: June 28, 2010, 10:13:20 am »
Quote
I'll stop voting for anything but correcting known bugs. I'm totally sick of getting new features that do not work.


You parallel my point 1 well.

S
« Last Edit: June 28, 2010, 10:15:08 am by skiwi »
Orthogonality rules
Position and Team disestablished, thanks austerity.
Now itinerant.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Navigating to the parent Repository from child
« Reply #4 on: June 28, 2010, 04:37:35 pm »
Quote
Supported!

I ended up adding it to my wrapper classes for this very reason.  But, as Fred says, it woudl be better if it was "native".

Paolo

Ha, same here, each of my wrapper classes has a local reference to the EA.Repository wrapper.

Geert



beginner

  • Guest
Re: Navigating to the parent Repository from child
« Reply #5 on: June 28, 2010, 04:43:32 pm »
The funny thing is that I might feel guilty for having enforced this development (well, actually I don't feel that way). Not too long ago I recommended EA as the tool to be as it was evolving so rapidly, reacting fast as lightning to user wishes and fixing bugs even faster. But these times are over. Nothing is true anymore. I suspect Sparx is not able to make the necessary turn and switch over to stability rather then flexibility. I got used to (almost) all of the quirks over the years. But fresh people get annoyed soon. Be it users or programmers. To me it looks like Sparx is simply closing eyes and telling "what I don't see isn't there". Childish.

b.

P.S. Sorry for kidnapping this thread.
« Last Edit: June 28, 2010, 04:44:53 pm by beginner »