[parenblinking]
Yes, that too. I'm now using it all the time. I've experienced a
sporadic bug with this where sometimes bold stuff gets left behind. Have
you seen this?

[shrinking selections]
I agree. It breaks some packages because it changes some instance
variable meanings, but it should be trivial to fix.

[Breakpoints package]
Haven't tried it yet. Does it make your life easier?

[other packages, Stubcreation should be harvested into the image]
Agree. 

Daniel

Marcus Denker <marcus at ira.uka.de> wrote:
> On Mon, Jul 21, 2003 at 01:56:57PM +0300, Daniel Vainsencher wrote:
> > For anyone wanting to work XP style, BrowseUnit makes the mechanics
> > quite a bit easier, in a very nice way.
> > 
> > "Debugger - stub method creation" helps in another part of the
> > mechanics, by allowing you to use undefined methods in your new tests,
> > and then create them lazily from the debugger. 
> > 
> > Who else uses them? I think we should consider parts of these for
> > inclusion in Basic (not for 3.6, of course).
> > 
> I use both in all my development images: It makes TestDriven Development
> much nicer... I think Debugger-Stubmethodcreation shouldn't be its own
> package: It should be added to the standard debugger (thus harvested
> into the image like a ENH to the Debugger).
> 
> BrowseUnit depends on SUnit, which is it's own package. So BrowseUnit
> need to be in it's own package... But this package should be part of
> "Basic". 
> 
> Other development-related changeset we should look at early in 3.7a are the
> shriking-selections-patch (which allows to adjust selections
> via shift-arrow), Avi's parenblinking and maybe the breakpoints package.
> 
>        Marcus
> 
> -- 
> Marcus Denker marcus at ira.uka.de  -- Squeak! http://squeak.de