Tools for refactoring and 'quality control'

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Tools for refactoring and 'quality control'

espin
Out of curiosity, has anybody a refactoring tool working in Trunk?
Around you find mentioned Refactoring Browser, Omni Browser (with Refactoring Engine),
Slime, SmalLint...

Any suggestion as what to use and how to load from a Trunk-based image?
Thanks in advance
Bye
--
Enrico Spinielli
"Do Androids dream of electric sheep?"— Philip K. Dick
"Hear and forget; see and remember;do and understand."—Mitchel Resnick


Reply | Threaded
Open this post in threaded view
|

Re: Tools for refactoring and 'quality control'

Colin Putney

On 2010-04-03, at 6:21 AM, Enrico Spinielli wrote:

> Out of curiosity, has anybody a refactoring tool working in Trunk?
> Around you find mentioned Refactoring Browser, Omni Browser (with Refactoring Engine),
> Slime, SmalLint...
>
> Any suggestion as what to use and how to load from a Trunk-based image?
> Thanks in advance

I'm working on a new OmniBrowser release that works in Squeak 4.1. In the meantime, try using this version of the refactoring engine:

http://www.squeaksource.com/rb/Refactoring-Core-cwp.116.mcz

There's a few other issue with OB on trunk, but this solves the bulk of it.

Colin
Reply | Threaded
Open this post in threaded view
|

Re: Tools for refactoring and 'quality control'

Chris Muller-3
> I'm working on a new OmniBrowser release that works in Squeak 4.1. In the meantime, try using this version of the refactoring engine:
>
> http://www.squeaksource.com/rb/Refactoring-Core-cwp.116.mcz

Hi, I tried this in the trunk image but RBParseTreeSearcher is
missing.  I don't mean to ask a dumb question but..  Can you help me
remember the overall structure and status of Refactoring Browser?
>From long-ago history, I seem to remember that RB had its own
browsers, but now I hear about "Refactoring Engine" and so was that
the RB domain factored out and made browser independent?  Did you do
that refactoring work as part of OB, and then use of the Refactoring
Engine was also picked up by the standard Squeak browsers?

Thanks for your insight.

On Sat, Apr 3, 2010 at 10:06 AM, Colin Putney <[hidden email]> wrote:

>
> On 2010-04-03, at 6:21 AM, Enrico Spinielli wrote:
>
>> Out of curiosity, has anybody a refactoring tool working in Trunk?
>> Around you find mentioned Refactoring Browser, Omni Browser (with Refactoring Engine),
>> Slime, SmalLint...
>>
>> Any suggestion as what to use and how to load from a Trunk-based image?
>> Thanks in advance
>
> I'm working on a new OmniBrowser release that works in Squeak 4.1. In the meantime, try using this version of the refactoring engine:
>
> http://www.squeaksource.com/rb/Refactoring-Core-cwp.116.mcz
>
> There's a few other issue with OB on trunk, but this solves the bulk of it.
>
> Colin
>

Reply | Threaded
Open this post in threaded view
|

Re: Tools for refactoring and 'quality control'

Colin Putney

On 2010-04-03, at 3:42 PM, Chris Muller wrote:

>>  Can you help me
> remember the overall structure and status of Refactoring Browser?
>> From long-ago history, I seem to remember that RB had its own
> browsers, but now I hear about "Refactoring Engine" and so was that
> the RB domain factored out and made browser independent?  Did you do
> that refactoring work as part of OB, and then use of the Refactoring
> Engine was also picked up by the standard Squeak browsers?
>
> Thanks for your insight.

Lukas Renggli is mostly responsible for the (excellent!) state of refactoring code in Squeak today. The original RB port was factored out into separate browser and engine packages, and the engine was incorporated into OB. Just recently, Lukas made a fresh port of some of the refactoring code from the most recent Refactory release. As far as I know, OB is the only browser for Squeak has supports refactoring - the "Refactoring Browser" package withered and died years ago.

Colin
Reply | Threaded
Open this post in threaded view
|

Re: Tools for refactoring and 'quality control'

Ralph Johnson
John Brant and Don Roberts divided the original refactoring browser into several components to aid in portability.   They supported it on VisualWorks and VisualAge for a few years, so they had to separate the GUI from the engine, and to have a portability layer underneath.   When it was ported to Squeak, someone wrote a new GUI and used pretty much everything else as-is.   I tried using it, but the GUI seemed incomplete.  The OB GIU is very solid.

-Ralph