Hi
I was following an exercise written by alex and the following code does not work | superclassEdges | luModel := (MooseModel allInstances last). luClasses := luModel allModelClasses. view shape rectangle size: [ :cls | cls queryAllOutgoingInvocations size ]. view nodes: luClasses. superclassEdges := view edgesFrom: #superclass. view treeLayout userDefinedEdges: superclassEdges. view shape line color: Color red. view edges: luClasses from: #yourself toAll: [ :cls | cls queryAllOutgoingInvocations atClassScope ] edgesFrom: raises an error several candidates. and I do not understand why. Stef _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Apparently my model was corrupted. now on a real example this example produce a red sqare so there is something strange in exported invocations
or something like that. On Sep 28, 2013, at 5:53 PM, Stéphane Ducasse <[hidden email]> wrote: > Hi > > I was following an exercise written by alex and the following code does not work > > > > | superclassEdges | > luModel := (MooseModel allInstances last). > luClasses := luModel allModelClasses. > view shape rectangle size: [ :cls | cls queryAllOutgoingInvocations size ]. > view nodes: luClasses. > superclassEdges := view edgesFrom: #superclass. > view treeLayout userDefinedEdges: superclassEdges. > > view shape line color: Color red. > view edges: luClasses from: #yourself toAll: > [ :cls | cls queryAllOutgoingInvocations atClassScope ] > > > edgesFrom: raises an error several candidates. > > and I do not understand why. > > Stef > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Stéphane Ducasse
Strange. I obtain a visualization that looks like this one:
I have no error, except a warning saying that I should use atTypeScope instead of atClassScope. By the way, I am not sure why we have changed atClassScope -> atTypeScope. Their names implies a different meaning. Alexandre On Sep 28, 2013, at 12:53 PM, Stéphane Ducasse <[hidden email]> wrote: Hi -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
On Sep 29, 2013, at 3:29 AM, Alexandre Bergel <[hidden email]> wrote: yes i got the same too and it looks not usable :)
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
This was discussed in details several times in the past. The reason is this: - FAMIXClass is only one of the subclasses of FAMIXType. - When working with systems like Java, you get in your model many types that are not FAMIXClass (e.g., FAMIXParameterizedType which models a specific generic type)
- When atClassScope was first created, #methods and #attributes were defined in FAMIXClass. In the meantime, we generalized the model, and we now have FAMIXType defining #methods and #attributes. The subtypes of FAMIXType are now responsible for handling only extra semantics. So essentially, the old atClassScope does correspond now with atTypeScope.
Cheers, Doru On Sun, Sep 29, 2013 at 9:17 AM, Stéphane Ducasse <[hidden email]> wrote:
"Every thing has its own flow"
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |