Hello,
Really after one hour of thinking that somewhere there is a bug I found the selectors InheritanceDefinition>>superClass and InheritanceDefinition>>subClass
which are not accessors and they are different of:
InheritanceDefinition>>superclass and InheritanceDefinition>>subclass.
Could you please illustrate why we need the selectors #superClass and #subClass when we have the accessors #superclass and #subclass? Specially, could you explain why both return a group that will always contain one, and only one, element?
thanks, hani
Hi,
Those are some unhappy names. The idea behind having a Group is just for the UI. The navigation works nicer with Group because you also get an explanation of what you have inside.
Usually, all methods that have a navigation:'' pragma are used by the UI.
Doru
On Oct 17, 2008, at 3:41 PM, Hani ABDEEN wrote:
Hello,
Really after one hour of thinking that somewhere there is a bug I found the selectors InheritanceDefinition>>superClass and InheritanceDefinition>>subClass
which are not accessors and they are different of:
InheritanceDefinition>>superclass and InheritanceDefinition>>subclass.
Could you please illustrate why we need the selectors #superClass and #subClass when we have the accessors #superclass and #subclass? Specially, could you explain why both return a group that will always contain one, and only one, element?
thanks, hani _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"Value is always contextual."
These methods are used to navigate through the moose browser I guess, but I am wondering why I do not have an entry 'Superclass' in the navigation menu. the method #superClass does not have much sender. Maybe it is obsolete.
Cheers, Alexandre
On 17 Oct 2008, at 15:41, Hani ABDEEN wrote:
Hello,
Really after one hour of thinking that somewhere there is a bug I found the selectors InheritanceDefinition>>superClass and InheritanceDefinition>>subClass
which are not accessors and they are different of:
InheritanceDefinition>>superclass and InheritanceDefinition>>subclass.
Could you please illustrate why we need the selectors #superClass and #subClass when we have the accessors #superclass and #subclass? Specially, could you explain why both return a group that will always contain one, and only one, element?
thanks, hani _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Oct 18, 2008, at 9:05 AM, Alexandre Bergel wrote:
These methods are used to navigate through the moose browser I guess, but I am wondering why I do not have an entry 'Superclass' in the navigation menu. the method #superClass does not have much sender. Maybe it is obsolete.
I imagine that the menu is build dynamically
Cheers, Alexandre
On 17 Oct 2008, at 15:41, Hani ABDEEN wrote:
Hello,
Really after one hour of thinking that somewhere there is a bug I found the selectors InheritanceDefinition>>superClass and InheritanceDefinition>>subClass
which are not accessors and they are different of:
InheritanceDefinition>>superclass and InheritanceDefinition>>subclass.
Could you please illustrate why we need the selectors #superClass and #subClass when we have the accessors #superclass and #subclass? Specially, could you explain why both return a group that will always contain one, and only one, element?
thanks, hani _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
These methods are used to navigate through the moose browser I guess, but I am wondering why I do not have an entry 'Superclass' in the navigation menu. the method #superClass does not have much sender. Maybe it is obsolete.
I imagine that the menu is build dynamically
Yes, but when does it appear? I tried out few menu in the Moose Browser, but I haven't seen it.
Cheers, Alexandre
You see it when you select an InheritanceDefinition.
Cheers, Doru
On Oct 18, 2008, at 1:58 PM, Alexandre Bergel wrote:
These methods are used to navigate through the moose browser I guess, but I am wondering why I do not have an entry 'Superclass' in the navigation menu. the method #superClass does not have much sender. Maybe it is obsolete.
I imagine that the menu is build dynamically
Yes, but when does it appear? I tried out few menu in the Moose Browser, but I haven't seen it.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"One cannot do more than one can do."
You see it when you select an InheritanceDefinition.
Oh okay!
Cheers, Alexandre
Cheers, Doru
On Oct 18, 2008, at 1:58 PM, Alexandre Bergel wrote:
These methods are used to navigate through the moose browser I guess, but I am wondering why I do not have an entry 'Superclass' in the navigation menu. the method #superClass does not have much sender. Maybe it is obsolete.
I imagine that the menu is build dynamically
Yes, but when does it appear? I tried out few menu in the Moose Browser, but I haven't seen it.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"One cannot do more than one can do."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Hani ABDEEN -
Stéphane Ducasse -
Tudor Girba