On 31 August 2011 18:34, Lukas Renggli <[email protected]> wrote: >>> Note that the classes contain actually excellent documentation. >>> >> Do you have any particular one in mind? > > You asked about the AST nodes. > >> I traced OB's execution to >> RBStringReplaceRule and then looked up the hierarchy finding basic >> few-sentence descriptions, but nothing in-depth about how to search and >> replace. > > That's a private internal class, you are not supposed to instantiate it. You > find documentation about the rewrite engine in the first link I sent you. > >>> Actually you can do it with a few clicks: Select #deprecated:, click >>> on "Refactor method > Add parameter" and follow the instructions. >>> >> Notice I asked about the API, not about the OB GUI. > > I couldn't guess that. > >> I needed to >> programmatically change each one depending on the sender's timeStamp and >> the >> collections of what was deprecated in which version. Also, there are >> already >> methods in the system with the name I'm changing to, so OB just mentions >> that and fails. > > A few more clicks and you have a refactoring scope on any method set you > want. > >> Let me ask maybe a better question - how would you do the following >> programmatically? > > I would crete a rewriter for each case, instantiate a RBNamespace, iterate > over all methods within, and apply the rewriters if necessary, then review > the changeset, and apply it. >
This is one of the best things which i seen in OB. But even by watching your screencasts i found it hard to use. I remember i tried to rewrite some code using it but then i failed and lost in space (too much windows open, no clear visibility in what context they might work and why it fails for me, but works for you etc etc), so i abandoned attempts to master refactoring-fu using OB. And of course, since most of the times i hunting bugs in core image(s) of past , OB was not there and these features was not available to me, as developer (that's again, another reason to have single image for everyone). I would really like to have it in our _default_ images to empower developers. And with nice documentation (HelpSystem maybe?) because you know, for you , as an author (and/or maintainer) of it things look pretty straightforward, but for people who only get started they apparently not. > Cheers, > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Best regards, Igor Stasenko AKA sig.
