Wow indeed - first impressions

Absolutely brilliant!

I love the additions to the chb:
- show inherited methods
- smaller standard font ;-)
- browse package
- browse published aspects/events

Very impressed with the package browser:
- 'folder' tree
- prerequisites (WOW)

Feedback:
- can we have a keyboard shortcut to reformat methods (ctrl-R?)
- should have asked for this before, but I use the 'find class' icon on the
toolbar loads, therefore I hate it that it changes into 'find string' when
focus is in the text views at the bottom of the screen.
- won't start the discussion on the standard background colour again ;-)
- the mouse wheel scroll doesn't work in the class hierarchy diagram
- system browser - a way to install packages (right click the package tree
view/package menu?)
- moet tree browser - moet tree window and method list window layout not
correctly?
- sunit test runner - looks a bit Windows 3.1 style.....
- autoplay.default view still has the caption Dolphin Smalltalk 4.01 (don't
ask me how I came across it, just thought I'll mention it)

Just to give it a start

Ted

You wrote in message news:[hidden email]...
> Absolutely brilliant!

Thanks

Jeffrey Oddel has also asked for this. You are aware of the Ctrl+Shift+S
keyboard shortcut which reformats and saves?

> - should have asked for this before, but I use the 'find class' icon on
the
> toolbar loads, therefore I hate it that it changes into 'find string' when
> focus is in the text views at the bottom of the screen.

The toolbar icon, like Ctrl+F, is bound to the context sensitive "Find"
command. This will vary depending on the keyboard focus.
Ctrl+Shift+F is bound directly to the 'Find Class' command.

> - won't start the discussion on the standard background colour again ;-)

Why not :-). The colouring is mainly chosen to help us distinguish which of
the Dolphin versions we are running at a glance. The background colour of
the system folder in the eventual release may well be different (once our
"graphics consultant" gets going).

> - the mouse wheel scroll doesn't work in the class hierarchy diagram

Ah, thanks, defect # 458.

> - system browser - a way to install packages (right click the package tree
> view/package menu?)

Hmmm, we wanted to keep the responsibility for managing packages mainly with
the Package Browser. What do others think?

> - moet tree browser - moet tree window and method list window layout not
> correctly?

Yes, thanks. Already recorded as defect #455.

> - sunit test runner - looks a bit Windows 3.1 style.....

Not really our responsibility, since it is a "Camp Smalltalk" tool. If you
wanted to get in contact with the SUnit maintainer for Dolphin (who is that
now?) then I'm sure he or she would be happy to accept a revised view :-).
Actually I did start improving it a bit last year (mainly by adding a tree
to select the tests to run) but then Jeff shipped his SUnitBrowser and we
now use (and recommend) that exclusively.

> - autoplay.default view still has the caption Dolphin Smalltalk 4.01
(don't
> ask me how I came across it, just thought I'll mention it)

That's because it is in fact the actual Autoplay we have used for Dolphin
Smalltalk 4.01 CD's that we've handed out at various events, and we thought
it would be useful so we turned it into a sample. I'll modify it though,
thanks.

Regards

Blair

Blair,

> Hmmm, we wanted to keep the responsibility for managing packages mainly
with
> the Package Browser. What do others think?

I'd support allowing a sensible subset of package management from anywhere
that a package is visible as an onscreen "object".  Direct manipulation
seems, in general, to be the Dolphin approach (and a Good Thing too), so why
not apply the principle here ?

Anyway, it should at least be possible to open the PB on a package by
double-clicking in the package list.

> Not really our responsibility, since it is a "Camp Smalltalk" tool. If you
> wanted to get in contact with the SUnit maintainer for Dolphin (who is
that
> now?) then I'm sure he or she would be happy to accept a revised view :-).
> Actually I did start improving it a bit last year (mainly by adding a tree
> to select the tests to run) but then Jeff shipped his SUnitBrowser and we
> now use (and recommend) that exclusively.

Is there any reason to include the old test runner in the "extra tools"
folder at all then ?  It just takes up space (I use the extra tools folder a
lot, so I care about the space it needs).

    -- chris

Chris

You wrote in message news:[hidden email]...
> Blair,
>
> > Hmmm, we wanted to keep the responsibility for managing packages mainly
> with
> > the Package Browser. What do others think?
>
> I'd support allowing a sensible subset of package management from anywhere
> that a package is visible as an onscreen "object".  Direct manipulation
> seems, in general, to be the Dolphin approach (and a Good Thing too), so
why
> not apply the principle here ?

In general I'd agree, but this specific request related to the ability to
install new packages (rather than operate on existing ones). We think this
should be accomplished within the Package Browser (or from a script if ones
development style demands it be done frequently).

>
> Anyway, it should at least be possible to open the PB on a package by
> double-clicking in the package list.

I assume you are talking about the System Browser? If so I'd agree, and the
Browse-It (Ctrl+B) command should also do that when there is a selection in
that list and it has focus. Defect #475.

> > Not really our responsibility, since it is a "Camp Smalltalk" tool. If
you
> > wanted to get in contact with the SUnit maintainer for Dolphin (who is
> that
> > now?) then I'm sure he or she would be happy to accept a revised view
:-).
> > Actually I did start improving it a bit last year (mainly by adding a
tree
> > to select the tests to run) but then Jeff shipped his SUnitBrowser and
we
> > now use (and recommend) that exclusively.
>
> Is there any reason to include the old test runner in the "extra tools"
> folder at all then ?  It just takes up space (I use the extra tools folder
a
> lot, so I care about the space it needs).

Only that we wouldn't really consider it our place to "edit" the content of
the Camp Smalltalk tools.

I'm starting to build up an new image configuration script for you Chris:

    SmalltalkWorkspace defaultFont: nil.
    TestRunner uninitialize.
    ...

:-)

Regards

Blair

>
>     -- chris
>
>
>

Blair

> [...] but this specific request related to the ability to
> install new packages (rather than operate on existing ones). We think this
> should be accomplished within the Package Browser (or from a script if
ones
> development style demands it be done frequently).

Fair point, I agree now.

> I'm starting to build up an new image configuration script for you Chris:
>
>     SmalltalkWorkspace defaultFont: nil.
>     TestRunner uninitialize.
>     ...
>
> :-)

You should see the scripts I actually do use...

> Blair

    -- chris