Book a Demo

Author Topic: Property Set/Get should be suppressible  (Read 4674 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Property Set/Get should be suppressible
« on: May 24, 2006, 07:26:10 pm »
Using Set Feature Visibility, it should be possible to directly suppress Property setters and getters.  This is because EA displays both the "Attribute" (which really isn't a raw Attribute any more, but a named Property) and the setters and getters.

I realise that it is possible to do this now, by using the «property» stereotype as the specified stereotype to hide.  However, I feel the functionality is more goal oriented than the work-around.

Paolo
« Last Edit: May 24, 2006, 07:27:43 pm by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Property Set/Get should be suppressible
« Reply #1 on: May 24, 2006, 08:09:50 pm »
Couldn't we always do something like this via the UML visibility indicators? Hide private property features but display public getter and setter methods.
No, you can't have it!

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Property Set/Get should be suppressible
« Reply #2 on: May 24, 2006, 08:26:19 pm »
Quote
Couldn't we always do something like this via the UML visibility indicators? Hide private property features but display public getter and setter methods.
Not really, see my Properties Redux posting.

In many languages (and conceptually - in my view) it is the named property that is public.

I'd be interested in adornments to the named property that indicted if it was read-only or write only.

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

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: Property Set/Get should be suppressible
« Reply #3 on: May 24, 2006, 08:33:46 pm »
Quote
I'd be interested in adornments to the named property that indicted if it was read-only or write only.


YESYESYES!!!
b
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Property Set/Get should be suppressible
« Reply #4 on: May 24, 2006, 09:26:00 pm »
Regarding the initial request.  Is what you are wanting essentially the same as provided at the diagram level with 'Hide Property Methods'?

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Property Set/Get should be suppressible
« Reply #5 on: May 24, 2006, 11:22:25 pm »
Quote
Regarding the initial request.  Is what you are wanting essentially the same as provided at the diagram level with 'Hide Property Methods'?
Yes Simon - at the classifier level and for both local and inherited properties.

Thanx,
Paolo

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

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Property Set/Get should be suppressible
« Reply #6 on: May 25, 2006, 03:29:57 am »
I second the classifier-level visibility setting.

And, I 'third' the adornments.

Either would be helpful, both even better.
No, you can't have it!