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

Pages: [1] 2 3 ... 824
1
Yep, it is ;-) I wasn't mentioning that because it would go to deep into the wild. Those more tricky things are better detailed in my Inside book. Alas, (without checking since it's too late here) you can take granted what Geert tells you in almost all cases.

q.

2
What do you intend to access by con.Client.SupplierEnd.Notes ?

q.

3
Sometimes you can experiment. I do have a stereotype TBD which formerly performed a shape script to make the background yellow. That worked for some time until I had to assign the color via a diagrammatic export. But if you are trying to combine complex things that will fail for sure.

q.

4
This has been asked (by Paolo IIRC) but I can't recall the answer (from Eve?). I'm dealing with "there is no order" as I always did.

q.

5
My 99% are the element notes. So they propably decided fot the "dunno".

q.

6
Automation Interface, Add-Ins and Tools / Re: MDG Meta-constraints
« on: October 22, 2021, 05:23:03 am »
I would guess that any metarelation you define would result in a new entry. However, I don't know by heart. If you figure it out, let us know :-) I'm just (again) starting to struggle with that.

q.

7
General Board / Define a metarelationship towards "stereotype"
« on: October 21, 2021, 02:50:09 am »
As it happens "stereotype" and "metaclass" are no stereotypes belonging to a profile. They are two of those ghost stereotypes. So how to nail the pudding to the wall? Or how to I get these into my Toolbox?

I fiddled for quite a while to realize that
Code: [Select]
      <Stereotype name="My Profile">
        <AppliesTo> <Apply type="ToolboxPage"/> </AppliesTo>
        <TaggedValues>
          <Tag name="UML::stereotype" default="Stereotype"/>
        </TaggedValues>
      </Stereotype>
 
will actually create such a ghost. (Trying with just "stereotype" simply did not create a toolbox entry; of course with no warning from EA.) It does show a class icon instead of the expected guillements. Well, I could live with that...

Now, how to do that for the "metaclass"?? The EA default creates a ghost stereotype (as said). Now I started experimenting.
Code: [Select]
      <Stereotype name="My Profile">
        <AppliesTo> <Apply type="ToolboxPage"/> </AppliesTo>
        <TaggedValues>
          <Tag name="UML::metaclass" default="Metaclass"/>
        </TaggedValues>
      </Stereotype>
 
That again shows the class icon and offers that wizard (argh) dialog to select. One chosen, EA starts complaining by popping up a message box telling that it does not like "UML::metaclass". Well, what? The created metaclass now has "UML Standard Profile::Metaclass" standing in the stereotype. Not a ghost one. And of course the quick linker does not recognize it (thus not offering Extenstion).

Well, while writing I changed the case for metaclass
Code: [Select]
          <Tag name="UML::Metaclass" default="Metaclass"/>
 

and now that shows the correct icon and does no longer complain. But still it creates no ghost metaclass but a "UML Standard Profile::Metaclass". The QL issue is the same.

I already went up the road defining my own stereotype and metaclass in my profile. Those showed up correctly in the toolbox and worked as expected. However, trying to add a metarelationship to show Extension between both did nothing.

So, what shall I do (except cursing)? I just need to add that metarelationship...

q.

P.S. When addding the constraint I tried something like this:
Code: [Select]
<Stereotypes>
<Stereotype name="stereotype" notes="" isAbstract="true">
<metarelationships>
<metarelationship metaclass="Generalization" constraint="UML Standard Profile::Metaclass"/>
</metarelationships>
</Stereotype>
...
but the Generalization did not show between ghost "stereotype" and the "UML Standard Profile::Metaclass"

8
General Board / Re: EA Code Generated From State Machines Question
« on: October 20, 2021, 09:34:19 am »
Keep on with that! I once started with code generation and went away from that queer macro language to just using the API. That gave me the ability to create ANY code I liked. However, as you could read above, i soon got to the point where I recognized that code generation is futile. I once used Rational Rose for code generation and that was quite nice out of the box. However, based on my experiance I wouldn't go that way further. Good luck with your hobby attempts, though :-)

q.

9
General Board / Re: OV-6c / Event Trace Diagram questions
« on: October 20, 2021, 08:48:25 am »
Honestly I don't know since I have no idea what this event trace diagram would be you're talking about. Maybe you're just using a SD?

q.

10
General Board / Re: EA Code Generated From State Machines Question
« on: October 20, 2021, 08:46:20 am »
Both of your code sections have the same content...

I would not bother to much with code generation. I think that's a cul-de-sac. Modeling and coding are two different domains and should stay separate. It's difficult to bridge, but that would be the task of the system architect. The model would be some abstract system and allow to keep juggling the balls in the air. Once you got the idea you can shove it over to the coders which can use UML for detailing things in (say) sequence diagrams (unless that will not make them complain about being too hard to use). Juggling looks easy, but everyone knows that it's pretty difficult and needs lots of experience....


q.

11
General Board / Re: Slow project transfer speed eapx to SQL Server
« on: October 19, 2021, 09:30:08 pm »
Well, for a SQL-SQL-Server you can simply use a SQL-Server backup.

q.

12
General Board / Re: Slow project transfer speed eapx to SQL Server
« on: October 19, 2021, 08:11:34 pm »
No, that's the queries taking time. EAP(x) is completely in-memory on your machine. Access to the SQL server will be over some network. And there can be lots of hurdles (the server itself, the network at all the many hops it has to take).

q.

13
General Board / Re: OV-6c / Event Trace Diagram questions
« on: October 19, 2021, 08:12:57 am »
Sounds just like the behavior in sequence diagrams. I wouldn't bet to see any change to that (except getting worse).

q.

14
AFAIK you can not stack shape scripts as there will not be any rule in which multiple/inherited shapes are worked at. So the best would likely be (as you thought) to start from scratch.

q.

15
EAUML is a profile name. An MDG may contain an arbitrary number of profiles of also arbitrary names.

q.

Pages: [1] 2 3 ... 824