I had a look at the video, and it looks great. Certainly the way to go.

Well, it's not that great. And it shows pretty old version of what I have now. I should make a new better one:)

��

I had some ideas along those, but I never have time to try them. My interest would have been to show how many methods (and where: group-package-tag-class?) the search pattern will impact.

In current version you can generate rule(it creates class for your rule), and than you can select packages/classes/methods you want to apply this rule

��

One suggestion. When in the menu, try to auto-select the relevant keyword or literal;

You mean in all other panes? It would be really cool

��

give access to the ast navigation stuff (up select the enclosing ast node, down the first node inside).

That's really great!�� It'will take time, but I'm going to implement that, just have to remember:)

I think you can work recreating the ast. I'm not sure there is any reason to keep track of old nodes, because what you do is: apply a change to ast under selection; rebuilt RB matching / transform rule; apply RB rule to sample code. update all four panes.

The process on video is: creating your own rule step by step. While doing this user may make a mistake.

I keep oldNodes, because I want to have an "Undo on node" action. It returns node into it's previous state.��