Re: [Pharo-dev] [Moose-dev] Re: a problem in latest moose 5.0 image
Retrying with the attachment. [image: Inline image 1] On Fri, Jan 24, 2014 at 2:56 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
I also just downloaded the latest Pharo 3.0 (30719), and I took the first class AIRootContext from the 'AST-Interpreter-Core' and dragged it to 'AST-Core' and the category is not changed. So, the problem comes from Pharo.
See the picture attached.
Cheers, Doru
[image: Inline image 1]
-- www.tudorgirba.com
"Every thing has its own flow"
On Fri, Jan 24, 2014 at 2:52 PM, Stephan Eggermont <stephan@stack.nl>wrote:
Followups in the pharo-dev list, please
Esteban wrote:
I would really like a reproducible case⦠in the form of an image, if no else.
btw⦠moose 5.0 images are severely broken in that area, so if you are using one of them you *will* have problems.
I can deny that it is a Moose problem, I can reproduce it in Pharo 30716 on mac
Open the image, open a Nautilus browser Add new package AZ Select AST-Core, Nodes Select RBProgramNode Copy the class with right-click menu Rename to AZProgramNode Enter your name (should have happened when creating the new package!) Drag AZProgramNode to AZ Category is not updated.
Stephan _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
I am on the run and I do not have time to do it properly via the bug tracker right now, so I am just dumping here what I found after looking into this briefly. In AbstractNautilusUI we have: AbstractNautilusUI>>dropInAPackage: aCollection into: receiver aCollection do:[:aClass | self showGroups ifTrue: [ * receiver addClasses: { aClass }.* * ???I do not quite know when this one happens???.* ActiveHand shiftPressed ifFalse: [ self selectedGroup removeClass: aClass. self updateClassView ]] ifFalse: [ * receiver addClass: aClass theNonMetaClass. * * aClass theNonMetaClass category: receiver name asString.* ActiveHand shiftPressed ifTrue: [ self selectedClass: nil. self updateClassView ] ifFalse:[ self selectedPackage: receiver. self selectedClass: aClass. self updateBothView ]]] The problem seems to be that the red lines work directly with the RPackage, but at the moment the right thing to do is still to go via setting categories and to let the SystemAnnouncer trigger the behavior in RPackage. Cheers, Doru On Fri, Jan 24, 2014 at 2:59 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Retrying with the attachment.
[image: Inline image 1]
On Fri, Jan 24, 2014 at 2:56 PM, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
I also just downloaded the latest Pharo 3.0 (30719), and I took the first class AIRootContext from the 'AST-Interpreter-Core' and dragged it to 'AST-Core' and the category is not changed. So, the problem comes from Pharo.
See the picture attached.
Cheers, Doru
[image: Inline image 1]
-- www.tudorgirba.com
"Every thing has its own flow"
On Fri, Jan 24, 2014 at 2:52 PM, Stephan Eggermont <stephan@stack.nl>wrote:
Followups in the pharo-dev list, please
Esteban wrote:
I would really like a reproducible case⦠in the form of an image, if no else.
btw⦠moose 5.0 images are severely broken in that area, so if you are using one of them you *will* have problems.
I can deny that it is a Moose problem, I can reproduce it in Pharo 30716 on mac
Open the image, open a Nautilus browser Add new package AZ Select AST-Core, Nodes Select RBProgramNode Copy the class with right-click menu Rename to AZProgramNode Enter your name (should have happened when creating the new package!) Drag AZProgramNode to AZ Category is not updated.
Stephan _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
participants (1)
-
Tudor Girba