( picoVerse-:( Up With Dolphin 6 Professional ) )

[picoVerse]

I just bought Dolphin 6 Professional.

I have been using the community version of Dolphin for a while.

I finally found that I needed to make a single .exe file for
distribution.

I give the Professional version two thumbs way up.

I really like the Idea Space and the System Browser. Those two things
are great.

The whole thing is just great. I highly recommend the professional
version. I think it is well worth it. I like Dolphin over Squeak and
VisualWorks. Squeak doesn't have a window builder( last time I
looked ) and it doesn't allow you to browse categories and VisualWorks
is too big and too expensive. Dolphin is the prettiest one.

One thing that is really great about Dolphin is that you can
categorize different things into the same category like
KEGTailPositionRecursion is a recent case for me and then you can
Browse the category and see all those related things together in one
single list. That is really great. And I bet nobody uses it either.
But it is a real big help. In sorting things out.

So when you see a method that is in the KEGTailPositionRecursion
category you can browse the category and see all the related methods
across different Classes and even across different packages.

The key is to make the categories really functionality specific.

If the categories get too many things in them then they become a lot
less functional in this way.

What would be really cool would be to be able to categorize code
fragments within methods and then see all the categorized methods
together in a single list. And when you click on a method then the
fragment(s) in question for that method is highlighted. Something
like that could go a long way towards making things more
understandable.

[Andy Bower]

Kego

> I just bought Dolphin 6 Professional.

Thanks.

> Dolphin is the prettiest one.

:-)

> What would be really cool would be to be able to categorize code
> fragments within methods and then see all the categorized methods
> together in a single list. And when you click on a method then the
> fragment(s) in question for that method is highlighted. Something
> like that could go a long way towards making things more
> understandable.

Do you think this would be useful. I sort of feel that, with Smalltalk
methods being pretty short anyway, that there wouldn't be too much
within a method to split up and categorize.

Best regards

Andy Bower