Let me know if there is other code that needs to be moved. Lukas Name: Refactoring-Core-lr.143 Author: lr Time: 10 June 2010, 3:34:12 pm UUID: 91014fcc-aa9f-4590-a22c-f8a1a0a5daa1 Ancestors: Refactoring-Core-lr.142 - moved some code from OB-Refactory Name: Refactoring-Tests-Core-lr.44 Author: lr Time: 10 June 2010, 3:34:37 pm UUID: 35e845c2-d58e-4b76-a1b7-bcec35761870 Ancestors: Refactoring-Tests-Core-lr.43 - moved some code from OB-Refactory Name: OB-Refactory-lr.214 Author: lr Time: 10 June 2010, 3:35:01 pm UUID: 70a76d23-ab08-450f-88c0-556b70666ed0 Ancestors: OB-Refactory-lr.213 - moved some code to Refactoring-Core On 10 June 2010 15:13, Lukas Renggli <renggli@gmail.com> wrote:
On 10 June 2010 13:40, Fernando olivero <oliverof@lu.unisi.ch> wrote:
Lukas do you think it would worth it to change the category of several methods, from extensions to OB to the refactoring engine itself.
For example in my case i don't need OB at all, but are forced to load just because this extensions are goodies i've need when using the refactoring engine.
For example
BrowserEnvironment>>allNonMetaClasses
from the category *ob-refactory-accessing
Maybe it's an sign that these belong to the refactoring engine package, the model, and not Ob, the view.
What do you think?
Yeah, that makes sense. We just have to write tests for them in the refactoring tests.
Lukas
Fernando _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli www.lukas-renggli.ch
-- Lukas Renggli www.lukas-renggli.ch