The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Another RB Hack

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
Another RB Hack Posted: Dec 12, 2003 3:16 PM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: Another RB Hack
Feed Title: Travis Griggs - Blog
Feed URL: http://www.cincomsmalltalk.com/rssBlog/travis-rss.xml
Feed Description: This TAG Line is Extra
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Travis Griggs - Blog

Advertisement
Often the question is asked "I want to rename a method with the RB, but I just want to do it in my package". Some know that if you turn on the "show refactorings" option in the settings tool under "browser", each refactoring opens a dialog which allows you to filter the changes before they are applied. But it shows it for every little refactoring. So you either put up with the dialog, adding the extra step of hitting "accept" on every single refactoring, or you go back and forth, or you just say bag it and do those kinds of changes manually. This has been bugging me and one of the other guys at Key for a while; it's finally been fixed (credit goes to Randy Coulman for initiating it).

The package RBBetterRefactorWarnings changes the behavior of when "show changes" is NOT enabled. We think, if we did it right, it should still behave the same obnoxious way when the option is enabled. When it's not enabled though, instead of the warning dialog, you instead get the warning dialog with changes. Basically, rather than show the simple dialog, we hijacked the CompositeRefactoringChangesInspector to show the warning, and of course present all of the changes that are causing dire warnings. So it's no more clicks than before, but allows you minimal clicks to filter the changes if necessary. Sorry we couldn't come up with an "Extra" package name, putting "Better" in there though got us enough presumption that I was satisfied. :)

Aside: In the past, John and Don probably would have taken this as a suggestion and probably provided a fix. With the sale of RB to Cincom though, it seems that evolution of the best code browser ever built has slowed. Or is it just me? That's not (btw) to say that John and Don don't still provide great changes for the RB. I appreciate greatly the contributions they continue to make.

Read: Another RB Hack

Topic: IBM ships a new VA Previous Topic   Next Topic Topic: Where Are We Now - Part 1

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use