Nonsense Epicea has nothing to do with RB goals. Epicea is to replace the changes file because we want a better change file and separate the code management from the version recording (micro commits). Source code could be managed in a separate database and microchanges can be managed to recover changes but not actually showing the latest version of a method. Stef Stef On Wed, Apr 26, 2017 at 11:19 AM, Peter Uhnak <i.uhnak@gmail.com> wrote:
Hi,
I'm under the impression that Epicea is supposed to replace RB refactorings at some point.
If that is true, is it currently possible to build refactorings by hand?
For example in RB I often do:
``` model := RBNamespace new.
model defineClass: ('<1s> subclass: #<2s><n><t>instanceVariableNames: <3p><n><t>classVariableNames: ''''<n><t>poolDictionaries: ''''<n><t>category: <4p>' expandMacrosWith: 'Object' with: 'MySomething' with: 'var1 var2' with: 'MyPackage'). cls := model classNamed: #MySomething. cls compile: 'var1 ^ var1' classified: 'accessing'.
(ChangesBrowser changes: model changes changes) open ```
or
(removing a method from a class) ``` model := RBNamespace new. model removeMethod: #testTrimRight from: StringTest. (ChangesBrowser changes: model changes changes) open ```
Thanks, Peter