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.
--
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"