A wish list

Hi,

1/ I would like an indication in the CHB that a class has a comment. The
indication could be an icon in "Class comment" tab (like the Package
Browser/Scripts tabs) or giving the "Class comment" text an enabled/disabled
look, or in the status bar. This would be good for the reader, and help the
writer to not forget about old comments.

2/ I would like a "Paste Text" menu command in "Edit" menus.

3/ When doing a rename refactoring, I would like another precondition that
informs me when I am renaming to a selector that already exists in the
image.

4/ Tongue in cheek (but the first change I will make to my image);  why is
"Find" the top pop-up menu command in the CHB classes pane? Since this is
Dolphin XP, my vote is for "Run Tests"!

(5/ and 6/ are from the perspective of an STS user. The repository is the
primary source of my packages, and the file system is used to
export/import/deploy packages).

5/ In the PackageBrowser, I would like to select a package folder and be
able to save out all packages in and below that folder, relative to a base
directory that I am prompted for. (Will "Save All Packages ..." do this?)

6/ In the PackageBrowser, I would like to be able to drag and drop a Package
to change its Folder.


=====
"Tools/System Transcript" does not bring an opened Transcript to the front.
(same in D4).

How to change a Font or Color Aspect is not obvious with the changes to
Object>>publishedAspects.

Thanks,
Steve Waring

Steve

"Steve Waring" <[hidden email]> wrote in message
news:[hidden email]...
> Hi,
>
> 1/ I would like an indication in the CHB that a class has a comment. The
> indication could be an icon in "Class comment" tab (like the Package
> Browser/Scripts tabs) or giving the "Class comment" text an
enabled/disabled
> look, or in the status bar. This would be good for the reader, and help
the
> writer to not forget about old comments.

I've logged an enhancement request (#550). It ought to be pretty easy to do
it in a similar way to the package browser script tabs (which are ticked if
there is a script), so if we get time...

> 2/ I would like a "Paste Text" menu command in "Edit" menus.

Yes, so would I (#551).

> 3/ When doing a rename refactoring, I would like another precondition that
> informs me when I am renaming to a selector that already exists in the
> image.

Are you sure you'd want to be prompted about that every time?

> 4/ Tongue in cheek (but the first change I will make to my image);  why is
> "Find" the top pop-up menu command in the CHB classes pane? Since this is
> Dolphin XP, my vote is for "Run Tests"!

History - its always been there, and it is still probably the most common
operation one performs off that menu (although personally I always use the
Ctrl+Shift+F accelerator), especially since 'Run Tests' only applies to
TestCase subclasses (there is currently no way to identify the tests that
relate to a particular class).

> (5/ and 6/ are from the perspective of an STS user. The repository is the
> primary source of my packages, and the file system is used to
> export/import/deploy packages).
>
> 5/ In the PackageBrowser, I would like to select a package folder and be
> able to save out all packages in and below that folder, relative to a base
> directory that I am prompted for. (Will "Save All Packages ..." do this?)

Save all packages will save relative to the image (at least it will when
working). I'm not quite sure what the implications of what you suggest would
be, bearing in mind the idea behind the hierarchical organisation relative
to the image root. I suppose if it were to be a distinct "Export" command
which didn't actually change the path of the packages then it would be OK.

> 6/ In the PackageBrowser, I would like to be able to drag and drop a
Package
> to change its Folder.

Enhancement request, #552.

> =====
> "Tools/System Transcript" does not bring an opened Transcript to the
front.
> (same in D4).

I've recorded that as #553.

>
> How to change a Font or Color Aspect is not obvious with the changes to
> Object>>publishedAspects.

I don't understand? Surely there is no change, and one uses Aspect
class>>font: or Aspect class>>color: as before?

Thanks for your feedback,

Blair

Hi Blair,

>> 3/ When doing a rename refactoring, I would like
>> another precondition that informs me when I am
>> renaming to a selector that already exists in the
>> image.

> Are you sure you'd want to be prompted about that every time?

Yes, I made this change in D4 and liked it. The caveat is that I did not
have the refactoring within a scope options available, and I guess I could
now use that to get myself out of the situations I want to avoid. (ie rename
to an unrelated method's name, and not notice until the buffer is cleared).

>> How to change a Font or Color Aspect is not obvious
>> with the changes to Object>>publishedAspects.

> I don't understand? Surely there is no change, and one uses Aspect
> class>>font: or Aspect class>>color: as before?

Not from the users pov. With the change to Object>>publishedAspects, if
there is only a #yourself aspect (even if the class replaces the default in
Object(class)>> publishedAspectsOfInstances) the getters are listed.

If I am a new to Dolphin, and I open the Dolphin Options and go to the
System Folder, it is not obvious to me to double click/hit return to change
the Font aspect. The obvious action is to open the tree and start changing
#logFont.

I may be nit-picking, but it could be one of the first things a new Dolphin
user does.

Thanks,
Steve