Status: Accepted
Owner: [hidden email] New issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 The point of tools registry is NOT to be a $%^&* facade full of protocols but to be a registration for tools that get loaded. So tool registry should not hod specific tools protocol. tool clients should invoke the correct methods of the tools. _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #1 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 It was there for legacy reasons. _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Labels: Type-Cleanup Comment #2 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 (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:
Labels: Milestone-1.4 Importance-High Difficulty-Easy Comment #3 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 So we should deprecate all the methods in convenience-browsing, convenience-debugging, convenience-inpsecting. For example: browse: aClass selector: aSelector "Open a browser" self deprecated: 'Use Smalltalk tools browser then a specific protocol like fullOnClass:selector:' on: '15 October 2011' in: 'Pharo1.4'. self using: #browser do: [:tool | tool fullOnClass: aClass selector: aSelector ] and client should use using: do: instead! _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #4 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 Is it possible to divide this issue in three parts? one for each category and this issue depends on the new ones. im asking because there are a lot of messages and references to solve (someone of them are not trivial for me). what do you think?. _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #5 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 Sure, if you want to do it in steps, you can make changesets for every step, and we will integrate them one by one. There no pressure to do it in a single huge blow. Also, small changes is better because they are easier to verify and fix, if they causing problems. _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Comment #6 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 Sure!. Yes you can even open a new entry for each action if this is helping you. As igor says the smaller the easier :) _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Updates:
Blockedon: 5197 Comment #7 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 (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:
Blockedon: 5198 Comment #8 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 (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:
Blockedon: 5199 Comment #9 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 (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:
Blockedon: 5224 Comment #10 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 (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: Closed Comment #11 on issue 4913 by [hidden email]: All the methods in ToolRegistry convenience protocols should be deprecated. http://code.google.com/p/pharo/issues/detail?id=4913 (No comment was entered for this change.) _______________________________________________ Pharo-bugtracker mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker |
Free forum by Nabble | Edit this page |