MC certainly abuses method categories, but it wouild not be as bad if methods could appear in multiple categories; that is a Dolphinism that you won't miss until after you have had it.
I would be opposed to hiding the method categories IF they are still used in the PackageInfo sense. If they continue to be abused/hijacked, then they should be displayed accordingly. Ideally we will succeed in creating first class packages that can be used as you describe, leaving method categories free to do what they do best.
Bill
________________________________________
From:
[hidden email] [
[hidden email]] On Behalf Of DeNigris Sean [
[hidden email]]
Sent: Monday, September 13, 2010 7:27 PM
To: The general-purpose Squeak developers list;
[hidden email]
Subject: [Pharo-project] Extension Methods
Extension methods showing up as *[PackageName] is an ugly hack!! It is an implementation detail (in this context) that probably should be first class (as a package name somewhere else), but definitely shouldn't be displayed to the user here :(
How about if *[PackageName]-[method category] showed up in the browser as:
Category (in the category pane): [method category]
Method name (in the right pane): [method name] (*[PackageName])
This way, since categories would cease to be hijacked, the methods would show up in their correct logical category, and it would still be clear that they were in a different package. Ideally, the dialogs to change the package/category would reflect this model, but changing the browsers would be a good start.
From ESUG
Sean
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Locked
