[Setools] Gjallar: extracting features

[Ron Teitelbaum]

Thanks Chris,

I understand that the other tools are needed.  I use them all the time.  I
find it easy to browse hierarchy from the package browser.  My real question
was why someone would suggest removal of the package browser.  For me it
lies at the center of development, and for me thinking of where the code
should be stored and packaged actually comes first.  This is especially true
when I need to add methods to base classes.  The ability to package a method
using a *Package notation and then forget about it is critical and very
productive.  

Thanks again for your explanation.

Ron 

> From: Chris Muller
> Sent: Sunday, February 11, 2007 10:47 PM
> 
> > Could you explain these comments?
> 
> Ron, the package browser is more a code-organization tool useful only
> for viewing and defining package boundaries.  This is typically done at
> the first and last 5% of a development life-cycle.  The rest of the
> time you really want browsers that allow you to focus on the _code_
> model, like classes, their hierarchies, and cross-cutting message
> flows.
> 
> _______________________________________________
> Setools mailing list
> Setools at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/setools