Issue 5954 in pharo: Nautilus subclass generation fails when viewing class side.

Status: New
Owner: ----
Labels: Nautilus

New issue 5954 by [hidden email]: Nautilus subclass generation fails when  
viewing class side.
http://code.google.com/p/pharo/issues/detail?id=5954

In Nautilus, looking at class side definitions, and I click on the class to  
Refactoring -> Class Refactoring -> Generate Subclass..., I find that a  
subclass is attempting to be created on MetaObject, which fails due to not  
understanding the #category message. This is not the same behavior as  
happens when looking at instance side, which created a named subclass of  
the class being viewed.

Subclass Generation should use the current class, not the metaclass.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Accepted
        Labels: Type-Bug Milestone-2.0

Comment #1 on issue 5954 by [hidden email]: Nautilus subclass  
generation fails when viewing class side.
http://code.google.com/p/pharo/issues/detail?id=5954

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 5954 by [hidden email]: Nautilus subclass generation  
fails when viewing class side.
http://code.google.com/p/pharo/issues/detail?id=5954

Similar behavior is exhibited when trying to add a package to a group which  
includes a class side extension. This is due to the block in  
DialogGroupAdderUI>>text.

If this should be a new issue, I can add it elsewhere.

Attached is a small monticello package which loads a package Issue and  
Issue-Core. Issue-Core defines MyClass, and Issue includes two extension  
methods. The presence of the class extension raises a Metaclass  
doesNotUnderstand prettyName error when attempting to add Issue to a group  
in Nautilus. Issue-Core can be added to a group with no problems. Removing  
the class side extension allows Issue to be added to the group.

It looks like a similar problem (Nautilus trying to act on  
Metaclass/MetaObject for class side operations). This does not occur when  
attempting to add the class or method to a group by selecting them, only  
when the package is selected for adding and it contains a class extension  
method.

Attachments:
        Issue-DanielUber.1.mcz  1.3 KB


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Cc: [hidden email]

Comment #3 on issue 5954 by [hidden email]: Nautilus subclass  
generation fails when viewing class side.
http://code.google.com/p/pharo/issues/detail?id=5954

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixToInclude

Comment #4 on issue 5954 by [hidden email]: Nautilus subclass  
generation fails when viewing class side.
http://code.google.com/p/pharo/issues/detail?id=5954

NautilusRefactoring-BenjaminVanRyseghem.40 in PharoInbox (fix the part 1)
About the second part, I can't reproduce it


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Integrated

Comment #5 on issue 5954 by [hidden email]: Nautilus subclass  
generation fails when viewing class side.
http://code.google.com/p/pharo/issues/detail?id=5954

in 2.0 210


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker