a problem in latest moose 5.0 image

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

a problem in latest moose 5.0 image

EstebanLM
Hi,

Stef discovered a bug on latest moose image and I could reproduce it there, and not in corresponding pharo image.
So I think is a problem that happens in some package installed by you :)

Here is the issue:

Take a class and drag it to a different package. It will not change the system category and therefore everything will became unstable.

enjoy ;)

Esteban
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: a problem in latest moose 5.0 image

Stephan Eggermont-3
Yesterday I copied a configuration class with Nautilus copy command. I dragged it to the new category
and noticed the same happening. In addition, the class side methods were not copied.

Haven’t checked corresponding Pharo yet. Could be related to the RPackage problems though

Stephan
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: a problem in latest moose 5.0 image

Stephan Eggermont-3
In reply to this post by EstebanLM
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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: a problem in latest moose 5.0 image

Tudor Girba-2
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

Inline image 1

-- 

"Every thing has its own flow"


On Fri, Jan 24, 2014 at 2:52 PM, Stephan Eggermont <[hidden email]> 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: a problem in latest moose 5.0 image

Tudor Girba-2
Retrying with the attachment.

Inline image 1


On Fri, Jan 24, 2014 at 2:56 PM, Tudor Girba <[hidden email]> 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

Inline image 1

-- 

"Every thing has its own flow"


On Fri, Jan 24, 2014 at 2:52 PM, Stephan Eggermont <[hidden email]> 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: a problem in latest moose 5.0 image

Tudor Girba-2
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 <[hidden email]> wrote:
Retrying with the attachment.

Inline image 1


On Fri, Jan 24, 2014 at 2:56 PM, Tudor Girba <[hidden email]> 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

Inline image 1

-- 

"Every thing has its own flow"


On Fri, Jan 24, 2014 at 2:52 PM, Stephan Eggermont <[hidden email]> 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
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"



--

"Every thing has its own flow"



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev